accumulo-notifications mailing list archives

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

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

Brian Loss commented on ACCUMULO-4169:
--------------------------------------

I'm ok with that solution too--I think it will work for our use case. However, I believe it
would be more flexible to have some configurable timeout for cleaning up contexts (cleanup
happens if the context is removed, or not used within the timeout). Then, setting a timeout
of 0 gives us the same solution. In a multi-tenant system where you might define contexts
for a number of users/applications, people might not want to leave contexts around for a long
time. Just a thought.

> 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