Accumulo-Integration-Tests - Build # 566 - Aborted! -- master
Accumulo-Integration-Tests - Build # 566 - Aborted: Check console output at https://secure.penguinsinabox.com/jenkins/job/Accumulo-Integration-Tests/566/ to view the results.
[jira] [Updated] (ACCUMULO-3509) Scanner lock cause Tablet lock, hence preventing idle scans from being swept, hence blocking SimpleTimer thread
[ https://issues.apache.org/jira/browse/ACCUMULO-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated ACCUMULO-3509: - Resolution: Fixed Status: Resolved (was: Patch Available) Thanks again for the fix, [~phrocker]! I did have a bit of merge conflict to resolve from 1.6 to 1.7. Please give it a glance to make sure I didn't mess anything up: https://github.com/apache/accumulo/commit/656282825ad0eb4ee51052e71492a3d3fd5c1f02 > Scanner lock cause Tablet lock, hence preventing idle scans from being swept, > hence blocking SimpleTimer thread > > > Key: ACCUMULO-3509 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3509 > Project: Accumulo > Issue Type: Bug > Components: tserver >Affects Versions: 1.6.0 >Reporter: marco polo >Assignee: marco polo > Fix For: 1.6.5, 1.7.1, 1.8.0 > > Attachments: ACCUMULO-3509-1.6.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > Synchronization with Tablet$Scanner via a read() will block close() being > called via the sweep method in TabletServer. As a result, the SimpleTimer > thread does not continue, and idle threads grow until the scan completes. > My patch, which is forthcoming, converts synchronized methods to use a fair > lock. If the lock is held by a read call, the close call will attempt to > obtain it, time out, and return indicating a close was not successful. The > sweep will continue, and the SimpleTimer thread will respawn later, > attempting closure on those Tablets at a later time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Accumulo-Integration-Tests - Build # 567 - Still unstable! -- 1.6
Accumulo-Integration-Tests - Build # 567 - Still unstable: Check console output at https://secure.penguinsinabox.com/jenkins/job/Accumulo-Integration-Tests/567/ to view the results.
[jira] [Updated] (ACCUMULO-4098) ConditionalWriterIT is failing
[
https://issues.apache.org/jira/browse/ACCUMULO-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Turner updated ACCUMULO-4098:
---
Attachment: (was: ACCUMULO-4098-1.patch)
> ConditionalWriterIT is failing
> --
>
> Key: ACCUMULO-4098
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4098
> Project: Accumulo
> Issue Type: Bug
>Reporter: Keith Turner
>Assignee: Keith Turner
>Priority: Blocker
> Fix For: 1.6.5, 1.7.1, 1.8.0
>
>
> I noticed that the ConditionalWriterIT was failing in master. Using the
> following command with {{git bisect}} I tracked it down to commit {{3af75fc}}
> for ACCUMULO-4077 as the change which broke the IT. Have not looked into why
> its failing yet.
> {noformat}
> mvn clean verify -Dit.test=ConditionalWriterIT -Dfindbugs.skip
> -Dcheckstyle.skip -Dtest=foo -DfailIfNoTests=false
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ACCUMULO-4098) ConditionalWriterIT is failing
[
https://issues.apache.org/jira/browse/ACCUMULO-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Turner updated ACCUMULO-4098:
---
Attachment: ACCUMULO-4098-1.6.patch
> ConditionalWriterIT is failing
> --
>
> Key: ACCUMULO-4098
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4098
> Project: Accumulo
> Issue Type: Bug
>Reporter: Keith Turner
>Assignee: Keith Turner
>Priority: Blocker
> Fix For: 1.6.5, 1.7.1, 1.8.0
>
> Attachments: ACCUMULO-4098-1.6.patch
>
>
> I noticed that the ConditionalWriterIT was failing in master. Using the
> following command with {{git bisect}} I tracked it down to commit {{3af75fc}}
> for ACCUMULO-4077 as the change which broke the IT. Have not looked into why
> its failing yet.
> {noformat}
> mvn clean verify -Dit.test=ConditionalWriterIT -Dfindbugs.skip
> -Dcheckstyle.skip -Dtest=foo -DfailIfNoTests=false
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ACCUMULO-4098) ConditionalWriterIT is failing
[
https://issues.apache.org/jira/browse/ACCUMULO-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Turner updated ACCUMULO-4098:
---
Attachment: ACCUMULO-4098-1.patch
I was cursing the thrift upgrade when I bumped into this, but upon
investigation I discovered that the thrift upgrade uncovered a problem in
Accumulo. The problem exists in 1.6 onward.
> ConditionalWriterIT is failing
> --
>
> Key: ACCUMULO-4098
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4098
> Project: Accumulo
> Issue Type: Bug
>Reporter: Keith Turner
>Assignee: Keith Turner
>Priority: Blocker
> Fix For: 1.8.0
>
> Attachments: ACCUMULO-4098-1.patch
>
>
> I noticed that the ConditionalWriterIT was failing in master. Using the
> following command with {{git bisect}} I tracked it down to commit {{3af75fc}}
> for ACCUMULO-4077 as the change which broke the IT. Have not looked into why
> its failing yet.
> {noformat}
> mvn clean verify -Dit.test=ConditionalWriterIT -Dfindbugs.skip
> -Dcheckstyle.skip -Dtest=foo -DfailIfNoTests=false
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4098) ConditionalWriterIT is failing
[
https://issues.apache.org/jira/browse/ACCUMULO-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15093256#comment-15093256
]
Keith Turner commented on ACCUMULO-4098:
In 1.8 there are two other problematic methods that call
ByteBuffer.arrayOffset. Don't think these exist in 1.6. I am thinking of
fixing those as I merge forward.
> ConditionalWriterIT is failing
> --
>
> Key: ACCUMULO-4098
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4098
> Project: Accumulo
> Issue Type: Bug
>Reporter: Keith Turner
>Assignee: Keith Turner
>Priority: Blocker
> Fix For: 1.8.0
>
> Attachments: ACCUMULO-4098-1.patch
>
>
> I noticed that the ConditionalWriterIT was failing in master. Using the
> following command with {{git bisect}} I tracked it down to commit {{3af75fc}}
> for ACCUMULO-4077 as the change which broke the IT. Have not looked into why
> its failing yet.
> {noformat}
> mvn clean verify -Dit.test=ConditionalWriterIT -Dfindbugs.skip
> -Dcheckstyle.skip -Dtest=foo -DfailIfNoTests=false
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Accumulo-1.6 - Build # 943 - Failure
The Apache Jenkins build system has built Accumulo-1.6 (build #943) Status: Failure Check console output at https://builds.apache.org/job/Accumulo-1.6/943/ to view the results.
Accumulo-Integration-Tests - Build # 568 - Aborted! -- 1.7
Accumulo-Integration-Tests - Build # 568 - Aborted: Check console output at https://secure.penguinsinabox.com/jenkins/job/Accumulo-Integration-Tests/568/ to view the results.
[jira] [Commented] (ACCUMULO-4106) Update documentation for new Git tag archival ASF policy
[
https://issues.apache.org/jira/browse/ACCUMULO-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15093143#comment-15093143
]
Christopher Tubbs commented on ACCUMULO-4106:
-
Also needed {{maven-release-plugin}} to be updated for the new
{{tagNameFormat}}, which is done now.
> Update documentation for new Git tag archival ASF policy
>
>
> Key: ACCUMULO-4106
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4106
> Project: Accumulo
> Issue Type: Task
>Reporter: Josh Elser
>Assignee: Josh Elser
> Fix For: 1.6.5, 1.7.1, 1.8.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> From Infra:
> {quote}
> Second, we've changed the 'protected' portions of git to primarily
> focus on refs/tags/rel - thus any tags under rel, will have their
> entire commit history. This provides the provenance that the ASF needs
> for releases, while still giving projects the ability to mold their
> repository in the way they see fit.
> Thus when a release vote is successful - part of the release process
> should become tagging the voted upon commit SHA under rel/ to make it
> indelible. ('# git tag rel/v15.4.2 ' or something similar.)
> {quote}
> Make sure our documentation and scripts correctly tell us to make the final
> tag start with "rel/"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ACCUMULO-3509) Scanner lock cause Tablet lock, hence preventing idle scans from being swept, hence blocking SimpleTimer thread
[ https://issues.apache.org/jira/browse/ACCUMULO-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15093313#comment-15093313 ] ASF GitHub Bot commented on ACCUMULO-3509: -- Github user asfgit closed the pull request at: https://github.com/apache/accumulo/pull/62 > Scanner lock cause Tablet lock, hence preventing idle scans from being swept, > hence blocking SimpleTimer thread > > > Key: ACCUMULO-3509 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3509 > Project: Accumulo > Issue Type: Bug > Components: tserver >Affects Versions: 1.6.0 >Reporter: marco polo >Assignee: marco polo > Fix For: 1.6.5, 1.7.1, 1.8.0 > > Attachments: ACCUMULO-3509-1.6.patch > > Time Spent: 0.5h > Remaining Estimate: 0h > > Synchronization with Tablet$Scanner via a read() will block close() being > called via the sweep method in TabletServer. As a result, the SimpleTimer > thread does not continue, and idle threads grow until the scan completes. > My patch, which is forthcoming, converts synchronized methods to use a fair > lock. If the lock is held by a read call, the close call will attempt to > obtain it, time out, and return indicating a close was not successful. The > sweep will continue, and the SimpleTimer thread will respawn later, > attempting closure on those Tablets at a later time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4109) Make build.sh create branches
[
https://issues.apache.org/jira/browse/ACCUMULO-4109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15093190#comment-15093190
]
Christopher Tubbs commented on ACCUMULO-4109:
-
For example, build.sh could:
# prompt for release candidate sequence number, {{n}}
# create a branch {{b-RCn-next}} from current branch, {{b}}
# switch to {{b-RCn-next}}
# run {{mvn clean release:clean release:prepare release:perform}}
# verify branch {{b}} is the same as {{HEAD~2}} and that {{HEAD}} and
{{HEAD~1}} contain "\[maven-release-plugin\]"
# create branch {{b-RCn}} to vote on, from {{HEAD~1}}
# delete tag matching {{HEAD~1}}
# verify origin matches {{https://git-wip-us.apache.org/repos/asf/accumulo}}
# push {{b-RCn}} (to vote on and make official signed tag from) and
{{b-RCn-next}} (to merge into {{b}} if vote passes to bump the version number)
It should handle failure cases (such as when {{release:perform}} fails after
the tag is created), to clean up any branches/tags, so they don't get
accidentally pushed.
> Make build.sh create branches
> -
>
> Key: ACCUMULO-4109
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4109
> Project: Accumulo
> Issue Type: Task
> Components: build
>Reporter: Christopher Tubbs
>Assignee: Christopher Tubbs
> Fix For: 1.6.5, 1.7.1, 1.8.0
>
>
> To make generating release candidates even easier, the {{build.sh}} script
> could be improved to automatically create and push branches to vote on (and
> to delete the local rel/version tag so it doesn't accidentally get pushed).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4098) ConditionalWriterIT is failing
[
https://issues.apache.org/jira/browse/ACCUMULO-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15093301#comment-15093301
]
Hadoop QA commented on ACCUMULO-4098:
-
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
46s {color} | {color:green} 1.6 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 39s
{color} | {color:green} 1.6 passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 28s
{color} | {color:green} 1.6 passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
51s {color} | {color:green} 1.6 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
19s {color} | {color:green} 1.6 passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 1m
46s {color} | {color:green} 1.6 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 30s
{color} | {color:green} 1.6 passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 41s
{color} | {color:green} 1.6 passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m
32s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 42s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 42s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 30s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 30s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m
54s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
14s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 0s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 27s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 42s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 8m 36s
{color} | {color:green} root in the patch passed with JDK v1.8.0. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 8m 26s
{color} | {color:green} root in the patch passed with JDK v1.7.0_79. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
6s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 30m 37s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12781732/ACCUMULO-4098-1.6.patch
|
| JIRA Issue | ACCUMULO-4098 |
| Optional Tests | asflicense javac javadoc unit findbugs checkstyle
compile |
| uname | Linux asf909.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-ACCUMULO-Build/test_framework/apache-yetus-6ce890b/precommit/personality/accumulo.sh
|
| git revision | 1.6 / 567f52f |
| Default Java | 1.7.0_79 |
| Multi-JDK versions | /home/jenkins/tools/java/jdk1.8.0:1.8.0
/usr/local/jenkins/java/jdk1.7.0_79:1.7.0_79 |
| findbugs | v2.0.3 |
| JDK v1.7.0_79 Test Results |
https://builds.apache.org/job/PreCommit-ACCUMULO-Build/15/testReport/ |
| modules | C: core U: core |
| Max memory used | 96MB |
| Powered by | Apache Yetus 0.2.0-SNAPSHOT http://yetus.apache.org |
| Console output |
https://builds.apache.org/job/PreCommit-ACCUMULO-Build/15/console |
This message
[jira] [Created] (ACCUMULO-4109) Make build.sh create branches
Christopher Tubbs created ACCUMULO-4109:
---
Summary: Make build.sh create branches
Key: ACCUMULO-4109
URL: https://issues.apache.org/jira/browse/ACCUMULO-4109
Project: Accumulo
Issue Type: Task
Components: build
Reporter: Christopher Tubbs
Assignee: Christopher Tubbs
Fix For: 1.6.5, 1.7.1, 1.8.0
To make generating release candidates even easier, the {{build.sh}} script
could be improved to automatically create and push branches to vote on (and to
delete the local rel/version tag so it doesn't accidentally get pushed).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ACCUMULO-4098) ConditionalWriterIT is failing
[
https://issues.apache.org/jira/browse/ACCUMULO-4098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Turner updated ACCUMULO-4098:
---
Fix Version/s: 1.7.1
1.6.5
Status: Patch Available (was: Open)
> ConditionalWriterIT is failing
> --
>
> Key: ACCUMULO-4098
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4098
> Project: Accumulo
> Issue Type: Bug
>Reporter: Keith Turner
>Assignee: Keith Turner
>Priority: Blocker
> Fix For: 1.6.5, 1.7.1, 1.8.0
>
> Attachments: ACCUMULO-4098-1.patch
>
>
> I noticed that the ConditionalWriterIT was failing in master. Using the
> following command with {{git bisect}} I tracked it down to commit {{3af75fc}}
> for ACCUMULO-4077 as the change which broke the IT. Have not looked into why
> its failing yet.
> {noformat}
> mvn clean verify -Dit.test=ConditionalWriterIT -Dfindbugs.skip
> -Dcheckstyle.skip -Dtest=foo -DfailIfNoTests=false
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4095) ShellServerIT#listscans failing due to null client
[
https://issues.apache.org/jira/browse/ACCUMULO-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15092713#comment-15092713
]
ASF GitHub Bot commented on ACCUMULO-4095:
--
Github user asfgit closed the pull request at:
https://github.com/apache/accumulo/pull/63
> ShellServerIT#listscans failing due to null client
> --
>
> Key: ACCUMULO-4095
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4095
> Project: Accumulo
> Issue Type: Bug
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Blocker
> Fix For: 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> root@miniInstance listscans> listscans
> TABLET SERVER| CLIENT | AGE | LAST | STATE |
> TYPE | USER| TABLE | COLUMNS | AUTHORIZATIONS | TABLET|
> SCAN ID| ITERATORS| ITERATOR OPTIONS
> hw10447.local:53868 | null | 9ms | 9ms |RUNNING
> |SINGLE |root |listscans |[] | | 2<< |
> 4790077908898785386
> |[SlowIterator=30,org.apache.accumulo.test.functional.SlowIterator] |
> {SlowIterator={sleepTime=500}}
> {noformat}
> Note that the client column has a value of "null". This is causing the test
> to fail. Seems to only be happening on master.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (ACCUMULO-4095) ShellServerIT#listscans failing due to null client
[
https://issues.apache.org/jira/browse/ACCUMULO-4095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated ACCUMULO-4095:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> ShellServerIT#listscans failing due to null client
> --
>
> Key: ACCUMULO-4095
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4095
> Project: Accumulo
> Issue Type: Bug
>Reporter: Josh Elser
>Assignee: Josh Elser
>Priority: Blocker
> Fix For: 1.8.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> root@miniInstance listscans> listscans
> TABLET SERVER| CLIENT | AGE | LAST | STATE |
> TYPE | USER| TABLE | COLUMNS | AUTHORIZATIONS | TABLET|
> SCAN ID| ITERATORS| ITERATOR OPTIONS
> hw10447.local:53868 | null | 9ms | 9ms |RUNNING
> |SINGLE |root |listscans |[] | | 2<< |
> 4790077908898785386
> |[SlowIterator=30,org.apache.accumulo.test.functional.SlowIterator] |
> {SlowIterator={sleepTime=500}}
> {noformat}
> Note that the client column has a value of "null". This is causing the test
> to fail. Seems to only be happening on master.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ACCUMULO-4108) 5 seconds is too small of a ZooKeeper session timeout for tests
Josh Elser created ACCUMULO-4108:
Summary: 5 seconds is too small of a ZooKeeper session timeout for
tests
Key: ACCUMULO-4108
URL: https://issues.apache.org/jira/browse/ACCUMULO-4108
Project: Accumulo
Issue Type: Bug
Components: test
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 1.6.5, 1.7.1, 1.8.0
Running tests on my laptop, I often get failures like follows:
{noformat}
largeTest(org.apache.accumulo.test.functional.ReadWriteIT) Time elapsed:
18.952 sec <<< FAILURE!
java.lang.AssertionError: Could not connect to Accumulo: Failed to connect to
zookeeper (localhost:56307) within 2x zookeeper timeout period 5000
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.accumulo.harness.AccumuloClusterHarness.getConnector(AccumuloClusterHarness.java:310)
at
org.apache.accumulo.test.functional.ReadWriteIT.largeTest(ReadWriteIT.java:320)
localityGroupChange(org.apache.accumulo.test.functional.ReadWriteIT) Time
elapsed: 17.767 sec <<< FAILURE!
java.lang.AssertionError: Could not connect to Accumulo: Failed to connect to
zookeeper (localhost:56598) within 2x zookeeper timeout period 5000
at org.junit.Assert.fail(Assert.java:88)
at
org.apache.accumulo.harness.AccumuloClusterHarness.getConnector(AccumuloClusterHarness.java:310)
at
org.apache.accumulo.test.functional.ReadWriteIT.localityGroupChange(ReadWriteIT.java:447)
{noformat}
This is a bit ridiculous. We should not be affecting the stability of the tests
just to get them to run faster sometimes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (ACCUMULO-4107) Need metrics on conditional mutations
Keith Turner created ACCUMULO-4107: -- Summary: Need metrics on conditional mutations Key: ACCUMULO-4107 URL: https://issues.apache.org/jira/browse/ACCUMULO-4107 Project: Accumulo Issue Type: Improvement Reporter: Keith Turner Tracking down uneven load in Fluo applications would be much easier if Accumulo reported some per tablet server conditional mutation metrics. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4107) Need metrics on conditional mutations
[ https://issues.apache.org/jira/browse/ACCUMULO-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15092287#comment-15092287 ] Keith Turner commented on ACCUMULO-4107: I'm thinking of Hadoop metrics2-level reporting > Need metrics on conditional mutations > - > > Key: ACCUMULO-4107 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4107 > Project: Accumulo > Issue Type: Improvement >Reporter: Keith Turner > > Tracking down uneven load in Fluo applications would be much easier if > Accumulo reported some per tablet server conditional mutation metrics. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (ACCUMULO-4075) Enable automated PreCommit testing
[
https://issues.apache.org/jira/browse/ACCUMULO-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved ACCUMULO-4075.
--
Resolution: Fixed
Per infra:
{quote}
ACCUMULO has now been added to the pre commit filter, the jenkins job will
start getting kicked off when the patch-available flag is set on your tickets
{quote}
> Enable automated PreCommit testing
> --
>
> Key: ACCUMULO-4075
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4075
> Project: Accumulo
> Issue Type: Task
>Reporter: Josh Elser
>Assignee: Josh Elser
>
> I've been lamenting the lack of automated PreCommit testing in Accumulo that
> both we as developers and our contributors can rely on to report for code
> quality.
> Now that [Yetus|http://yetus.apache.org/] has made a release, I think we
> should look in earnest to getting something set up for patches applied to
> JIRA. We already have some Jenkins automation for PullRequests, but it would
> be nice to swap that out in favor of Yetus (so that we have one single
> PreCommit "entry point").
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4107) Need metrics on conditional mutations
[ https://issues.apache.org/jira/browse/ACCUMULO-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15092281#comment-15092281 ] Josh Elser commented on ACCUMULO-4107: -- Are you thinking Hadoop metrics2-level reporting or something in the monitor (akin to the normal ingest rate graph)? > Need metrics on conditional mutations > - > > Key: ACCUMULO-4107 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4107 > Project: Accumulo > Issue Type: Improvement >Reporter: Keith Turner > > Tracking down uneven load in Fluo applications would be much easier if > Accumulo reported some per tablet server conditional mutation metrics. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-3509) Scanner lock cause Tablet lock, hence preventing idle scans from being swept, hence blocking SimpleTimer thread
[
https://issues.apache.org/jira/browse/ACCUMULO-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15092461#comment-15092461
]
Hadoop QA commented on ACCUMULO-3509:
-
| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s {color} | {color:green} The patch appears to include 2 new or modified test
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 2m
34s {color} | {color:green} 1.6 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 35s
{color} | {color:green} 1.6 passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 3s
{color} | {color:green} 1.6 passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
12s {color} | {color:green} 1.6 passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
43s {color} | {color:green} 1.6 passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
23s {color} | {color:green} 1.6 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 58s
{color} | {color:green} 1.6 passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 8s
{color} | {color:green} 1.6 passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m
12s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 26s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 26s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 3s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 3s
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
10s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m
39s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s {color} | {color:green} Patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 3m
55s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 2s
{color} | {color:green} the patch passed with JDK v1.8.0 {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 1m 6s
{color} | {color:green} the patch passed with JDK v1.7.0_79 {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 8m 0s
{color} | {color:green} root in the patch passed with JDK v1.8.0. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 8m 11s
{color} | {color:green} root in the patch passed with JDK v1.7.0_79. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
16s {color} | {color:green} Patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 41m 40s {color}
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | ACCUMULO-3509 |
| GITHUB PR | https://github.com/apache/accumulo/pull/62 |
| Optional Tests | asflicense javac javadoc unit findbugs checkstyle
compile |
| uname | Linux asf904.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality |
/home/jenkins/jenkins-slave/workspace/PreCommit-ACCUMULO-Build/test_framework/apache-yetus-6ce890b/precommit/personality/accumulo.sh
|
| git revision | 1.6 / 8669215 |
| Default Java | 1.7.0_79 |
| Multi-JDK versions | /home/jenkins/tools/java/jdk1.8.0:1.8.0
/usr/local/jenkins/java/jdk1.7.0_79:1.7.0_79 |
| findbugs | v2.0.3 |
| JDK v1.7.0_79 Test Results |
https://builds.apache.org/job/PreCommit-ACCUMULO-Build/14/testReport/ |
| modules | C: core server/tserver test U: . |
| Max memory used | 96MB |
| Powered by | Apache Yetus 0.2.0-SNAPSHOT http://yetus.apache.org |
| Console output |
https://builds.apache.org/job/PreCommit-ACCUMULO-Build/14/console |
| Console output |
[jira] [Commented] (ACCUMULO-4075) Enable automated PreCommit testing
[ https://issues.apache.org/jira/browse/ACCUMULO-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15092385#comment-15092385 ] Sean Busbey commented on ACCUMULO-4075: --- FYI, I found a bug in how HBase's precommit job was handling having a cached yetus install. Essentially if there was a cached install it failed to set the path to the bin/lib parts; this meant that essentially every attempt to use the cached install failed. I updated the Accumulo job to fix the same error. > Enable automated PreCommit testing > -- > > Key: ACCUMULO-4075 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4075 > Project: Accumulo > Issue Type: Task >Reporter: Josh Elser >Assignee: Josh Elser > > I've been lamenting the lack of automated PreCommit testing in Accumulo that > both we as developers and our contributors can rely on to report for code > quality. > Now that [Yetus|http://yetus.apache.org/] has made a release, I think we > should look in earnest to getting something set up for patches applied to > JIRA. We already have some Jenkins automation for PullRequests, but it would > be nice to swap that out in favor of Yetus (so that we have one single > PreCommit "entry point"). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-3509) Scanner lock cause Tablet lock, hence preventing idle scans from being swept, hence blocking SimpleTimer thread
[ https://issues.apache.org/jira/browse/ACCUMULO-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15092371#comment-15092371 ] Josh Elser commented on ACCUMULO-3509: -- Let's try to trigger Yetus: https://github.com/apache/accumulo/pull/62.patch > Scanner lock cause Tablet lock, hence preventing idle scans from being swept, > hence blocking SimpleTimer thread > > > Key: ACCUMULO-3509 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3509 > Project: Accumulo > Issue Type: Bug > Components: tserver >Affects Versions: 1.6.0 >Reporter: marco polo >Assignee: marco polo > Fix For: 1.6.5, 1.7.1, 1.8.0 > > > Synchronization with Tablet$Scanner via a read() will block close() being > called via the sweep method in TabletServer. As a result, the SimpleTimer > thread does not continue, and idle threads grow until the scan completes. > My patch, which is forthcoming, converts synchronized methods to use a fair > lock. If the lock is held by a read call, the close call will attempt to > obtain it, time out, and return indicating a close was not successful. The > sweep will continue, and the SimpleTimer thread will respawn later, > attempting closure on those Tablets at a later time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ACCUMULO-3509) Scanner lock cause Tablet lock, hence preventing idle scans from being swept, hence blocking SimpleTimer thread
[ https://issues.apache.org/jira/browse/ACCUMULO-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated ACCUMULO-3509: - Status: Patch Available (was: Open) > Scanner lock cause Tablet lock, hence preventing idle scans from being swept, > hence blocking SimpleTimer thread > > > Key: ACCUMULO-3509 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3509 > Project: Accumulo > Issue Type: Bug > Components: tserver >Reporter: marco polo >Assignee: marco polo > Fix For: 1.6.5, 1.7.1, 1.8.0 > > > Synchronization with Tablet$Scanner via a read() will block close() being > called via the sweep method in TabletServer. As a result, the SimpleTimer > thread does not continue, and idle threads grow until the scan completes. > My patch, which is forthcoming, converts synchronized methods to use a fair > lock. If the lock is held by a read call, the close call will attempt to > obtain it, time out, and return indicating a close was not successful. The > sweep will continue, and the SimpleTimer thread will respawn later, > attempting closure on those Tablets at a later time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4075) Enable automated PreCommit testing
[ https://issues.apache.org/jira/browse/ACCUMULO-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15092389#comment-15092389 ] Josh Elser commented on ACCUMULO-4075: -- bq. Essentially if there was a cached install it failed to set the path to the bin/lib parts; this meant that essentially every attempt to use the cached install failed Thanks! I had been struggling with that when creating the job. I appreciate you taking the time to fix the Accumulo job too. > Enable automated PreCommit testing > -- > > Key: ACCUMULO-4075 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4075 > Project: Accumulo > Issue Type: Task >Reporter: Josh Elser >Assignee: Josh Elser > > I've been lamenting the lack of automated PreCommit testing in Accumulo that > both we as developers and our contributors can rely on to report for code > quality. > Now that [Yetus|http://yetus.apache.org/] has made a release, I think we > should look in earnest to getting something set up for patches applied to > JIRA. We already have some Jenkins automation for PullRequests, but it would > be nice to swap that out in favor of Yetus (so that we have one single > PreCommit "entry point"). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ACCUMULO-3509) Scanner lock cause Tablet lock, hence preventing idle scans from being swept, hence blocking SimpleTimer thread
[ https://issues.apache.org/jira/browse/ACCUMULO-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated ACCUMULO-3509: - Attachment: ACCUMULO-3509-1.6.patch > Scanner lock cause Tablet lock, hence preventing idle scans from being swept, > hence blocking SimpleTimer thread > > > Key: ACCUMULO-3509 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3509 > Project: Accumulo > Issue Type: Bug > Components: tserver >Affects Versions: 1.6.0 >Reporter: marco polo >Assignee: marco polo > Fix For: 1.6.5, 1.7.1, 1.8.0 > > Attachments: ACCUMULO-3509-1.6.patch > > > Synchronization with Tablet$Scanner via a read() will block close() being > called via the sweep method in TabletServer. As a result, the SimpleTimer > thread does not continue, and idle threads grow until the scan completes. > My patch, which is forthcoming, converts synchronized methods to use a fair > lock. If the lock is held by a read call, the close call will attempt to > obtain it, time out, and return indicating a close was not successful. The > sweep will continue, and the SimpleTimer thread will respawn later, > attempting closure on those Tablets at a later time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4104) Move m2e config to profile
[
https://issues.apache.org/jira/browse/ACCUMULO-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15092548#comment-15092548
]
Christopher Tubbs commented on ACCUMULO-4104:
-
What are you doing to colorize? I use a bash function in {{~/.bashrc}}:
{code}
function mvn() {
trap 'echo -en "\e[m"' SIGHUP SIGINT SIGTERM
command mvn "$@" 2>&1 | awk '
BEGIN { IGNORECASE=1 }
/BUILD SUCCESS/ { print "\033[1;36m" $0 "\033[m" ; next }
/^\[FATAL\]/{ print "\033[1;31m" $0 "\033[m" ; next }
/^\[ERROR\]/{ print "\033[1;31m" $0 "\033[m" ; next }
/^\[TRACE\]/{ print "\033[2;33m" $0 "\033[m" ; next }
/^\[WARNING\]/ { print "\033[1;33m" $0 "\033[m" ; next }
/^\[DEBUG\]/{ print "\033[2;34m" $0 "\033[m" ; next }
/^\[INFO\]/ { print "\033[0;37m" $0 "\033[m" ; next }
/^\[ALL\]/ { print "\033[1;37m" $0 "\033[m" ; next }
{ print }
'
return ${PIPESTATUS[0]} ${pipestatus[1]}
}
{code}
> Move m2e config to profile
> --
>
> Key: ACCUMULO-4104
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4104
> Project: Accumulo
> Issue Type: Task
> Components: build
>Reporter: Christopher Tubbs
>Assignee: Christopher Tubbs
> Fix For: 1.6.5, 1.7.1, 1.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> m2e lifecycle pluginManagement configuration should be moved to a profile as
> described in http://stackoverflow.com/a/23707050 to eliminate unnecessary
> (and potentially confusing) warnings when building outside of eclipse.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4104) Move m2e config to profile
[ https://issues.apache.org/jira/browse/ACCUMULO-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15092558#comment-15092558 ] Christopher Tubbs commented on ACCUMULO-4104: - Nice! I hadn't tried the log4j2 stuff yet. Mine has problems with interactive input when making RCs (have to use /path/to/mvn instead... NBD). I'm guessing the new log4j2 stuff addresses that. > Move m2e config to profile > -- > > Key: ACCUMULO-4104 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4104 > Project: Accumulo > Issue Type: Task > Components: build >Reporter: Christopher Tubbs >Assignee: Christopher Tubbs > Fix For: 1.6.5, 1.7.1, 1.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > m2e lifecycle pluginManagement configuration should be moved to a profile as > described in http://stackoverflow.com/a/23707050 to eliminate unnecessary > (and potentially confusing) warnings when building outside of eclipse. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-3509) Scanner lock cause Tablet lock, hence preventing idle scans from being swept, hence blocking SimpleTimer thread
[ https://issues.apache.org/jira/browse/ACCUMULO-3509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15092526#comment-15092526 ] Josh Elser commented on ACCUMULO-3509: -- I will run this through some ITs and then merge today. Thanks in advance, [~phrocker]! > Scanner lock cause Tablet lock, hence preventing idle scans from being swept, > hence blocking SimpleTimer thread > > > Key: ACCUMULO-3509 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3509 > Project: Accumulo > Issue Type: Bug > Components: tserver >Affects Versions: 1.6.0 >Reporter: marco polo >Assignee: marco polo > Fix For: 1.6.5, 1.7.1, 1.8.0 > > Attachments: ACCUMULO-3509-1.6.patch > > > Synchronization with Tablet$Scanner via a read() will block close() being > called via the sweep method in TabletServer. As a result, the SimpleTimer > thread does not continue, and idle threads grow until the scan completes. > My patch, which is forthcoming, converts synchronized methods to use a fair > lock. If the lock is held by a read call, the close call will attempt to > obtain it, time out, and return indicating a close was not successful. The > sweep will continue, and the SimpleTimer thread will respawn later, > attempting closure on those Tablets at a later time. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ACCUMULO-4105) MiniAccumuloClusterConfigImpl doesn't implement MiniAccumuloClusterConfig
[ https://issues.apache.org/jira/browse/ACCUMULO-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Tubbs updated ACCUMULO-4105: Fix Version/s: (was: 2.0.0) 1.8.0 > MiniAccumuloClusterConfigImpl doesn't implement MiniAccumuloClusterConfig > - > > Key: ACCUMULO-4105 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4105 > Project: Accumulo > Issue Type: Bug > Components: mini >Affects Versions: 1.8.0 >Reporter: Jim Klucar >Priority: Minor > Fix For: 1.8.0 > > > I was launching MiniAccumuloCluster and needed to add a jar to the classpath. > MiniAccumuloClusterConfigImpl has a method setClasspathItems(String ...) that > I used for this purpose. Unfortunately since MiniAccumuloClusterConfigImpl > doesn't declare that it implements MiniAccumuloClusterConfig, I had to use > MiniAccumuloClusterImpl instead of MiniAccumuloCluster. Not sure what the > right solution is here. At the end of the day, explicitly adding things to > the classpath is the feature I needed. It was there, but not in the public > API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ACCUMULO-4104) Move m2e config to profile
[ https://issues.apache.org/jira/browse/ACCUMULO-4104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15092553#comment-15092553 ] Josh Elser commented on ACCUMULO-4104: -- I followed https://garygregory.wordpress.com/2015/03/23/watch-maven-in-color/ way back when. > Move m2e config to profile > -- > > Key: ACCUMULO-4104 > URL: https://issues.apache.org/jira/browse/ACCUMULO-4104 > Project: Accumulo > Issue Type: Task > Components: build >Reporter: Christopher Tubbs >Assignee: Christopher Tubbs > Fix For: 1.6.5, 1.7.1, 1.8.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > m2e lifecycle pluginManagement configuration should be moved to a profile as > described in http://stackoverflow.com/a/23707050 to eliminate unnecessary > (and potentially confusing) warnings when building outside of eclipse. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
