accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Bella (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4169) TabletServer.config contextCleaner removes contexts that are not set on a table
Date Tue, 29 Mar 2016 22:21:25 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216954#comment-15216954
] 

Ivan Bella commented on ACCUMULO-4169:
--------------------------------------

I believe I am ok with that solution.  If a system owner is adding context definitions, then
they need to ensure that the permgen (for Java 7) can handle at least that many classloaders
concurrently.  So change the code to only remove contexts that are not defined, and add the
CMSClassUnloadingEnabled as a default flag in the environment.

> TabletServer.config contextCleaner removes contexts that are not set on a table
> -------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-4169
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4169
>             Project: Accumulo
>          Issue Type: Bug
>          Components: tserver
>    Affects Versions: 1.8.0
>            Reporter: Dave Marion
>
> ACCUMULO-3948 added a feature where you could define a context in the Accumulo configuration,
not set it on a table, and use it in a Scanner. However, there is a runnable created n TabletServer.config()
that runs every 60 seconds that closes context that are not defined on a table. Suggesting
that we have the context cleaner not close any context defined in the configuration.



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

Mime
View raw message