[jira] [Commented] (HBASE-15957) RpcClientImpl.close never ends in some circumstances

2016-06-07 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15319768#comment-15319768
 ] 

Hudson commented on HBASE-15957:


SUCCESS: Integrated in HBase-1.1-JDK7 #1728 (See 
[https://builds.apache.org/job/HBase-1.1-JDK7/1728/])
HBASE-15957 RpcClientImpl.close never ends in some circumstances (enis: rev 
4418ba2f8f10ee08d82aee9f311e0e1b6bd7be5e)
* 
hbase-it/src/test/java/org/apache/hadoop/hbase/ipc/IntegrationTestRpcClient.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClientImpl.java


> RpcClientImpl.close never ends in some circumstances
> 
>
> Key: HBASE-15957
> URL: https://issues.apache.org/jira/browse/HBASE-15957
> Project: HBase
>  Issue Type: Bug
>  Components: Client, rpc
>Affects Versions: 1.1.2
>Reporter: Sergey Soldatov
>Assignee: Sergey Soldatov
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15957-2.patch, HBASE-15957.patch
>
>
> This bug is related to HBASE-14241 and HBASE-13851. 
> Fix for HBASE-13851 introduced the check for non alive connections and if 
> connection is not alive, it close it:
> {noformat}
> if (!conn.isAlive()) {
>   if (connsToClose == null) {
> connsToClose = new HashSet();
>   }
>   connsToClose.add(conn);
> }
> 
> if (connsToClose != null) {
>   for (Connection conn : connsToClose) {
> if (conn.markClosed(new InterruptedIOException("RpcClient is 
> closing"))) {
>   conn.close();
> }
>   }
> }
> {noformat}
> That worked fine until fix for HBASE-14241 introduced handling for interrupt 
> in writer thread:
> {noformat}
>   try {
> cts = callsToWrite.take();
>   } catch (InterruptedException e) {
> markClosed(new InterruptedIOException());
>   }
> {noformat}
> So, if writer thread is running, but connection thread is not started yet, 
> interrupt will cause calling of markClosed which will set 
> shouldCloseConnection flag for the parent connection. And the next time 
> during the handling of non alive connections markClosed will return false and 
> close will not be called. As the result connection will not be removed from 
> the connections pool and RpcClientImpl.close never finish. 



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


[jira] [Commented] (HBASE-15957) RpcClientImpl.close never ends in some circumstances

2016-06-07 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15319729#comment-15319729
 ] 

Hudson commented on HBASE-15957:


SUCCESS: Integrated in HBase-1.1-JDK8 #1815 (See 
[https://builds.apache.org/job/HBase-1.1-JDK8/1815/])
HBASE-15957 RpcClientImpl.close never ends in some circumstances (enis: rev 
4418ba2f8f10ee08d82aee9f311e0e1b6bd7be5e)
* 
hbase-it/src/test/java/org/apache/hadoop/hbase/ipc/IntegrationTestRpcClient.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClientImpl.java


> RpcClientImpl.close never ends in some circumstances
> 
>
> Key: HBASE-15957
> URL: https://issues.apache.org/jira/browse/HBASE-15957
> Project: HBase
>  Issue Type: Bug
>  Components: Client, rpc
>Affects Versions: 1.1.2
>Reporter: Sergey Soldatov
>Assignee: Sergey Soldatov
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15957-2.patch, HBASE-15957.patch
>
>
> This bug is related to HBASE-14241 and HBASE-13851. 
> Fix for HBASE-13851 introduced the check for non alive connections and if 
> connection is not alive, it close it:
> {noformat}
> if (!conn.isAlive()) {
>   if (connsToClose == null) {
> connsToClose = new HashSet();
>   }
>   connsToClose.add(conn);
> }
> 
> if (connsToClose != null) {
>   for (Connection conn : connsToClose) {
> if (conn.markClosed(new InterruptedIOException("RpcClient is 
> closing"))) {
>   conn.close();
> }
>   }
> }
> {noformat}
> That worked fine until fix for HBASE-14241 introduced handling for interrupt 
> in writer thread:
> {noformat}
>   try {
> cts = callsToWrite.take();
>   } catch (InterruptedException e) {
> markClosed(new InterruptedIOException());
>   }
> {noformat}
> So, if writer thread is running, but connection thread is not started yet, 
> interrupt will cause calling of markClosed which will set 
> shouldCloseConnection flag for the parent connection. And the next time 
> during the handling of non alive connections markClosed will return false and 
> close will not be called. As the result connection will not be removed from 
> the connections pool and RpcClientImpl.close never finish. 



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


[jira] [Commented] (HBASE-15957) RpcClientImpl.close never ends in some circumstances

2016-06-07 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15319659#comment-15319659
 ] 

Hudson commented on HBASE-15957:


FAILURE: Integrated in HBase-Trunk_matrix #1007 (See 
[https://builds.apache.org/job/HBase-Trunk_matrix/1007/])
HBASE-15957 RpcClientImpl.close never ends in some circumstances (enis: rev 
da88b4824054f57fbcbc7795469ab2369a39b5ed)
* 
hbase-it/src/test/java/org/apache/hadoop/hbase/ipc/IntegrationTestRpcClient.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClientImpl.java


> RpcClientImpl.close never ends in some circumstances
> 
>
> Key: HBASE-15957
> URL: https://issues.apache.org/jira/browse/HBASE-15957
> Project: HBase
>  Issue Type: Bug
>  Components: Client, rpc
>Affects Versions: 1.1.2
>Reporter: Sergey Soldatov
>Assignee: Sergey Soldatov
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15957-2.patch, HBASE-15957.patch
>
>
> This bug is related to HBASE-14241 and HBASE-13851. 
> Fix for HBASE-13851 introduced the check for non alive connections and if 
> connection is not alive, it close it:
> {noformat}
> if (!conn.isAlive()) {
>   if (connsToClose == null) {
> connsToClose = new HashSet();
>   }
>   connsToClose.add(conn);
> }
> 
> if (connsToClose != null) {
>   for (Connection conn : connsToClose) {
> if (conn.markClosed(new InterruptedIOException("RpcClient is 
> closing"))) {
>   conn.close();
> }
>   }
> }
> {noformat}
> That worked fine until fix for HBASE-14241 introduced handling for interrupt 
> in writer thread:
> {noformat}
>   try {
> cts = callsToWrite.take();
>   } catch (InterruptedException e) {
> markClosed(new InterruptedIOException());
>   }
> {noformat}
> So, if writer thread is running, but connection thread is not started yet, 
> interrupt will cause calling of markClosed which will set 
> shouldCloseConnection flag for the parent connection. And the next time 
> during the handling of non alive connections markClosed will return false and 
> close will not be called. As the result connection will not be removed from 
> the connections pool and RpcClientImpl.close never finish. 



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


[jira] [Commented] (HBASE-15957) RpcClientImpl.close never ends in some circumstances

2016-06-07 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15319634#comment-15319634
 ] 

Hudson commented on HBASE-15957:


FAILURE: Integrated in HBase-1.3-IT #695 (See 
[https://builds.apache.org/job/HBase-1.3-IT/695/])
HBASE-15957 RpcClientImpl.close never ends in some circumstances (enis: rev 
600d10a8b831afe0c881bc109d53f53cee9e3a8a)
* hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClientImpl.java
* 
hbase-it/src/test/java/org/apache/hadoop/hbase/ipc/IntegrationTestRpcClient.java


> RpcClientImpl.close never ends in some circumstances
> 
>
> Key: HBASE-15957
> URL: https://issues.apache.org/jira/browse/HBASE-15957
> Project: HBase
>  Issue Type: Bug
>  Components: Client, rpc
>Affects Versions: 1.1.2
>Reporter: Sergey Soldatov
>Assignee: Sergey Soldatov
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15957-2.patch, HBASE-15957.patch
>
>
> This bug is related to HBASE-14241 and HBASE-13851. 
> Fix for HBASE-13851 introduced the check for non alive connections and if 
> connection is not alive, it close it:
> {noformat}
> if (!conn.isAlive()) {
>   if (connsToClose == null) {
> connsToClose = new HashSet();
>   }
>   connsToClose.add(conn);
> }
> 
> if (connsToClose != null) {
>   for (Connection conn : connsToClose) {
> if (conn.markClosed(new InterruptedIOException("RpcClient is 
> closing"))) {
>   conn.close();
> }
>   }
> }
> {noformat}
> That worked fine until fix for HBASE-14241 introduced handling for interrupt 
> in writer thread:
> {noformat}
>   try {
> cts = callsToWrite.take();
>   } catch (InterruptedException e) {
> markClosed(new InterruptedIOException());
>   }
> {noformat}
> So, if writer thread is running, but connection thread is not started yet, 
> interrupt will cause calling of markClosed which will set 
> shouldCloseConnection flag for the parent connection. And the next time 
> during the handling of non alive connections markClosed will return false and 
> close will not be called. As the result connection will not be removed from 
> the connections pool and RpcClientImpl.close never finish. 



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


[jira] [Commented] (HBASE-15957) RpcClientImpl.close never ends in some circumstances

2016-06-07 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15319631#comment-15319631
 ] 

Hudson commented on HBASE-15957:


SUCCESS: Integrated in HBase-1.2 #644 (See 
[https://builds.apache.org/job/HBase-1.2/644/])
HBASE-15957 RpcClientImpl.close never ends in some circumstances (enis: rev 
da52e0cdf109199b157ccaedbd891336221c439b)
* 
hbase-it/src/test/java/org/apache/hadoop/hbase/ipc/IntegrationTestRpcClient.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClientImpl.java


> RpcClientImpl.close never ends in some circumstances
> 
>
> Key: HBASE-15957
> URL: https://issues.apache.org/jira/browse/HBASE-15957
> Project: HBase
>  Issue Type: Bug
>  Components: Client, rpc
>Affects Versions: 1.1.2
>Reporter: Sergey Soldatov
>Assignee: Sergey Soldatov
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15957-2.patch, HBASE-15957.patch
>
>
> This bug is related to HBASE-14241 and HBASE-13851. 
> Fix for HBASE-13851 introduced the check for non alive connections and if 
> connection is not alive, it close it:
> {noformat}
> if (!conn.isAlive()) {
>   if (connsToClose == null) {
> connsToClose = new HashSet();
>   }
>   connsToClose.add(conn);
> }
> 
> if (connsToClose != null) {
>   for (Connection conn : connsToClose) {
> if (conn.markClosed(new InterruptedIOException("RpcClient is 
> closing"))) {
>   conn.close();
> }
>   }
> }
> {noformat}
> That worked fine until fix for HBASE-14241 introduced handling for interrupt 
> in writer thread:
> {noformat}
>   try {
> cts = callsToWrite.take();
>   } catch (InterruptedException e) {
> markClosed(new InterruptedIOException());
>   }
> {noformat}
> So, if writer thread is running, but connection thread is not started yet, 
> interrupt will cause calling of markClosed which will set 
> shouldCloseConnection flag for the parent connection. And the next time 
> during the handling of non alive connections markClosed will return false and 
> close will not be called. As the result connection will not be removed from 
> the connections pool and RpcClientImpl.close never finish. 



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


[jira] [Commented] (HBASE-15957) RpcClientImpl.close never ends in some circumstances

2016-06-07 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15319602#comment-15319602
 ] 

Hudson commented on HBASE-15957:


SUCCESS: Integrated in HBase-1.3 #727 (See 
[https://builds.apache.org/job/HBase-1.3/727/])
HBASE-15957 RpcClientImpl.close never ends in some circumstances (enis: rev 
600d10a8b831afe0c881bc109d53f53cee9e3a8a)
* hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClientImpl.java
* 
hbase-it/src/test/java/org/apache/hadoop/hbase/ipc/IntegrationTestRpcClient.java


> RpcClientImpl.close never ends in some circumstances
> 
>
> Key: HBASE-15957
> URL: https://issues.apache.org/jira/browse/HBASE-15957
> Project: HBase
>  Issue Type: Bug
>  Components: Client, rpc
>Affects Versions: 1.1.2
>Reporter: Sergey Soldatov
>Assignee: Sergey Soldatov
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15957-2.patch, HBASE-15957.patch
>
>
> This bug is related to HBASE-14241 and HBASE-13851. 
> Fix for HBASE-13851 introduced the check for non alive connections and if 
> connection is not alive, it close it:
> {noformat}
> if (!conn.isAlive()) {
>   if (connsToClose == null) {
> connsToClose = new HashSet();
>   }
>   connsToClose.add(conn);
> }
> 
> if (connsToClose != null) {
>   for (Connection conn : connsToClose) {
> if (conn.markClosed(new InterruptedIOException("RpcClient is 
> closing"))) {
>   conn.close();
> }
>   }
> }
> {noformat}
> That worked fine until fix for HBASE-14241 introduced handling for interrupt 
> in writer thread:
> {noformat}
>   try {
> cts = callsToWrite.take();
>   } catch (InterruptedException e) {
> markClosed(new InterruptedIOException());
>   }
> {noformat}
> So, if writer thread is running, but connection thread is not started yet, 
> interrupt will cause calling of markClosed which will set 
> shouldCloseConnection flag for the parent connection. And the next time 
> during the handling of non alive connections markClosed will return false and 
> close will not be called. As the result connection will not be removed from 
> the connections pool and RpcClientImpl.close never finish. 



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


[jira] [Commented] (HBASE-15957) RpcClientImpl.close never ends in some circumstances

2016-06-07 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15319535#comment-15319535
 ] 

Hudson commented on HBASE-15957:


SUCCESS: Integrated in HBase-1.4 #201 (See 
[https://builds.apache.org/job/HBase-1.4/201/])
HBASE-15957 RpcClientImpl.close never ends in some circumstances (enis: rev 
7fed7a8f4eff4e06d73b72c7e9620caadeb94e5c)
* 
hbase-it/src/test/java/org/apache/hadoop/hbase/ipc/IntegrationTestRpcClient.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClientImpl.java


> RpcClientImpl.close never ends in some circumstances
> 
>
> Key: HBASE-15957
> URL: https://issues.apache.org/jira/browse/HBASE-15957
> Project: HBase
>  Issue Type: Bug
>  Components: Client, rpc
>Affects Versions: 1.1.2
>Reporter: Sergey Soldatov
>Assignee: Sergey Soldatov
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15957-2.patch, HBASE-15957.patch
>
>
> This bug is related to HBASE-14241 and HBASE-13851. 
> Fix for HBASE-13851 introduced the check for non alive connections and if 
> connection is not alive, it close it:
> {noformat}
> if (!conn.isAlive()) {
>   if (connsToClose == null) {
> connsToClose = new HashSet();
>   }
>   connsToClose.add(conn);
> }
> 
> if (connsToClose != null) {
>   for (Connection conn : connsToClose) {
> if (conn.markClosed(new InterruptedIOException("RpcClient is 
> closing"))) {
>   conn.close();
> }
>   }
> }
> {noformat}
> That worked fine until fix for HBASE-14241 introduced handling for interrupt 
> in writer thread:
> {noformat}
>   try {
> cts = callsToWrite.take();
>   } catch (InterruptedException e) {
> markClosed(new InterruptedIOException());
>   }
> {noformat}
> So, if writer thread is running, but connection thread is not started yet, 
> interrupt will cause calling of markClosed which will set 
> shouldCloseConnection flag for the parent connection. And the next time 
> during the handling of non alive connections markClosed will return false and 
> close will not be called. As the result connection will not be removed from 
> the connections pool and RpcClientImpl.close never finish. 



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


[jira] [Commented] (HBASE-15957) RpcClientImpl.close never ends in some circumstances

2016-06-07 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15319205#comment-15319205
 ] 

Hudson commented on HBASE-15957:


SUCCESS: Integrated in HBase-1.2-IT #526 (See 
[https://builds.apache.org/job/HBase-1.2-IT/526/])
HBASE-15957 RpcClientImpl.close never ends in some circumstances (enis: rev 
da52e0cdf109199b157ccaedbd891336221c439b)
* 
hbase-it/src/test/java/org/apache/hadoop/hbase/ipc/IntegrationTestRpcClient.java
* hbase-client/src/main/java/org/apache/hadoop/hbase/ipc/RpcClientImpl.java


> RpcClientImpl.close never ends in some circumstances
> 
>
> Key: HBASE-15957
> URL: https://issues.apache.org/jira/browse/HBASE-15957
> Project: HBase
>  Issue Type: Bug
>  Components: Client, rpc
>Affects Versions: 1.1.2
>Reporter: Sergey Soldatov
>Assignee: Sergey Soldatov
> Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 1.1.6
>
> Attachments: HBASE-15957-2.patch, HBASE-15957.patch
>
>
> This bug is related to HBASE-14241 and HBASE-13851. 
> Fix for HBASE-13851 introduced the check for non alive connections and if 
> connection is not alive, it close it:
> {noformat}
> if (!conn.isAlive()) {
>   if (connsToClose == null) {
> connsToClose = new HashSet();
>   }
>   connsToClose.add(conn);
> }
> 
> if (connsToClose != null) {
>   for (Connection conn : connsToClose) {
> if (conn.markClosed(new InterruptedIOException("RpcClient is 
> closing"))) {
>   conn.close();
> }
>   }
> }
> {noformat}
> That worked fine until fix for HBASE-14241 introduced handling for interrupt 
> in writer thread:
> {noformat}
>   try {
> cts = callsToWrite.take();
>   } catch (InterruptedException e) {
> markClosed(new InterruptedIOException());
>   }
> {noformat}
> So, if writer thread is running, but connection thread is not started yet, 
> interrupt will cause calling of markClosed which will set 
> shouldCloseConnection flag for the parent connection. And the next time 
> during the handling of non alive connections markClosed will return false and 
> close will not be called. As the result connection will not be removed from 
> the connections pool and RpcClientImpl.close never finish. 



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


[jira] [Commented] (HBASE-15957) RpcClientImpl.close never ends in some circumstances

2016-06-06 Thread Enis Soztutar (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15317604#comment-15317604
 ] 

Enis Soztutar commented on HBASE-15957:
---

Thanks [~sergey.soldatov]. The patch makes sense since not in all cases after 
calling markClosed(), we call close() from that thread. So, if a thread calls 
markClosed() without subsequent call to close(), then the write thread does 
{{if (markClosed())}} check the thread will just hang.



> RpcClientImpl.close never ends in some circumstances
> 
>
> Key: HBASE-15957
> URL: https://issues.apache.org/jira/browse/HBASE-15957
> Project: HBase
>  Issue Type: Bug
>  Components: Client, rpc
>Affects Versions: 1.1.2
>Reporter: Sergey Soldatov
>Assignee: Sergey Soldatov
> Attachments: HBASE-15957-2.patch, HBASE-15957.patch
>
>
> This bug is related to HBASE-14241 and HBASE-13851. 
> Fix for HBASE-13851 introduced the check for non alive connections and if 
> connection is not alive, it close it:
> {noformat}
> if (!conn.isAlive()) {
>   if (connsToClose == null) {
> connsToClose = new HashSet();
>   }
>   connsToClose.add(conn);
> }
> 
> if (connsToClose != null) {
>   for (Connection conn : connsToClose) {
> if (conn.markClosed(new InterruptedIOException("RpcClient is 
> closing"))) {
>   conn.close();
> }
>   }
> }
> {noformat}
> That worked fine until fix for HBASE-14241 introduced handling for interrupt 
> in writer thread:
> {noformat}
>   try {
> cts = callsToWrite.take();
>   } catch (InterruptedException e) {
> markClosed(new InterruptedIOException());
>   }
> {noformat}
> So, if writer thread is running, but connection thread is not started yet, 
> interrupt will cause calling of markClosed which will set 
> shouldCloseConnection flag for the parent connection. And the next time 
> during the handling of non alive connections markClosed will return false and 
> close will not be called. As the result connection will not be removed from 
> the connections pool and RpcClientImpl.close never finish. 



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


[jira] [Commented] (HBASE-15957) RpcClientImpl.close never ends in some circumstances

2016-06-03 Thread Enis Soztutar (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314896#comment-15314896
 ] 

Enis Soztutar commented on HBASE-15957:
---

I think the idea with markClosed() is to make sure that the connection is 
closed only once. Only if you get true from markClosed() call, you should call 
close(). This assumes that if you get markClosed() to return true, in all 
cases, you should call close() yourself. But apparently it is not the case. 

> RpcClientImpl.close never ends in some circumstances
> 
>
> Key: HBASE-15957
> URL: https://issues.apache.org/jira/browse/HBASE-15957
> Project: HBase
>  Issue Type: Bug
>  Components: Client, rpc
>Affects Versions: 1.1.2
>Reporter: Sergey Soldatov
>Assignee: Sergey Soldatov
> Attachments: HBASE-15957.patch
>
>
> This bug is related to HBASE-14241 and HBASE-13851. 
> Fix for HBASE-13851 introduced the check for non alive connections and if 
> connection is not alive, it close it:
> {noformat}
> if (!conn.isAlive()) {
>   if (connsToClose == null) {
> connsToClose = new HashSet();
>   }
>   connsToClose.add(conn);
> }
> 
> if (connsToClose != null) {
>   for (Connection conn : connsToClose) {
> if (conn.markClosed(new InterruptedIOException("RpcClient is 
> closing"))) {
>   conn.close();
> }
>   }
> }
> {noformat}
> That worked fine until fix for HBASE-14241 introduced handling for interrupt 
> in writer thread:
> {noformat}
>   try {
> cts = callsToWrite.take();
>   } catch (InterruptedException e) {
> markClosed(new InterruptedIOException());
>   }
> {noformat}
> So, if writer thread is running, but connection thread is not started yet, 
> interrupt will cause calling of markClosed which will set 
> shouldCloseConnection flag for the parent connection. And the next time 
> during the handling of non alive connections markClosed will return false and 
> close will not be called. As the result connection will not be removed from 
> the connections pool and RpcClientImpl.close never finish. 



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


[jira] [Commented] (HBASE-15957) RpcClientImpl.close never ends in some circumstances

2016-06-03 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-15957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15314810#comment-15314810
 ] 

Hadoop QA commented on HBASE-15957:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m 
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s 
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:red}-1{color} | {color:red} test4tests {color} | {color:red} 0m 0s 
{color} | {color:red} The patch doesn't appear to include any new or modified 
tests. Please justify why no new tests are needed for this patch. Also please 
list what manual steps were performed to verify this patch. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m 
0s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 27s 
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 16s 
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 
24s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 
10s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 
57s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 27s 
{color} | {color:green} master passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 19s 
{color} | {color:green} master passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 
19s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 27s 
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 27s 
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 18s 
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 18s 
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 
24s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 
14s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
25m 56s {color} | {color:green} Patch does not cause any errors with Hadoop 
2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.1 2.6.2 2.6.3 2.7.1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m 
15s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 26s 
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 19s 
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 56s 
{color} | {color:green} hbase-client in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 
7s {color} | {color:green} Patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 37m 5s {color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12808052/HBASE-15957.patch |
| JIRA Issue | HBASE-15957 |
| Optional Tests |  asflicense  javac  javadoc  unit  findbugs  hadoopcheck  
hbaseanti  checkstyle  compile  |
| uname | Linux asf900.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP 
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build@2/component/dev-support/hbase-personality.sh
 |
| git revision | master / f0c159b |
| Default Java | 1.7.0_79 |
| Multi-JDK versions |  /home/jenkins/tools/java/jdk1.8.0:1.8.0 
/usr/local/jenkins/java/jdk1.7.0_79:1.7.0_79 |
| findbugs |