[
https://issues.apache.org/jira/browse/HBASE-12833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14274461#comment-14274461
]
Enis Soztutar commented on HBASE-12833:
---------------------------------------
bq. I'm now wondering if we'll need to skip this patch and revert the work
committed on HBASE-12495 for 1.x, so that shell scripts continue to use the old
managed/shared connection code. This would be an API,semantics compatibility
question.
I personally have not encountered a user that has used jruby classes directly
(rather than shell usage). Even if there are some, I would argue that it should
be pretty rare. I am in favor of breaking this for branch-1.
> [shell] table.rb leaks connections
> ----------------------------------
>
> Key: HBASE-12833
> URL: https://issues.apache.org/jira/browse/HBASE-12833
> Project: HBase
> Issue Type: Bug
> Components: shell
> Affects Versions: 1.0.0, 2.0.0, 1.1.0
> Reporter: Nick Dimiduk
> Assignee: Solomon Duskis
> Fix For: 1.0.0, 2.0.0, 1.1.0
>
> Attachments: HBASE-12833.patch
>
>
> TestShell is erring out (timeout) consistently for me. Culprit is OOM cannot
> create native thread. It looks to me like test_table.rb and hbase/table.rb
> are made for leaking connections. table calls
> ConnectionFactory.createConnection() for every table but provides no close()
> method to clean it up. test_table creates a new table with every test.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
