Re: recent metastore failures in HiveQA

2016-04-27 Thread Wei Zheng
Still seeing lots of failing tests with "Connection refused" message.. But locally they run fine. Thanks, Wei On 4/12/16, 14:48, "Ashutosh Chauhan" wrote: >I can repro locally hang of TestJdbcWithMiniHS2 and I also saw it hanging >on recent QA runs: >http://ec2-174-129-184-35.compute-1

Re: recent metastore failures in HiveQA

2016-04-12 Thread Ashutosh Chauhan
I can repro locally hang of TestJdbcWithMiniHS2 and I also saw it hanging on recent QA runs: http://ec2-174-129-184-35.compute-1.amazonaws.com/logs/PreCommit-HIVE-TRUNK-Build-7556/failed/TestJdbcWithMiniHS2/ Wondering if you guys have seen this? Thanks, Ashutosh On Tue, Apr 12, 2016 at 11:28 A

Re: recent metastore failures in HiveQA

2016-04-12 Thread Szehon Ho
Thanks Thejas for this patch! I'm also going to restart PTest and force recreation of the test slaves based on fresh image to see if it resolves the issue (in case the test slaves are getting too loaded and slow to start HMS in time). If not then Thejas's patch should tell us a bit more. On Tue,

Re: recent metastore failures in HiveQA

2016-04-12 Thread Thejas Nair
Created a patch that should hopefully help in figuring out whats going on - https://issues.apache.org/jira/browse/HIVE-13491 On Wed, Apr 6, 2016 at 1:56 PM, Szehon Ho wrote: > Yea thanks for point it out. I see it too and am not able to reproduce it > locally. It points to an environment issu

Re: recent metastore failures in HiveQA

2016-04-06 Thread Szehon Ho
Yea thanks for point it out. I see it too and am not able to reproduce it locally. It points to an environment issue, but not aware anything changed with the environment. Anyone have any ideas? On Wed, Apr 6, 2016 at 1:29 PM, Sergey Shelukhin wrote: > Has anyone else noticed that many tests t

recent metastore failures in HiveQA

2016-04-06 Thread Sergey Shelukhin
Has anyone else noticed that many tests that involve metastore started failing lately? The failures are sporadic and happen both in the tests that test metastore, and q files that use metastore… The error is always something like java.net.ConnectException: Connection refused at java.net.Pla