accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-1923) Ensure ZK instances closed correctly
Date Mon, 30 Dec 2013 21:54:50 GMT

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

Josh Elser updated ACCUMULO-1923:
---------------------------------

    Priority: Minor  (was: Critical)

> Ensure ZK instances closed correctly
> ------------------------------------
>
>                 Key: ACCUMULO-1923
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1923
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>         Environment: development single node, hadoop 2.2, 
>            Reporter: Eric Newton
>            Assignee: Bill Havanki
>            Priority: Minor
>             Fix For: 1.4.5, 1.5.1, 1.6.0
>
>
> Was: "warning at the end of a MapReduce job"
> Ensure that ZK instances are closed where opened across the Accumulo codebase. This is
an expansion of the original ticket scope, whose description is below.
> Original Description:
> While running the randomwalk tests I saw this at the end of a map/reduce job:
> {noformat}
> 22 16:56:30,583 [client.ZooKeeperInstance] WARN : ZooKeeperInstance being cleaned up
without being closed. Please remember to call close() before dereferencing to clean up threads.
> {noformat}
> This came just after the warning:
> {noformat}
> 22 16:56:31,742 [sequential.MapRedVerify] DEBUG: Dropping table: sequential_hostname_1385157013877_MR
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message