[
https://issues.apache.org/jira/browse/ACCUMULO-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845521#comment-13845521
]
Bill Havanki commented on ACCUMULO-1923:
----------------------------------------
[~ecn]: The changes I have for this only address this specific problem as
reported. However, there seem to be other areas where ZK instances could be
left unclosed before finalization, areas that are not being exercised during
the Sequential randomwalk test.
1. Should the scope of this ticket expand to include those areas?
2. Would the lack of resolving those other problems block the release of 1.4.5,
as this ticket does?
Thanks.
> warning at the end of a MapReduce job
> -------------------------------------
>
> 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
> Fix For: 1.4.5, 1.5.1, 1.6.0
>
>
> 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.4#6159)
