You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2011/05/05 22:47:03 UTC

[jira] [Commented] (HBASE-3700) Suggestion to note close connection explicitly at exit in HBase book, and improve MapReduce interface by adding explicit closes

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

stack commented on HBASE-3700:
------------------------------

This situation should be improved by just committed hbase-3777

> Suggestion to note close connection explicitly at exit in HBase book, and improve MapReduce interface by adding explicit closes
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-3700
>                 URL: https://issues.apache.org/jira/browse/HBASE-3700
>             Project: HBase
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Guanpeng Xu
>            Priority: Minor
>
> I once had an issue of "Too many connections" in ZooKeeper while running a MapReduce job where tables are used in my own classes instead of the interface provided by HBase (e.g. TableInputFormat and TableOutputFormat etc).  Investigation suggests this is due to many ZooKeeper's connection slots are occupied by remaining connections after clients exit, so that the free slots are not enough.
> Discussed with Lars George, I suggest we note the need of explicit close of connections (to ZooKeepers) in HBase book.  Lars also suggests we improve TableOutputFormat by adding explicit calls to close methods.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira