Accumulo-Integration-Tests - Build # 783 - Aborted! -- 1.7
Accumulo-Integration-Tests - Build # 783 - Aborted: Check console output at https://secure.penguinsinabox.com/jenkins/job/Accumulo-Integration-Tests/783/ to view the results.
Accumulo-Integration-Tests - Build # 782 - Unstable! -- 1.6
Accumulo-Integration-Tests - Build # 782 - Unstable: Check console output at https://secure.penguinsinabox.com/jenkins/job/Accumulo-Integration-Tests/782/ to view the results.
[jira] [Commented] (ACCUMULO-4169) TabletServer.config contextCleaner removes contexts that are not set on a table
[ https://issues.apache.org/jira/browse/ACCUMULO-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208902#comment-15208902 ] Ivan Bella commented on ACCUMULO-4169: -- bq. "in use" for a context would, I think, mean the call to Context.getClassLoader() by IteratorUtil.loadIterators or something else. You are not suggesting that we track the use of the actual classloader that is returned from the context are you? By "in use" I means the class loader for that context being used in a scan. So we just need a means to determine if there are any currently running scans using a particular context, or get all of the contexts being used by current scans. The routine that periodically checks for unused contexts would have to keep track of the contexts and the last time they appears to be used. I think this logic should be fairly simple. bq. Considering this, Dave's suggestion seems more reasonable to me (the lifetime of a context is defined by the presence of the configuration property). Is there a concern in taking that approach? The concern I have is that each class loader takes up perm-gen space. So cleaning them out if not being used seems prudent. > 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)
[jira] [Commented] (ACCUMULO-4169) TabletServer.config contextCleaner removes contexts that are not set on a table
[ 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)
[jira] [Commented] (ACCUMULO-4169) TabletServer.config contextCleaner removes contexts that are not set on a table
[ https://issues.apache.org/jira/browse/ACCUMULO-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208870#comment-15208870 ] Dave Marion commented on ACCUMULO-4169: --- bq. Do we have an API now for creating the context? The context object is created under the covers and has no direct API. A user can define/undefine a context via the Accumulo configuration. > 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)
[jira] [Commented] (ACCUMULO-4169) TabletServer.config contextCleaner removes contexts that are not set on a table
[ https://issues.apache.org/jira/browse/ACCUMULO-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208752#comment-15208752 ] Josh Elser commented on ACCUMULO-4169: -- bq. Suggesting that we have the context cleaner not close any context defined in the configuration. bq. Configurable time window to clean up if the context is unused w/in the window. If the time were set to a negative number, it could be treated as "infinite" time in which case it would only clean up the context when it is no longer defined Do we have an API now for creating the context? I'm just wondering how a user wanting to use a context for a scanner (not tied to a table) would (re)create a context that was cleaned up (if it still exists in the configuration). Considering this, Dave's suggestion seems more reasonable to me (the lifetime of a context is defined by the presence of the configuration property). Is there a concern in taking that approach? > 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)
[jira] [Commented] (ACCUMULO-4169) TabletServer.config contextCleaner removes contexts that are not set on a table
[ https://issues.apache.org/jira/browse/ACCUMULO-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208679#comment-15208679 ] Dave Marion commented on ACCUMULO-4169: --- "in use" for a context would, I think, mean the call to Context.getClassLoader() by IteratorUtil.loadIterators or something else. You are not suggesting that we track the use of the actual classloader that is returned from the context are you? > 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)
[jira] [Commented] (ACCUMULO-4169) TabletServer.config contextCleaner removes contexts that are not set on a table
[ https://issues.apache.org/jira/browse/ACCUMULO-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208616#comment-15208616 ] Brian Loss commented on ACCUMULO-4169: -- I like Ivan's idea. Configurable time window to clean up if the context is unused w/in the window. If the time were set to a negative number, it could be treated as "infinite" time in which case it would only clean up the context when it is no longer defined. This approach would still allow the scenario specified in the ticket description. > 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)
[jira] [Commented] (ACCUMULO-4169) TabletServer.config contextCleaner removes contexts that are not set on a table
[ 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)
[jira] [Updated] (ACCUMULO-4169) TabletServer.config contextCleaner removes contexts that are not set on a table
[ https://issues.apache.org/jira/browse/ACCUMULO-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Marion updated ACCUMULO-4169: -- Description: 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. > 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)
[jira] [Created] (ACCUMULO-4169) TabletServer.config contextCleaner removes contexts that are not set on a table
Dave Marion created ACCUMULO-4169: - Summary: 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Accumulo-Integration-Tests - Build # 781 - Aborted! -- master
Accumulo-Integration-Tests - Build # 781 - Aborted: Check console output at https://secure.penguinsinabox.com/jenkins/job/Accumulo-Integration-Tests/781/ to view the results.
