[jira] [Resolved] (BOOKKEEPER-519) Ensure all threads in BookKeeper/Hedwig have meaningful names

2014-01-15 Thread Sijie Guo (JIRA) 

 [ 
https://issues.apache.org/jira/browse/BOOKKEEPER-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo resolved BOOKKEEPER-519.
--

Resolution: Won't Fix

grep the code base now, it seems that all the threads are already have 
meaningful now. so close the ticket now. we could re-open it when we found some 
threads need to add names.

> Ensure all threads in BookKeeper/Hedwig have meaningful names
> -
>
> Key: BOOKKEEPER-519
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-519
> Project: Bookkeeper
>  Issue Type: Bug
>  Components: bookkeeper-auto-recovery, bookkeeper-server, 
> hedwig-server
>Reporter: Ivan Kelly
> Fix For: 4.3.0
>
>
> As summary says, give them all names. They should also be unique within tests 
> so that debugging test failures is easier.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (BOOKKEEPER-661) Turn readonly back to writable if spaces are reclaimed.

2014-01-15 Thread Sijie Guo (JIRA) 

 [ 
https://issues.apache.org/jira/browse/BOOKKEEPER-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo updated BOOKKEEPER-661:
-

Attachment: BOOKKEEPER-661_662.diff

attach a patch with BOOKKEEPER-662 changes for precommit job.

> Turn readonly back to writable if spaces are reclaimed.
> ---
>
> Key: BOOKKEEPER-661
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-661
> Project: Bookkeeper
>  Issue Type: Improvement
>  Components: bookkeeper-server
>Reporter: Sijie Guo
>Assignee: Sijie Guo
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-661.diff, BOOKKEEPER-661.diff, 
> BOOKKEEPER-661_662.diff
>
>
> should be able to turn a bookie from readonly back to writable if the spaces 
> are reclaimed.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (BOOKKEEPER-661) Turn readonly back to writable if spaces are reclaimed.

2014-01-15 Thread Sijie Guo (JIRA) 

 [ 
https://issues.apache.org/jira/browse/BOOKKEEPER-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo updated BOOKKEEPER-661:
-

Attachment: BOOKKEEPER-661.diff

addressed comment. attach latest patch based on BOOKKEEPER-662.

> Turn readonly back to writable if spaces are reclaimed.
> ---
>
> Key: BOOKKEEPER-661
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-661
> Project: Bookkeeper
>  Issue Type: Improvement
>  Components: bookkeeper-server
>Reporter: Sijie Guo
>Assignee: Sijie Guo
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-661.diff, BOOKKEEPER-661.diff, 
> BOOKKEEPER-661_662.diff
>
>
> should be able to turn a bookie from readonly back to writable if the spaces 
> are reclaimed.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (BOOKKEEPER-662) Major GC should kick in immediately if remaining space reaches a warning threshold

2014-01-15 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on BOOKKEEPER-662:
--

Testing JIRA BOOKKEEPER-662


Patch 
[BOOKKEEPER-662.diff|https://issues.apache.org/jira/secure/attachment/12623085/BOOKKEEPER-662.diff]
 downloaded at Wed Jan 15 08:03:30 UTC 2014



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
120
.{color:green}+1{color} the patch does adds/modifies 4 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 FINDBUGS{color}
.{color:green}+1{color} the patch does not seem to introduce new Findbugs 
warnings
{color:green}+1 TESTS{color}
.Tests run: 887
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/bookkeeper-trunk-precommit-build/554/

> Major GC should kick in immediately if remaining space reaches a warning 
> threshold
> --
>
> Key: BOOKKEEPER-662
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-662
> Project: Bookkeeper
>  Issue Type: Improvement
>  Components: bookkeeper-server
>Reporter: Sijie Guo
>Assignee: Aniruddha
> Fix For: 4.3.0
>
> Attachments: 0001-WIP.patch, BOOKKEEPER-662.diff, 
> BOOKKEEPER-662.diff, BOOKKEEPER-662.diff
>
>
> in a high throughput case, Major GC should kick in immediately if remaining 
> spaces reaches a warning threshold.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (BOOKKEEPER-510) LedgerRecoveryOp updates metadata before it needs to

2014-01-15 Thread Sijie Guo (JIRA) 

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

Sijie Guo commented on BOOKKEEPER-510:
--

[~ikelly] I still don't understand. This issue seems not be a problem anymore.

- recovery only updates metadata when close since BOOKKEEPER-355
- recovery op keeps a copy of metadata for recovery reading in BOOKKEEPER-510.

Could you clarify what is the ticket for? if not an issue, shall we close it?

> LedgerRecoveryOp updates metadata before it needs to
> 
>
> Key: BOOKKEEPER-510
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-510
> Project: Bookkeeper
>  Issue Type: Bug
>  Components: bookkeeper-client
>Reporter: Ivan Kelly
> Fix For: 4.3.0
>
> Attachments: 
> 0002-BOOKKEEPER-510-LedgerRecoveryOp-updates-metadata-bef.patch
>
>
> This could lead to an issue if there are a lot of errors in a specific order.
> You have a ledger with ensemble (B1, B2, B3)
> # B1 brought down for maintenance
> # Ledger recovery started
> # B2 answers read last confirmed.
> # B1 replaced in ensemble by B4
> # Write to B4 fails for some reason
> # B1 comes back up.
> # B2 goes down for maintenance.
> # Ledger recovery starts (ledger is now unavailable)
> See BOOKKEEPER-355



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Comment Edited] (BOOKKEEPER-510) LedgerRecoveryOp updates metadata before it needs to

2014-01-15 Thread Sijie Guo (JIRA) 

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

Sijie Guo edited comment on BOOKKEEPER-510 at 1/15/14 8:48 AM:
---

[~ikelly] I still don't understand. This issue seems not be a problem anymore.

- recovery only updates metadata when close since BOOKKEEPER-355
- recovery op keeps a copy of metadata for recovery reading in BOOKKEEPER-581.

Could you clarify what is the ticket for? if not an issue, shall we close it?


was (Author: hustlmsp):
[~ikelly] I still don't understand. This issue seems not be a problem anymore.

- recovery only updates metadata when close since BOOKKEEPER-355
- recovery op keeps a copy of metadata for recovery reading in BOOKKEEPER-510.

Could you clarify what is the ticket for? if not an issue, shall we close it?

> LedgerRecoveryOp updates metadata before it needs to
> 
>
> Key: BOOKKEEPER-510
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-510
> Project: Bookkeeper
>  Issue Type: Bug
>  Components: bookkeeper-client
>Reporter: Ivan Kelly
> Fix For: 4.3.0
>
> Attachments: 
> 0002-BOOKKEEPER-510-LedgerRecoveryOp-updates-metadata-bef.patch
>
>
> This could lead to an issue if there are a lot of errors in a specific order.
> You have a ledger with ensemble (B1, B2, B3)
> # B1 brought down for maintenance
> # Ledger recovery started
> # B2 answers read last confirmed.
> # B1 replaced in ensemble by B4
> # Write to B4 fails for some reason
> # B1 comes back up.
> # B2 goes down for maintenance.
> # Ledger recovery starts (ledger is now unavailable)
> See BOOKKEEPER-355



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (BOOKKEEPER-661) Turn readonly back to writable if spaces are reclaimed.

2014-01-15 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on BOOKKEEPER-661:
--

Testing JIRA BOOKKEEPER-661


Patch 
[BOOKKEEPER-661_662.diff|https://issues.apache.org/jira/secure/attachment/12623092/BOOKKEEPER-661_662.diff]
 downloaded at Wed Jan 15 08:37:19 UTC 2014



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
120
.{color:green}+1{color} the patch does adds/modifies 5 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 FINDBUGS{color}
.{color:green}+1{color} the patch does not seem to introduce new Findbugs 
warnings
{color:green}+1 TESTS{color}
.Tests run: 888
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:green}*+1 Overall result, good!, no -1s*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/bookkeeper-trunk-precommit-build/555/

> Turn readonly back to writable if spaces are reclaimed.
> ---
>
> Key: BOOKKEEPER-661
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-661
> Project: Bookkeeper
>  Issue Type: Improvement
>  Components: bookkeeper-server
>Reporter: Sijie Guo
>Assignee: Sijie Guo
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-661.diff, BOOKKEEPER-661.diff, 
> BOOKKEEPER-661_662.diff
>
>
> should be able to turn a bookie from readonly back to writable if the spaces 
> are reclaimed.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (BOOKKEEPER-710) OpenLedgerNoRecovery should watch ensemble change.

2014-01-15 Thread Ivan Kelly (JIRA) 

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

Ivan Kelly commented on BOOKKEEPER-710:
---

How do you communicate the change in LAC to the client. The client will be 
still be polling by calling readLastAddConfirmed, no?

> OpenLedgerNoRecovery should watch ensemble change.
> --
>
> Key: BOOKKEEPER-710
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-710
> Project: Bookkeeper
>  Issue Type: Bug
>  Components: bookkeeper-client
>Reporter: Sijie Guo
>Assignee: Sijie Guo
>Priority: Blocker
> Fix For: 4.3.0, 4.2.3
>
> Attachments: BOOKKEEPER-710.diff
>
>
> LedgerHandle opened by openLedgerNoRecovery should watch ensemble change. 
> otherwise, readLastConfirmed & readEntries will stuck if there are ensemble 
> changes in the ledger.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (BOOKKEEPER-708) Shade protobuf library to avoid incompatible versions

2014-01-15 Thread Ivan Kelly (JIRA) 

 [ 
https://issues.apache.org/jira/browse/BOOKKEEPER-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Kelly updated BOOKKEEPER-708:
--

Attachment: 0001-BOOKKEEPER-708-Shade-protobuf-library-to-avoid-incom.patch

> Shade protobuf library to avoid incompatible versions
> -
>
> Key: BOOKKEEPER-708
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-708
> Project: Bookkeeper
>  Issue Type: Bug
>  Components: bookkeeper-server
>Reporter: Sijie Guo
>Assignee: Rakesh R
> Fix For: 4.3.0, 4.2.3
>
> Attachments: 
> 0001-BOOKKEEPER-708-Shade-protobuf-library-to-avoid-incom.patch, 
> 0001-BOOKKEEPER-708.patch, 0002-BOOKKEEPER-708.patch
>
>
> as offline discussion, we need to shade protobuf library for BKJM as hadoop 
> uses protobuf 2.5.
> this is planned on version 4.2.3 and 4.3.0.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (BOOKKEEPER-708) Shade protobuf library to avoid incompatible versions

2014-01-15 Thread Ivan Kelly (JIRA) 

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

Ivan Kelly commented on BOOKKEEPER-708:
---

I've set createDependencyReducedPom to true in a new patch. Regarding the jar 
in the dist bin package, I don't think it's easy to exclude it without hacking 
around it, any having it there does no harm. Shading the deps is only important 
for the client. The dist bin package is the server.

> Shade protobuf library to avoid incompatible versions
> -
>
> Key: BOOKKEEPER-708
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-708
> Project: Bookkeeper
>  Issue Type: Bug
>  Components: bookkeeper-server
>Reporter: Sijie Guo
>Assignee: Rakesh R
> Fix For: 4.3.0, 4.2.3
>
> Attachments: 
> 0001-BOOKKEEPER-708-Shade-protobuf-library-to-avoid-incom.patch, 
> 0001-BOOKKEEPER-708.patch, 0002-BOOKKEEPER-708.patch
>
>
> as offline discussion, we need to shade protobuf library for BKJM as hadoop 
> uses protobuf 2.5.
> this is planned on version 4.2.3 and 4.3.0.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (BOOKKEEPER-708) Shade protobuf library to avoid incompatible versions

2014-01-15 Thread Hadoop QA (JIRA) 

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

Hadoop QA commented on BOOKKEEPER-708:
--

Testing JIRA BOOKKEEPER-708


Patch 
[0001-BOOKKEEPER-708-Shade-protobuf-library-to-avoid-incom.patch|https://issues.apache.org/jira/secure/attachment/12623139/0001-BOOKKEEPER-708-Shade-protobuf-library-to-avoid-incom.patch]
 downloaded at Wed Jan 15 14:00:48 UTC 2014



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
120
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 FINDBUGS{color}
.{color:green}+1{color} the patch does not seem to introduce new Findbugs 
warnings
{color:green}+1 TESTS{color}
.Tests run: 885
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/bookkeeper-trunk-precommit-build/556/

> Shade protobuf library to avoid incompatible versions
> -
>
> Key: BOOKKEEPER-708
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-708
> Project: Bookkeeper
>  Issue Type: Bug
>  Components: bookkeeper-server
>Reporter: Sijie Guo
>Assignee: Rakesh R
> Fix For: 4.3.0, 4.2.3
>
> Attachments: 
> 0001-BOOKKEEPER-708-Shade-protobuf-library-to-avoid-incom.patch, 
> 0001-BOOKKEEPER-708.patch, 0002-BOOKKEEPER-708.patch
>
>
> as offline discussion, we need to shade protobuf library for BKJM as hadoop 
> uses protobuf 2.5.
> this is planned on version 4.2.3 and 4.3.0.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Build failed in Jenkins: bookkeeper-trunk #509

2014-01-15 Thread Apache Jenkins Server 
See 

Changes:

[ivank] BOOKKEEPER-662: Major GC should kick in immediately if remaining space 
reaches a warning threshold (sijie via ivank)

--
[...truncated 449 lines...]
[INFO] Compiling 6 source files to 

[INFO] 
[INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ 
hedwig-protocol ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.0:testCompile (default-testCompile) @ 
hedwig-protocol ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.9:test (default-test) @ hedwig-protocol ---
[INFO] Surefire report directory: 


---
 T E S T S
---

---
 T E S T S
---

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ hedwig-protocol ---
[INFO] Building jar: 

[INFO] 
[INFO] >>> findbugs-maven-plugin:2.5.2:check (default-cli) @ hedwig-protocol >>>
[INFO] 
[INFO] --- findbugs-maven-plugin:2.5.2:findbugs (findbugs) @ hedwig-protocol ---
[INFO] Fork Value is true
[INFO] Done FindBugs Analysis
[INFO] 
[INFO] <<< findbugs-maven-plugin:2.5.2:check (default-cli) @ hedwig-protocol <<<
[INFO] 
[INFO] --- findbugs-maven-plugin:2.5.2:check (default-cli) @ hedwig-protocol ---
[INFO] BugInstance size is 0
[INFO] Error size is 0
[INFO] No errors/warnings found
[INFO] 
[INFO] 
[INFO] Building bookkeeper-server 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bookkeeper-server ---
[INFO] 
[INFO] --- apache-rat-plugin:0.7:check (default-cli) @ bookkeeper-server ---
[INFO] Exclude: **/DataFormats.java
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.1:process (default) @ 
bookkeeper-server ---
[INFO] 
[INFO] --- maven-resources-plugin:2.4.3:resources (default-resources) @ 
bookkeeper-server ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ 
bookkeeper-server ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 159 source files to 

[INFO] 
[INFO] --- maven-resources-plugin:2.4.3:testResources (default-testResources) @ 
bookkeeper-server ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.0:testCompile (default-testCompile) @ 
bookkeeper-server ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 79 source files to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.9:test (default-test) @ bookkeeper-server ---
[INFO] Surefire report directory: 


---
 T E S T S
---

---
 T E S T S
---
Running org.apache.bookkeeper.replication.AutoRecoveryMainTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.167 sec
Running org.apache.bookkeeper.replication.BookieAutoRecoveryTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 28.589 sec
Running org.apache.bookkeeper.replication.BookieLedgerIndexTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 8.883 sec
Running org.apache.bookkeeper.replication.AuditorPeriodicCheckTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 15.802 sec
Running org.apache.bookkeeper.replication.AuditorLedgerCheckerTest
Tests run: 18, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 54.173 sec <<< 
FAILURE!
Running org.apache.bookkeeper.replication.TestLedgerUnderreplicationManager
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.492 se

[jira] [Commented] (BOOKKEEPER-662) Major GC should kick in immediately if remaining space reaches a warning threshold

2014-01-15 Thread Hudson (JIRA) 

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

Hudson commented on BOOKKEEPER-662:
---

FAILURE: Integrated in bookkeeper-trunk #509 (See 
[https://builds.apache.org/job/bookkeeper-trunk/509/])
BOOKKEEPER-662: Major GC should kick in immediately if remaining space reaches 
a warning threshold (sijie via ivank) (ivank: rev 1558410)
* /zookeeper/bookkeeper/trunk/CHANGES.txt
* 
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/Bookie.java
* 
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/EntryLogger.java
* 
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/GarbageCollectorThread.java
* 
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/IndexPersistenceMgr.java
* 
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/InterleavedLedgerStorage.java
* 
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/bookie/LedgerDirsManager.java
* 
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/conf/ServerConfiguration.java
* 
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/main/java/org/apache/bookkeeper/util/DiskChecker.java
* 
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/bookie/BookieInitializationTest.java
* 
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/bookie/CompactionTest.java
* 
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/bookie/TestSyncThread.java
* 
/zookeeper/bookkeeper/trunk/bookkeeper-server/src/test/java/org/apache/bookkeeper/util/TestDiskChecker.java


> Major GC should kick in immediately if remaining space reaches a warning 
> threshold
> --
>
> Key: BOOKKEEPER-662
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-662
> Project: Bookkeeper
>  Issue Type: Improvement
>  Components: bookkeeper-server
>Reporter: Sijie Guo
>Assignee: Aniruddha
> Fix For: 4.3.0
>
> Attachments: 0001-WIP.patch, BOOKKEEPER-662.diff, 
> BOOKKEEPER-662.diff, BOOKKEEPER-662.diff
>
>
> in a high throughput case, Major GC should kick in immediately if remaining 
> spaces reaches a warning threshold.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (BOOKKEEPER-662) Major GC should kick in immediately if remaining space reaches a warning threshold

2014-01-15 Thread Flavio Junqueira (JIRA) 

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

Flavio Junqueira commented on BOOKKEEPER-662:
-

It is possibly not related to the committed patch, but this test case failed 
according to build 509:

org.apache.bookkeeper.replication.AuditorLedgerCheckerTest.testToggleLedgerReplication[2]

> Major GC should kick in immediately if remaining space reaches a warning 
> threshold
> --
>
> Key: BOOKKEEPER-662
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-662
> Project: Bookkeeper
>  Issue Type: Improvement
>  Components: bookkeeper-server
>Reporter: Sijie Guo
>Assignee: Aniruddha
> Fix For: 4.3.0
>
> Attachments: 0001-WIP.patch, BOOKKEEPER-662.diff, 
> BOOKKEEPER-662.diff, BOOKKEEPER-662.diff
>
>
> in a high throughput case, Major GC should kick in immediately if remaining 
> spaces reaches a warning threshold.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Re: hedwig-client-jms build failing

2014-01-15 Thread Flavio Junqueira 
This is the test case failing for me:

Failed tests:   testSimpleChat(org.apache.hedwig.jms.BasicJMSTest)

If you want I can create a jira and post logs.

-Flavio

> 
> Flavio:
> 
> 
> What's the error? Compilation error? or Test error? Could you send more info?
> 
> - Sijie
> 
> 
> On Tue, Jan 14, 2014 at 3:17 PM, Flavio Junqueira  
> wrote:
> Does it fail for you people? It is failing for me…
> 
> -Flavio
>

[jira] [Commented] (BOOKKEEPER-662) Major GC should kick in immediately if remaining space reaches a warning threshold

2014-01-15 Thread Ivan Kelly (JIRA) 

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

Ivan Kelly commented on BOOKKEEPER-662:
---

Probably unrelated. That test has a history of flake. Part of it also failed on 
build 505. Creating JIRA for it.

> Major GC should kick in immediately if remaining space reaches a warning 
> threshold
> --
>
> Key: BOOKKEEPER-662
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-662
> Project: Bookkeeper
>  Issue Type: Improvement
>  Components: bookkeeper-server
>Reporter: Sijie Guo
>Assignee: Aniruddha
> Fix For: 4.3.0
>
> Attachments: 0001-WIP.patch, BOOKKEEPER-662.diff, 
> BOOKKEEPER-662.diff, BOOKKEEPER-662.diff
>
>
> in a high throughput case, Major GC should kick in immediately if remaining 
> spaces reaches a warning threshold.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Created] (BOOKKEEPER-718) AuditorLedgerCheckerTest is flakey

2014-01-15 Thread Ivan Kelly (JIRA) 
Ivan Kelly created BOOKKEEPER-718:
-

 Summary: AuditorLedgerCheckerTest is flakey
 Key: BOOKKEEPER-718
 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-718
 Project: Bookkeeper
  Issue Type: Bug
  Components: bookkeeper-auto-recovery
Reporter: Ivan Kelly
 Fix For: 4.3.0
 Attachments: error505.txt, error509.txt

See:
https://builds.apache.org/job/bookkeeper-trunk/505/
& 
https://builds.apache.org/job/bookkeeper-trunk/509

Relevant errors attached.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (BOOKKEEPER-718) AuditorLedgerCheckerTest is flakey

2014-01-15 Thread Ivan Kelly (JIRA) 

 [ 
https://issues.apache.org/jira/browse/BOOKKEEPER-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Kelly updated BOOKKEEPER-718:
--

Attachment: error509.txt
error505.txt

> AuditorLedgerCheckerTest is flakey
> --
>
> Key: BOOKKEEPER-718
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-718
> Project: Bookkeeper
>  Issue Type: Bug
>  Components: bookkeeper-auto-recovery
>Reporter: Ivan Kelly
> Fix For: 4.3.0
>
> Attachments: error505.txt, error509.txt
>
>
> See:
> https://builds.apache.org/job/bookkeeper-trunk/505/
> & 
> https://builds.apache.org/job/bookkeeper-trunk/509
> Relevant errors attached.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Reopened] (BOOKKEEPER-661) Turn readonly back to writable if spaces are reclaimed.

2014-01-15 Thread Sijie Guo (JIRA) 

 [ 
https://issues.apache.org/jira/browse/BOOKKEEPER-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sijie Guo reopened BOOKKEEPER-661:
--


not sure why this was resolved. :(

> Turn readonly back to writable if spaces are reclaimed.
> ---
>
> Key: BOOKKEEPER-661
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-661
> Project: Bookkeeper
>  Issue Type: Improvement
>  Components: bookkeeper-server
>Reporter: Sijie Guo
>Assignee: Sijie Guo
> Fix For: 4.3.0
>
> Attachments: BOOKKEEPER-661.diff, BOOKKEEPER-661.diff, 
> BOOKKEEPER-661_662.diff
>
>
> should be able to turn a bookie from readonly back to writable if the spaces 
> are reclaimed.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)