hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-3700) Suggestion to note close connection explicitly at exit in HBase book, and improve MapReduce interface by adding explicit closes
Date Wed, 28 May 2014 15:04:02 GMT

     [ https://issues.apache.org/jira/browse/HBASE-3700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack resolved HBASE-3700.
--------------------------

    Resolution: Cannot Reproduce

Resolving as can't reproduce.  Lets open new issue if still a problem.

> 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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message