hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-4619) TableOutputFormat.close() interferes with HBase clients in same JVM
Date Tue, 06 Jan 2015 16:44:34 GMT

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

Andrew Purtell resolved HBASE-4619.
-----------------------------------
    Resolution: Not a Problem

Thanks for the nudge [~clehene]

> TableOutputFormat.close() interferes with HBase clients in same JVM
> -------------------------------------------------------------------
>
>                 Key: HBASE-4619
>                 URL: https://issues.apache.org/jira/browse/HBASE-4619
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Dave Revell
>              Labels: close, delete
>
> This appears in TableOutputFormat.java: 
> {code}
> @Override
>     public void close(TaskAttemptContext context)
>     throws IOException {
>       table.flushCommits();
>       // The following call will shutdown all connections to the cluster from
>       // this JVM.  It will close out our zk session otherwise zk wil log
>       // expired sessions rather than closed ones.  If any other HTable instance
>       // running in this JVM, this next call will cause it damage.  Presumption
>       // is that the above this.table is only instance.
>       HConnectionManager.deleteAllConnections(true);
>     }
> {code}
> It's not a safe assumption that a single TableOutputFormat is the only HBase client in
a JVM.



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

Mime
View raw message