[ 
https://issues.apache.org/jira/browse/OOZIE-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15518010#comment-15518010
 ] 

Hadoop QA commented on OOZIE-2654:
----------------------------------

Testing JIRA OOZIE-2654

Cleaning local git workspace

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:green}+1{color} the patch does not introduce any trailing spaces
.    {color:green}+1{color} the patch does not introduce any line longer than 
132
.    {color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.    {color:green}+1{color} HEAD compiles
.    {color:green}+1{color} patch compiles
.    {color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.    {color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.    {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.    Tests run: 1808
.    Tests failed: 5
.    Tests errors: 4

.    The patch failed the following testcases:

.      testMain(org.apache.oozie.action.hadoop.TestHiveMain)
.      testPigScript(org.apache.oozie.action.hadoop.TestPigMainWithOldAPI)
.      testEmbeddedPigWithinPython(org.apache.oozie.action.hadoop.TestPigMain)
.      testPigScript(org.apache.oozie.action.hadoop.TestPigMain)
.      testPig_withNullExternalID(org.apache.oozie.action.hadoop.TestPigMain)

{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/3327/

> Zookeeper dependent services should not depend on Connectionstate to be valid 
> before cleaning up
> ------------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-2654
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2654
>             Project: Oozie
>          Issue Type: Bug
>          Components: HA
>    Affects Versions: 4.2.0
>            Reporter: Venkat Ranganathan
>            Assignee: Venkat Ranganathan
>         Attachments: OOZIE-2654.diff
>
>
> Currently in ZKUtils, ZKLocks and ZKJobsConcurrency services, we don't 
> properly teardown the zookeeper connections when the callback was not 
> received from zookeeper to change the connection state.
> We can get into this situation if the ZK session for example was closed by ZK 
> before any callback was received to update the connection state. This can 
> cause the oozie server in a HA mode to not terminate  with one or more 
> sockets in close_wait state.
> Here is an instance of this issue
> From the network connections, we have one connection still on close_wait with 
> indefinite wait.
> {quote} tcp6 143 0 x.x.x.1:46710 x.x.x.2:2181 CLOSE_WAIT 4688/java off 
> (0.00/0/0)
> {quote}
> From the zookeeper logs,
> {quote}
> 016-08-18 20:45:29,921 - INFO 
> NIOServerCxn.Factory:0.0.0.0/0.0.0.0:2181:ZooKeeperServer@868 - Client 
> attempting to establish new session at /x.x.x.1:46710 2016-08-18 20:45:29,926 
> - INFO CommitProcessor:1:ZooKeeperServer@617 - Established session 
> 0x1569f576843000e with negotiated timeout 40000 for client /x.x.x.1:46710
> {quote}
> and later
> {quote}
> 2016-08-18 20:46:34,008 - INFO CommitProcessor:1:NIOServerCnxn@1007 - Closed 
> socket connection for client /x.x.x.1:46710 which had sessionid 
> 0x1569f576843000e
> {quote}
> The fix is to not check for the connectionstate during service destroy and  
> teardown the zk connections.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to