Accumulo-Integration-Tests - Build # 801 - Aborted! -- 1.7
Accumulo-Integration-Tests - Build # 801 - Aborted: Check console output at https://secure.penguinsinabox.com/jenkins/job/Accumulo-Integration-Tests/801/ to view the results.
Accumulo-Pull-Requests - Build # 234 - Fixed
The Apache Jenkins build system has built Accumulo-Pull-Requests (build #234) Status: Fixed Check console output at https://builds.apache.org/job/Accumulo-Pull-Requests/234/ to view the results.
[jira] [Commented] (ACCUMULO-4147) Add Accumulo Namespace Operations to Proxy
[ https://issues.apache.org/jira/browse/ACCUMULO-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217394#comment-15217394 ] ASF GitHub Bot commented on ACCUMULO-4147: -- Github user tristeng commented on the pull request: https://github.com/apache/accumulo/pull/74#issuecomment-203250036 I'm about to add in the 2 changes Keith suggested...should only take me a few minutes, and then however long it takes to run the tests. > Add Accumulo Namespace Operations to Proxy > -- > > Key: ACCUMULO-4147 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4147 > Project: Accumulo > Issue Type: Improvement > Components: proxy >Affects Versions: 1.7.1 >Reporter: Tristen Georgiou >Assignee: Tristen Georgiou >Priority: Minor > Fix For: 1.8.0 > > > The namespace operations are absent from the Accumulo proxy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4147) Add Accumulo Namespace Operations to Proxy
[ https://issues.apache.org/jira/browse/ACCUMULO-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217391#comment-15217391 ] ASF GitHub Bot commented on ACCUMULO-4147: -- Github user joshelser commented on the pull request: https://github.com/apache/accumulo/pull/74#issuecomment-203249840 @keith-turner do you have time to merge this in? I can try to swing around on it soon if not. > Add Accumulo Namespace Operations to Proxy > -- > > Key: ACCUMULO-4147 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4147 > Project: Accumulo > Issue Type: Improvement > Components: proxy >Affects Versions: 1.7.1 >Reporter: Tristen Georgiou >Assignee: Tristen Georgiou >Priority: Minor > Fix For: 1.8.0 > > > The namespace operations are absent from the Accumulo proxy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4004) open WALs prevent DN decommissioning
[ https://issues.apache.org/jira/browse/ACCUMULO-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217385#comment-15217385 ] Josh Elser commented on ACCUMULO-4004: -- Or if you know, Dave :) > open WALs prevent DN decommissioning > > > Key: ACCUMULO-4004 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4004 > Project: Accumulo > Issue Type: Improvement > Components: tserver >Reporter: Eric Newton >Assignee: Eric Newton > Fix For: 1.6.6, 1.7.2, 1.8.0 > > Attachments: ACCUMULO-4004-1.patch > > Time Spent: 10m > Remaining Estimate: 0h > > It should be possible to manually roll WALs so that files on decommissioning > datanodes are closed and the decommissioning process can complete. At the > very least, the logs could be closed after an elapsed period of time, such as > an hour. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4004) open WALs prevent DN decommissioning
[ https://issues.apache.org/jira/browse/ACCUMULO-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217383#comment-15217383 ] Josh Elser commented on ACCUMULO-4004: -- bq. Some folks I'm working with have been wanting this to make replication more predictive. Definitely a nice bonus which gets around a quick of the replication impl. bq. It should be possible to manually roll WALs so that files on decommissioning datanodes are closed and the decommissioning process can complete [~ecn], do you have an explanation for why we even need to do this? I'd like to better understand why we need to change our code. > open WALs prevent DN decommissioning > > > Key: ACCUMULO-4004 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4004 > Project: Accumulo > Issue Type: Improvement > Components: tserver >Reporter: Eric Newton >Assignee: Eric Newton > Fix For: 1.6.6, 1.7.2, 1.8.0 > > Attachments: ACCUMULO-4004-1.patch > > Time Spent: 10m > Remaining Estimate: 0h > > It should be possible to manually roll WALs so that files on decommissioning > datanodes are closed and the decommissioning process can complete. At the > very least, the logs could be closed after an elapsed period of time, such as > an hour. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACCUMULO-3364) Inconsistency between java and native map update within single mutation
[
https://issues.apache.org/jira/browse/ACCUMULO-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved ACCUMULO-3364.
--
Resolution: Duplicate
Fix Version/s: (was: 1.6.6)
(was: 1.7.2)
(was: 1.8.0)
Closing as duplicate of ACCUMULO-4148
> Inconsistency between java and native map update within single mutation
> ---
>
> Key: ACCUMULO-3364
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3364
> Project: Accumulo
> Issue Type: Bug
> Components: tserver
>Affects Versions: 1.6.1
>Reporter: Josh Elser
>Priority: Critical
>
> Noticed the following when I was poking around with
> {{ExamplesIT#testStatsCombiner}}:
> {code}
> String table = getUniqueNames(1)[0];
> c.tableOperations().create(table);
> is = new IteratorSetting(10, StatsCombiner.class);
> StatsCombiner.setCombineAllColumns(is, true);
> c.tableOperations().attachIterator(table, is);
> bw = c.createBatchWriter(table, bwc);
> Mutation m = new Mutation("foo");
> m.put("a", "b", "1");
> m.put("a", "b", "3");
> bw.addMutation(m);
> bw.flush();
> Iterator> iter = c.createScanner(table,
> Authorizations.EMPTY).iterator();
> assertTrue("Iterator had no results", iter.hasNext());
> Entry e = iter.next();
> assertEquals("Results ", "1,3,4,2", e.getValue().toString());
> {code}
> When run against the Java maps, the above succeeds as the test expects it to.
> However, this fails when the instance is using native maps.
> Talked to [~kturner] about this, and he noted that the Java maps [use a
> one-up counter when performing
> updates|https://github.com/apache/accumulo/blob/1.6.1/server/tserver/src/main/java/org/apache/accumulo/tserver/InMemoryMap.java#L404]
> whereas it does not appear that the NativeMap does this.
> The reason I got stuck on it is because I expected to see both updates
> because the StatsCombiner was running below the VersioningIterator, but I
> would only see a single Key-Value out of the scanner (a value of "3,3,3,1").
> My gut reaction is that we should have the same semantics across both Java
> and Native maps, although I'm not sure which one is correct/expected yet.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Accumulo-Integration-Tests - Build # 800 - Still unstable! -- 1.6
Accumulo-Integration-Tests - Build # 800 - Still unstable: Check console output at https://secure.penguinsinabox.com/jenkins/job/Accumulo-Integration-Tests/800/ 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=15216954#comment-15216954 ] Ivan Bella commented on ACCUMULO-4169: -- I believe I am ok with that solution. If a system owner is adding context definitions, then they need to ensure that the permgen (for Java 7) can handle at least that many classloaders concurrently. So change the code to only remove contexts that are not defined, and add the CMSClassUnloadingEnabled as a default flag in the environment. > 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-4004) open WALs prevent DN decommissioning
[ https://issues.apache.org/jira/browse/ACCUMULO-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216854#comment-15216854 ] William Slacum commented on ACCUMULO-4004: -- Thanks for the PR, Dave. Some folks I'm working with have been wanting this to make replication more predictive. > open WALs prevent DN decommissioning > > > Key: ACCUMULO-4004 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4004 > Project: Accumulo > Issue Type: Improvement > Components: tserver >Reporter: Eric Newton >Assignee: Eric Newton > Fix For: 1.6.6, 1.7.2, 1.8.0 > > Attachments: ACCUMULO-4004-1.patch > > Time Spent: 10m > Remaining Estimate: 0h > > It should be possible to manually roll WALs so that files on decommissioning > datanodes are closed and the decommissioning process can complete. At the > very least, the logs could be closed after an elapsed period of time, such as > an hour. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4004) open WALs prevent DN decommissioning
[ https://issues.apache.org/jira/browse/ACCUMULO-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216848#comment-15216848 ] ASF GitHub Bot commented on ACCUMULO-4004: -- Github user wjsl commented on the pull request: https://github.com/apache/accumulo/pull/84#issuecomment-203107908 I would assume they're under src/test in your repo :) > open WALs prevent DN decommissioning > > > Key: ACCUMULO-4004 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4004 > Project: Accumulo > Issue Type: Improvement > Components: tserver >Reporter: Eric Newton >Assignee: Eric Newton > Fix For: 1.6.6, 1.7.2, 1.8.0 > > Attachments: ACCUMULO-4004-1.patch > > Time Spent: 10m > Remaining Estimate: 0h > > It should be possible to manually roll WALs so that files on decommissioning > datanodes are closed and the decommissioning process can complete. At the > very least, the logs could be closed after an elapsed period of time, such as > an hour. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Accumulo-Pull-Requests - Build # 233 - Still Failing
The Apache Jenkins build system has built Accumulo-Pull-Requests (build #233) Status: Still Failing Check console output at https://builds.apache.org/job/Accumulo-Pull-Requests/233/ to view the results.
[jira] [Updated] (ACCUMULO-4173) Balance table within a set of hosts
[ https://issues.apache.org/jira/browse/ACCUMULO-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Marion updated ACCUMULO-4173: -- Attachment: ACCUMULO-4173-1.patch > Balance table within a set of hosts > --- > > Key: ACCUMULO-4173 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4173 > Project: Accumulo > Issue Type: Bug > Components: master >Reporter: Dave Marion >Assignee: Dave Marion > Labels: balancer > Fix For: 1.8.0 > > Attachments: ACCUMULO-4173-1.patch > > > Create a table balancer that will provide a set of hosts for the table tablet > balancer to use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ACCUMULO-4004) open WALs prevent DN decommissioning
[ https://issues.apache.org/jira/browse/ACCUMULO-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Marion updated ACCUMULO-4004: -- Attachment: ACCUMULO-4004-1.patch > open WALs prevent DN decommissioning > > > Key: ACCUMULO-4004 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4004 > Project: Accumulo > Issue Type: Improvement > Components: tserver >Reporter: Eric Newton >Assignee: Eric Newton > Fix For: 1.6.6, 1.7.2, 1.8.0 > > Attachments: ACCUMULO-4004-1.patch > > Time Spent: 10m > Remaining Estimate: 0h > > It should be possible to manually roll WALs so that files on decommissioning > datanodes are closed and the decommissioning process can complete. At the > very least, the logs could be closed after an elapsed period of time, such as > an hour. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4004) open WALs prevent DN decommissioning
[ https://issues.apache.org/jira/browse/ACCUMULO-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216755#comment-15216755 ] ASF GitHub Bot commented on ACCUMULO-4004: -- GitHub user dlmarion opened a pull request: https://github.com/apache/accumulo/pull/84 ACCUMULO-4004: Add new property for WALog max age, close log when age is reached. Didn't see any tests, anyone know where they are? You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/accumulo ACCUMULO-4004 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/accumulo/pull/84.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #84 commit f7d22c395a27ced9fa382b44162371d8b464988d Author: Dave Marion Date: 2016-03-29T20:02:38Z ACCUMULO-4004: Add new property for WALog max age, close log when age is reached. > open WALs prevent DN decommissioning > > > Key: ACCUMULO-4004 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4004 > Project: Accumulo > Issue Type: Improvement > Components: tserver >Reporter: Eric Newton >Assignee: Eric Newton > Fix For: 1.6.6, 1.7.2, 1.8.0 > > Time Spent: 10m > Remaining Estimate: 0h > > It should be possible to manually roll WALs so that files on decommissioning > datanodes are closed and the decommissioning process can complete. At the > very least, the logs could be closed after an elapsed period of time, such as > an hour. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4173) Balance table within a set of hosts
[ https://issues.apache.org/jira/browse/ACCUMULO-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216572#comment-15216572 ] ASF GitHub Bot commented on ACCUMULO-4173: -- Github user dlmarion commented on the pull request: https://github.com/apache/accumulo/pull/83#issuecomment-203039636 Jenkins failure is not due to the patch. > Balance table within a set of hosts > --- > > Key: ACCUMULO-4173 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4173 > Project: Accumulo > Issue Type: Bug > Components: master >Reporter: Dave Marion >Assignee: Dave Marion > Labels: balancer > Fix For: 1.8.0 > > > Create a table balancer that will provide a set of hosts for the table tablet > balancer to use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Accumulo-Pull-Requests - Build # 232 - Still Failing
The Apache Jenkins build system has built Accumulo-Pull-Requests (build #232) Status: Still Failing Check console output at https://builds.apache.org/job/Accumulo-Pull-Requests/232/ to view the results.
Accumulo-Pull-Requests - Build # 231 - Still Failing
The Apache Jenkins build system has built Accumulo-Pull-Requests (build #231) Status: Still Failing Check console output at https://builds.apache.org/job/Accumulo-Pull-Requests/231/ to view the results.
[jira] [Commented] (ACCUMULO-4171) Update to htrace-core4
[ https://issues.apache.org/jira/browse/ACCUMULO-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216487#comment-15216487 ] Sean Busbey commented on ACCUMULO-4171: --- The continued lack of concern in the htrace project around tracing during upgrades might also be an issue for us, since last I checked the expected implementation is "turn off the span receiver until you finish rolling upgrade to the new version, then turn it on." > Update to htrace-core4 > -- > > Key: ACCUMULO-4171 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4171 > Project: Accumulo > Issue Type: Improvement > Components: trace >Reporter: Mike Drob > Fix For: 1.8.0 > > > We are currently using HTrace 3.1.0-incubating. There were some API changes > and improvements on the way to HTrace 4.x-incubating, and we should stay up > to date with those changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4171) Update to htrace-core4
[ https://issues.apache.org/jira/browse/ACCUMULO-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216481#comment-15216481 ] Sean Busbey commented on ACCUMULO-4171: --- They didn't get a centralized span receiver until 4.1.0-incubating, so the first problem was just lack of tooling to actually process the spans written in files everywhere (and relying on a zipkin bridge was... not usable). Accumulo having its own span receiver and some tooling for presenting a summation of spans probably puts us in a unique position within the ecosystem wrt those early versions. > Update to htrace-core4 > -- > > Key: ACCUMULO-4171 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4171 > Project: Accumulo > Issue Type: Improvement > Components: trace >Reporter: Mike Drob > Fix For: 1.8.0 > > > We are currently using HTrace 3.1.0-incubating. There were some API changes > and improvements on the way to HTrace 4.x-incubating, and we should stay up > to date with those changes. -- 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=15216311#comment-15216311 ] Dave Marion commented on ACCUMULO-4169: --- [~bfloss] [~ivan.bella] I'd like to come to some consensus on the "in-use" issue. You have suggested removing contexts that don't have running scans that use them in an attempt to reduce the used perm gen space. [~ctubbsii] mentioned that perm gen space is not as big of an issue with Java 8 (and likely beyond). So, the question is, I think, is using -XX:+CMSClassUnloadingEnabled in Java 7 sufficient if we remove Contexts that are no longer 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] [Commented] (ACCUMULO-4171) Update to htrace-core4
[ https://issues.apache.org/jira/browse/ACCUMULO-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216237#comment-15216237 ] Billie Rinaldi commented on ACCUMULO-4171: -- Ah, that kind of makes sense. Do you recall why it seemed impossible to use? The only issue I encountered was that HDFS generates way too many spans, but we dealt with that in the Accumulo SpanReceiver by dropping the 0ms spans. > Update to htrace-core4 > -- > > Key: ACCUMULO-4171 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4171 > Project: Accumulo > Issue Type: Improvement > Components: trace >Reporter: Mike Drob > Fix For: 1.8.0 > > > We are currently using HTrace 3.1.0-incubating. There were some API changes > and improvements on the way to HTrace 4.x-incubating, and we should stay up > to date with those changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4171) Update to htrace-core4
[ https://issues.apache.org/jira/browse/ACCUMULO-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216223#comment-15216223 ] Sean Busbey commented on ACCUMULO-4171: --- When I've chatted with htrace and hadoop folks about the api stuff, especially changing versions in Hadoop 2.y, the common refrain is that tracing in Hadoop has been experimental and so they're not likely to settle until folks can see a solid story of what's going on inside Hadoop. FWIW, htrace-3 was practically impossible to actually use in practice for HDFS from what I remember. > Update to htrace-core4 > -- > > Key: ACCUMULO-4171 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4171 > Project: Accumulo > Issue Type: Improvement > Components: trace >Reporter: Mike Drob > Fix For: 1.8.0 > > > We are currently using HTrace 3.1.0-incubating. There were some API changes > and improvements on the way to HTrace 4.x-incubating, and we should stay up > to date with those changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Accumulo-Pull-Requests - Build # 230 - Still Failing
The Apache Jenkins build system has built Accumulo-Pull-Requests (build #230) Status: Still Failing Check console output at https://builds.apache.org/job/Accumulo-Pull-Requests/230/ to view the results.
[jira] [Commented] (ACCUMULO-4173) Balance table within a set of hosts
[ https://issues.apache.org/jira/browse/ACCUMULO-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216106#comment-15216106 ] ASF GitHub Bot commented on ACCUMULO-4173: -- GitHub user dlmarion opened a pull request: https://github.com/apache/accumulo/pull/83 ACCUMULO-4173: Host Regex Table Load Balancer A table load balancer that passes a subset of the tserver hosts to the configured tablet balancer for a table. Tservers that do not match any regex are part of a default pool. Tables with configured regex (or those that are in error) are balanced within the default pool of tservers. You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/accumulo ACCUMULO-4173 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/accumulo/pull/83.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #83 commit 594ecc3c6a876922b1a47301a619551e32c31e7a Author: Dave Marion Date: 2016-03-29T14:33:41Z Squashed commit of the following: commit 2afa820763ece3a1299ac9e8889532fa4966acff Author: Dave Marion Date: Fri Mar 25 14:36:18 2016 -0400 Added tests where tablets were either all assigned or partially assigned commit 9c08258b7907ad3195227d21a782ffe7545fa696 Author: Dave Marion Date: Fri Mar 25 14:26:57 2016 -0400 Added test for out of bounds tablets commit be07ba3d20e378d88c71f77366e1b3f2dd325c73 Author: Dave Marion Date: Fri Mar 25 13:38:35 2016 -0400 Added more tests commit dc842305d4fda77d2271ae8a111031bfb1eda9f7 Author: Dave Marion Date: Fri Mar 25 11:31:20 2016 -0400 Initial work on Host based regex master balancer > Balance table within a set of hosts > --- > > Key: ACCUMULO-4173 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4173 > Project: Accumulo > Issue Type: Bug > Components: master >Reporter: Dave Marion >Assignee: Dave Marion > Labels: balancer > Fix For: 1.8.0 > > > Create a table balancer that will provide a set of hosts for the table tablet > balancer to use. -- 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=15216092#comment-15216092 ] Dave Marion commented on ACCUMULO-4169: --- bq. A possible work around on a running system is to add the context to an empty table to lock it in memory. This workaround only works if you create splits for the empty table and a split is hosted on each tserver. > 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-4173) Balance table within a set of hosts
Dave Marion created ACCUMULO-4173: - Summary: Balance table within a set of hosts Key: ACCUMULO-4173 URL: https://issues.apache.org/jira/browse/ACCUMULO-4173 Project: Accumulo Issue Type: Bug Components: master Reporter: Dave Marion Assignee: Dave Marion Fix For: 1.8.0 Create a table balancer that will provide a set of hosts for the table tablet balancer to use. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4147) Add Accumulo Namespace Operations to Proxy
[ https://issues.apache.org/jira/browse/ACCUMULO-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215990#comment-15215990 ] ASF GitHub Bot commented on ACCUMULO-4147: -- Github user keith-turner commented on the pull request: https://github.com/apache/accumulo/pull/74#issuecomment-202890798 The changes look great. I am finished looking at this and have nothing else to add. > Add Accumulo Namespace Operations to Proxy > -- > > Key: ACCUMULO-4147 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4147 > Project: Accumulo > Issue Type: Improvement > Components: proxy >Affects Versions: 1.7.1 >Reporter: Tristen Georgiou >Assignee: Tristen Georgiou >Priority: Minor > Fix For: 1.8.0 > > > The namespace operations are absent from the Accumulo proxy. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4147) Add Accumulo Namespace Operations to Proxy
[
https://issues.apache.org/jira/browse/ACCUMULO-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215982#comment-15215982
]
ASF GitHub Bot commented on ACCUMULO-4147:
--
Github user keith-turner commented on a diff in the pull request:
https://github.com/apache/accumulo/pull/74#discussion_r57719585
--- Diff:
test/src/main/java/org/apache/accumulo/test/proxy/SimpleProxyBase.java ---
@@ -836,6 +1020,22 @@ public void testExists() throws Exception {
}
@Test
+ public void testNamespaceExists() throws Exception {
+try {
+ client.createNamespace(creds, namespaceName);
--- End diff --
Also, will this test pass if not exception is thrown?
> Add Accumulo Namespace Operations to Proxy
> --
>
> Key: ACCUMULO-4147
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4147
> Project: Accumulo
> Issue Type: Improvement
> Components: proxy
>Affects Versions: 1.7.1
>Reporter: Tristen Georgiou
>Assignee: Tristen Georgiou
>Priority: Minor
> Fix For: 1.8.0
>
>
> The namespace operations are absent from the Accumulo proxy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4147) Add Accumulo Namespace Operations to Proxy
[
https://issues.apache.org/jira/browse/ACCUMULO-4147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215981#comment-15215981
]
ASF GitHub Bot commented on ACCUMULO-4147:
--
Github user keith-turner commented on a diff in the pull request:
https://github.com/apache/accumulo/pull/74#discussion_r57719491
--- Diff:
test/src/main/java/org/apache/accumulo/test/proxy/SimpleProxyBase.java ---
@@ -818,6 +950,58 @@ public void tableNotFound() throws Exception {
}
@Test
+ public void namespaceNotFound() throws Exception {
+final String doesNotExist = "doesNotExists";
+try {
+ client.deleteNamespace(creds, doesNotExist);
--- End diff --
If this thrift call does not throw a NNFE, it seems like the test will
still pass? If this is the case, could place an Assert.fail() after each
thrift call thats supposed to throw.
> Add Accumulo Namespace Operations to Proxy
> --
>
> Key: ACCUMULO-4147
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4147
> Project: Accumulo
> Issue Type: Improvement
> Components: proxy
>Affects Versions: 1.7.1
>Reporter: Tristen Georgiou
>Assignee: Tristen Georgiou
>Priority: Minor
> Fix For: 1.8.0
>
>
> The namespace operations are absent from the Accumulo proxy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Accumulo-Integration-Tests - Build # 799 - Aborted! -- master
Accumulo-Integration-Tests - Build # 799 - Aborted: Check console output at https://secure.penguinsinabox.com/jenkins/job/Accumulo-Integration-Tests/799/ to view the results.
