Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1669458351.1220055344270.JavaMail.jira@brutus>
Date: Fri, 29 Aug 2008 17:15:44 -0700 (PDT)
From: "Jim Kellerman (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-854) hbase-841 broke build on hudson?
In-Reply-To: <1038116351.1219986524315.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12627168#action_12627168 ] 

Jim Kellerman commented on HBASE-854:
-------------------------------------

For whatever reason, IPC proxies are not being shut down reliably and consequently test cases that run multiple tests may experience this problem because the proxy cache is static and does not get shut down properly.
This occurs in HConnectionManager, and in HRegionServer. Further, the RPC version number for HRegionInterface was not incremented when we changed the IPC, so old applications could potentially do "bad things" when talking to a server implementing the new interface.

We need to ensure that HRegionServer and HConnectionManager call HbaseRPC.stopProxy, for each open connection when the processes are exiting.

> hbase-841 broke build on hudson?
> --------------------------------
>
>                 Key: HBASE-854
>                 URL: https://issues.apache.org/jira/browse/HBASE-854
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: Jim Kellerman
>            Priority: Blocker
>             Fix For: 0.18.0
>
>         Attachments: hbase-854.patch
>
>
> Jim, you want to take a look at it?
> 841 changed interfaces.  Changed interfaces can make for odd issues like the hangs exhibited up on hudson (stuff is failing for me on my laptop since about the commit 841... timeouts.  I don't have same issue on branch).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.