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 Wed, 23 Mar 2016 18:00:30 GMT

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

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

bq. The context object is created under the covers and has no direct API. A user can define/undefine
a context via the Accumulo configuration.

Thanks, I thought this was the case (glancing back at the original issue) but I wanted to
double-check. Do you think that would make sense long-term? Some additions to InstanceOperations
to manage contexts that isn't just "change the configuration" (the implementation could just
be doing configuration changes under the hood, but at least we'd have a clean/focused API
to interact with cp contexts)?

> 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