Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is to increase the Xmx for HMS/Hive for this image, since recently I got a lot failures during HIVE_TEST in presto code, Refer:
prestodb/presto#13699
The errors showing in the travis CI are sth like:
com.facebook.presto.spi.PrestoException: hadoop-master:9083: java.net.SocketTimeoutException: Read timed out
at com.facebook.presto.hive.metastore.thrift.ThriftHiveMetastore.getTable(ThriftHiveMetastore.java:292)
at com.facebook.presto.hive.metastore.thrift.BridgingHiveMetastore.getTable(BridgingHiveMetastore.java:83)
at com.facebook.presto.hive.metastore.CachingHiveMetastore.loadTable(CachingHiveMetastore.java:274)
...
After I did some research inside the containers, in HMS logs, I got stuff like:
Starting Hive Metastore Server
Exception in thread "pool-8-thread-2" java.lang.OutOfMemoryError: GC overhead limit exceeded
WARNING: Use "yarn jar" to launch YARN applications.
Exception in thread "pool-8-thread-364" Exception in thread "pool-8-thread-369" java.lang.OutOfMemoryError: GC overhead limit exceeded
at org.apache.commons.lang.exception.ExceptionUtils.(ExceptionUtils.java:65)
at org.apache.hadoop.hive.metastore.RetryingHMSHandler.invokeInternal(RetryingHMSHandler.java:203)
at org.apache.hadoop.hive.metastore.RetryingHMSHandler.invoke(RetryingHMSHandler.java:105)
at com.sun.proxy.$Proxy16.get_partition(Unknown Source)
at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$get_partition.getResult(ThriftHiveMetastore.java:10354)
at org.apache.hadoop.hive.metastore.api.ThriftHiveMetastore$Processor$get_partition.getResult(ThriftHiveMetastore.java:10338)
at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:39)
at org.apache.hadoop.hive.metastore.TUGIBasedProcessor.process(TUGIBasedProcessor.java:103)
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)
Exception in thread "pool-8-thread-365" java.lang.NoCl...
Even I switch to master branch, running this hive tests locally, sometimes I got ok, sometimes I got exactly same errors.