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 Wed, 23 Mar 2016 15:37:25 GMT

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

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

A possible work around on a running system is to add the context to an empty table to lock
it in memory.

The question is what constitutes a context "in use".  Since we can now specify the context
to use on an arbitrary scan, the concept of "in use" is somewhat fluid.

Perhaps the context should be cleaned out if it has not been used within some configurable
number of minutes.  Alternatively we say that a defined context constitutes it being "in use"
indefinitely.  I prefer the first option.

> 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