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] [Commented] (ACCUMULO-4169) TabletServer.config contextCleaner removes contexts that are not set on a table
Date Thu, 24 Mar 2016 17:07:25 GMT

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

Josh Elser commented on ACCUMULO-4169:
--------------------------------------

bq. The concern I have is that each class loader takes up perm-gen space. So cleaning them
out if not being used seems prudent.

Ahh, of course. Thanks for pointing that out, [~ivan.bella]. That's a little scary too --
clients have the ability to attack the servers via creating lots of new contexts, right? This
sounds like something we should be monitoring closely and have a crystal clear understanding
of its use. I'm not sure what kind of protection we could provide to prevent clients in a
multi-tenant environment from tanking the entire system.

> 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