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

Jonathan Hsieh updated HBASE-16117:
-----------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.2.5)
                       (was: 1.1.7)
                       (was: 1.3.1)
     Release Note: 
(This change will be irrelevant after HBASE-16774 lands).
There is a subtle change with error handling when a connection is not able to 
connect to ZK.  Attempts to create a connection when ZK is not up will now fail 
immediately instead of silently creating and then failing on a subsequent 
HBaseAdmin call.



  was:There is a subtle change with error handling when a connection is not 
able to connect to ZK.  Attempts to create a connection when ZK is not up will 
now fail immediately instead of silently creating and then failing on a 
subsequent HBaseAdmin call.

           Status: Resolved  (was: Patch Available)

As noted earlier, I'm abandoning the attempt to port to 1.x currently.

> Fix Connection leak in mapred.TableOutputFormat 
> ------------------------------------------------
>
>                 Key: HBASE-16117
>                 URL: https://issues.apache.org/jira/browse/HBASE-16117
>             Project: HBase
>          Issue Type: Bug
>          Components: mapreduce
>    Affects Versions: 2.0.0, 1.3.0, 1.2.2, 1.1.6
>            Reporter: Jonathan Hsieh
>            Assignee: Jonathan Hsieh
>             Fix For: 2.0.0
>
>         Attachments: HBASE-16117.branch-1.001.patch, 
> hbase-16117-part2.v5.patch, hbase-16117.branch-1.002.patch, 
> hbase-16117.branch-1.patch, hbase-16117.part2.v6.patch, hbase-16117.patch, 
> hbase-16117.v2.branch-1.patch, hbase-16117.v2.patch, 
> hbase-16117.v3.branch-1.patch, hbase-16117.v3.patch, hbase-16117.v4.patch
>
>
> Spark seems to instantiate multiple instances of output formats within a 
> single process.  When mapred.TableOutputFormat (not 
> mapreduce.TableOutputFormat) is used, this may cause connection leaks that 
> slowly exhaust the cluster's zk connections.  
> This patch fixes that.



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

Reply via email to