Hive问题
GC overhead limit exceeded
- 问题描述:
DataGrip连接hiveserver2执行带MR的sql不停。
- 报错信息:
两个文件的日志信息
Job Submission failed with exception 'java.io.InterruptedIOException(Retry interrupted)'FAILED: command has been interrupted: during query execution:nullOKOKOKOKOKException in thread "HiveServer2-Handler-Pool: Thread-431" java.lang.OutOfMemoryError: GC overhead limit exceededat java.nio.ByteBuffer.wrap(ByteBuffer.java:373)at java.nio.ByteBuffer.wrap(ByteBuffer.java:396)at org.apache.hadoop.hive.serde2.thrift.ColumnBuffer.toTColumn(ColumnBuffer.java:317)at org.apache.hive.service.cli.ColumnBasedSet.toTRowSet(ColumnBasedSet.java:165)at org.apache.hive.service.cli.thrift.ThriftCLIService.FetchResults(ThriftCLIService.java:791)at org.apache.hive.service.rpc.thrift.TCLIService$Processor$FetchResults.getResult(TCLIService.java:1837)at org.apache.hive.service.rpc.thrift.TCLIService$Processor$FetchResults.getResult(TCLIService.java:1822)at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)at org.apache.hive.service.auth.TSetIpAddressProcessor.process(TSetIpAddressProcessor.java:56)at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748)java.io.FileNotFoundException: File does not exist: /tmp/atguigu/operation_logs/756591cf-0199-454f-8464-30ab702b8a5eat org.apache.commons.io.FileUtils.forceDelete(FileUtils.java:2275) ~[commons-io-2.4.jar:2.4]at org.apache.hive.service.cli.session.HiveSessionImpl.cleanupSessionLogDir(HiveSessionImpl.java:793) ~[hive-service-3.1.2.jar:3.1.2]at org.apache.hive.service.cli.session.HiveSessionImpl.close(HiveSessionImpl.java:754) ~[hive-service-3.1.2.jar:3.1.2]at org.apache.hive.service.cli.session.HiveSessionImplwithUGI.close(HiveSessionImplwithUGI.java:93) ~[hive-service-3.1.2.jar:3.1.2]at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_212]at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_212]at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_212]at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_212]at org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:78) ~[hive-service-3.1.2.jar:3.1.2]at org.apache.hive.service.cli.session.HiveSessionProxy.access$000(HiveSessionProxy.java:36) ~[hive-service-3.1.2.jar:3.1.2]at org.apache.hive.service.cli.session.HiveSessionProxy$1.run(HiveSessionProxy.java:63) ~[hive-service-3.1.2.jar:3.1.2]at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_212]at javax.security.auth.Subject.doAs(Subject.java:422) ~[?:1.8.0_212]at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1729) ~[hadoop-common-3.1.3.jar:?]at org.apache.hive.service.cli.session.HiveSessionProxy.invoke(HiveSessionProxy.java:59) ~[hive-service-3.1.2.jar:3.1.2]at com.sun.proxy.$Proxy37.close(Unknown Source) ~[?:?]at org.apache.hive.service.cli.session.SessionManager.closeSession(SessionManager.java:552) ~[hive-service-3.1.2.jar:3.1.2]at org.apache.hive.service.cli.CLIService.closeSession(CLIService.java:241) ~[hive-service-3.1.2.jar:3.1.2]at org.apache.hive.service.cli.thrift.ThriftBinaryCLIService$1.deleteContext(ThriftBinaryCLIService.java:141) ~[hive-service-3.1.2.jar:3.1.2]at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:300) ~[hive-exec-3.1.2.jar:3.1.2]at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[?:1.8.0_212]at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[?:1.8.0_212]at java.lang.Thread.run(Thread.java:748) [?:1.8.0_212]2022-02-27T21:55:59,699 INFO [756591cf-0199-454f-8464-30ab702b8a5e HiveServer2-Handler-Pool: Thread-444] session.SessionState: Resetting thread name to HiveServer2-Handler-Pool: Thread-444
- 解决方案:
错误原因:
由java.lang.OutOfMemoryError: Java heap space 可知 hiveserver2运行出现 JVM内存溢出
This Error happened during connect hiveserver2 via beeline, both happened from hiveserver node and remote node.
解决方法:
heapsize太小了,可以适当的调大些
Root cause, the heapsize of hadoop opts is too small, need to increase the size in hive-env.sh as bold.
修改hive-env.sh配置文件,详情修改内容如下cd hive/confmv hive-env.sh.template hive-env.sh# Hive Client memory usage can be an issue if a large number of clients# are running at the same time. The flags below have been useful in# reducing memory usage:#if [ "$SERVICE" = "cli" ]; thenif [ -z "$DEBUG" ]; thenexport HADOOP_OPTS="$HADOOP_OPTS -XX:NewRatio=12 -Xms10m -Xmx4096m -XX:MaxHeapFreeRatio=40 -XX:MinHeapFreeRatio=15 -XX:+UseParNewGC -XX:-UseGCOverheadLimit"elseexport HADOOP_OPTS="$HADOOP_OPTS -XX:NewRatio=12 -Xms10m -Xmx4096m -XX:MaxHeapFreeRatio=40 -XX:MinHeapFreeRatio=15 -XX:-UseGCOverheadLimit"fifi# The heap size of the jvm stared by hive shell script can be controlled via:#export HADOOP_HEAPSIZE=4096## Larger heap size may be required when running queries over large number of files or partitions.# By default hive shell scripts use a heap size of 256 (MB). Larger heap size would also be# appropriate for hive server.
