ZooKeeper-trunk-ibm6 - Build # 652 - Still Failing

2014-10-21 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper-trunk-ibm6/652/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 335597 lines...]
[junit] 2014-10-21 09:29:43,296 [myid:] - INFO  [main:JMXEnv@142] - 
ensureOnly:[]
[junit] 2014-10-21 09:29:43,298 [myid:] - INFO  [main:ClientBase@443] - 
STARTING server
[junit] 2014-10-21 09:29:43,299 [myid:] - INFO  [main:ClientBase@364] - 
CREATING server instance 127.0.0.1:11221
[junit] 2014-10-21 09:29:43,299 [myid:] - INFO  
[main:NIOServerCnxnFactory@670] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 2 selector thread(s), 32 worker threads, and 64 
kB direct buffers.
[junit] 2014-10-21 09:29:43,300 [myid:] - INFO  
[main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2014-10-21 09:29:43,300 [myid:] - INFO  [main:ClientBase@339] - 
STARTING server instance 127.0.0.1:11221
[junit] 2014-10-21 09:29:43,301 [myid:] - INFO  [main:ZooKeeperServer@781] 
- minSessionTimeout set to 6000
[junit] 2014-10-21 09:29:43,301 [myid:] - INFO  [main:ZooKeeperServer@790] 
- maxSessionTimeout set to 6
[junit] 2014-10-21 09:29:43,301 [myid:] - INFO  [main:ZooKeeperServer@152] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-ibm6/trunk/build/test/tmp/test3571506451130181692.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-ibm6/trunk/build/test/tmp/test3571506451130181692.junit.dir/version-2
[junit] 2014-10-21 09:29:43,303 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-ibm6/trunk/build/test/tmp/test3571506451130181692.junit.dir/version-2/snapshot.b
[junit] 2014-10-21 09:29:43,305 [myid:] - INFO  [main:FileTxnSnapLog@298] - 
Snapshotting: 0xb to 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-ibm6/trunk/build/test/tmp/test3571506451130181692.junit.dir/version-2/snapshot.b
[junit] 2014-10-21 09:29:43,308 [myid:] - INFO  
[main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221
[junit] 2014-10-21 09:29:43,308 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:50848
[junit] 2014-10-21 09:29:43,310 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@835] - Processing stat command from 
/127.0.0.1:50848
[junit] 2014-10-21 09:29:43,310 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn$StatCommand@684] - Stat command output
[junit] 2014-10-21 09:29:43,311 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@1006] - Closed socket connection for client 
/127.0.0.1:50848 (no session established for client)
[junit] 2014-10-21 09:29:43,311 [myid:] - INFO  [main:JMXEnv@224] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2014-10-21 09:29:43,314 [myid:] - INFO  [main:JMXEnv@241] - 
expect:InMemoryDataTree
[junit] 2014-10-21 09:29:43,315 [myid:] - INFO  [main:JMXEnv@245] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2014-10-21 09:29:43,315 [myid:] - INFO  [main:JMXEnv@241] - 
expect:StandaloneServer_port
[junit] 2014-10-21 09:29:43,315 [myid:] - INFO  [main:JMXEnv@245] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2014-10-21 09:29:43,315 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 5500
[junit] 2014-10-21 09:29:43,316 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 40
[junit] 2014-10-21 09:29:43,316 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota
[junit] 2014-10-21 09:29:43,316 [myid:] - INFO  [main:ClientBase@520] - 
tearDown starting
[junit] 2014-10-21 09:29:43,352 [myid:] - INFO  [main:ZooKeeper@968] - 
Session: 0x149320a676e closed
[junit] 2014-10-21 09:29:43,352 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@529] - EventThread shut down
[junit] 2014-10-21 09:29:43,353 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2014-10-21 09:29:43,354 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2014-10-21 09:29:43,354 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2014-10-21 09:29:43,354 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2014-10-21 09:29:43,354 [myid:] - INFO  

[jira] [Created] (ZOOKEEPER-2064) Prevent resource leak in various classes

2014-10-21 Thread Ted Yu (JIRA)
Ted Yu created ZOOKEEPER-2064:
-

 Summary: Prevent resource leak in various classes
 Key: ZOOKEEPER-2064
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2064
 Project: ZooKeeper
  Issue Type: Bug
Reporter: Ted Yu


In various classes, there is potential resource leak.
e.g. LogIterator / RandomAccessFileReader is not closed upon return from the 
method.

Corresponding close() should be called to prevent resource leak.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (ZOOKEEPER-2064) Prevent resource leak in various classes

2014-10-21 Thread Ted Yu (JIRA)

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

Ted Yu updated ZOOKEEPER-2064:
--
Attachment: 2064-v1.txt

Tentative patch.

 Prevent resource leak in various classes
 

 Key: ZOOKEEPER-2064
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2064
 Project: ZooKeeper
  Issue Type: Bug
Reporter: Ted Yu
 Attachments: 2064-v1.txt


 In various classes, there is potential resource leak.
 e.g. LogIterator / RandomAccessFileReader is not closed upon return from the 
 method.
 Corresponding close() should be called to prevent resource leak.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Failed: ZOOKEEPER-2064 PreCommit Build #2396

2014-10-21 Thread Apache Jenkins Server
Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-2064
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2396/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 180 lines...]
 [exec] File to patch: 
 [exec] Skip this patch? [y] 
 [exec] Skipping patch.
 [exec] 1 out of 1 hunk ignored
 [exec] PATCH APPLICATION FAILED
 [exec] 
 [exec] 
 [exec] 
 [exec] 
 [exec] -1 overall.  Here are the results of testing the latest attachment 
 [exec]   
http://issues.apache.org/jira/secure/attachment/12676159/2064-v1.txt
 [exec]   against trunk revision 1632209.
 [exec] 
 [exec] +1 @author.  The patch does not contain any @author tags.
 [exec] 
 [exec] +1 tests included.  The patch appears to include 6 new or 
modified tests.
 [exec] 
 [exec] -1 patch.  The patch command could not apply the patch.
 [exec] 
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2396//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] Comment added.
 [exec] 132883f1032739545bf695946019c0a6d4710067 logged out
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-Build/trunk/build.xml:1714:
 exec returned: 1

Total time: 38 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Sending artifact delta relative to PreCommit-ZOOKEEPER-Build #2393
Archived 1 artifacts
Archive block size is 32768
Received 0 blocks and 58386 bytes
Compression is 0.0%
Took 1.9 sec
Recording test results
Description set: ZOOKEEPER-2064
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Commented] (ZOOKEEPER-2064) Prevent resource leak in various classes

2014-10-21 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178952#comment-14178952
 ] 

Hadoop QA commented on ZOOKEEPER-2064:
--

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12676159/2064-v1.txt
  against trunk revision 1632209.

+1 @author.  The patch does not contain any @author tags.

+1 tests included.  The patch appears to include 6 new or modified tests.

-1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2396//console

This message is automatically generated.

 Prevent resource leak in various classes
 

 Key: ZOOKEEPER-2064
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2064
 Project: ZooKeeper
  Issue Type: Bug
Reporter: Ted Yu
 Attachments: 2064-v1.txt


 In various classes, there is potential resource leak.
 e.g. LogIterator / RandomAccessFileReader is not closed upon return from the 
 method.
 Corresponding close() should be called to prevent resource leak.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


ZooKeeper-trunk-openjdk7 - Build # 606 - Failure

2014-10-21 Thread Apache Jenkins Server
See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/606/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 323058 lines...]
[junit] 2014-10-21 20:29:24,000 [myid:] - INFO  [main:ClientBase@364] - 
CREATING server instance 127.0.0.1:11221
[junit] 2014-10-21 20:29:24,000 [myid:] - INFO  
[main:NIOServerCnxnFactory@670] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 2 selector thread(s), 32 worker threads, and 64 
kB direct buffers.
[junit] 2014-10-21 20:29:24,000 [myid:] - INFO  
[main:NIOServerCnxnFactory@683] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2014-10-21 20:29:24,001 [myid:] - INFO  
[SessionTracker:SessionTrackerImpl@157] - SessionTrackerImpl exited loop!
[junit] 2014-10-21 20:29:24,001 [myid:] - INFO  [main:ClientBase@339] - 
STARTING server instance 127.0.0.1:11221
[junit] 2014-10-21 20:29:24,001 [myid:] - INFO  
[SessionTracker:SessionTrackerImpl@157] - SessionTrackerImpl exited loop!
[junit] 2014-10-21 20:29:24,001 [myid:] - INFO  [main:ZooKeeperServer@781] 
- minSessionTimeout set to 6000
[junit] 2014-10-21 20:29:24,002 [myid:] - INFO  [main:ZooKeeperServer@790] 
- maxSessionTimeout set to 6
[junit] 2014-10-21 20:29:24,002 [myid:] - INFO  [main:ZooKeeperServer@152] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test5906258536155691804.junit.dir/version-2
 snapdir 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test5906258536155691804.junit.dir/version-2
[junit] 2014-10-21 20:29:24,003 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test5906258536155691804.junit.dir/version-2/snapshot.b
[junit] 2014-10-21 20:29:24,006 [myid:] - INFO  [main:FileTxnSnapLog@298] - 
Snapshotting: 0xb to 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/test/tmp/test5906258536155691804.junit.dir/version-2/snapshot.b
[junit] 2014-10-21 20:29:24,008 [myid:] - INFO  
[main:FourLetterWordMain@43] - connecting to 127.0.0.1 11221
[junit] 2014-10-21 20:29:24,009 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:54090
[junit] 2014-10-21 20:29:24,011 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@835] - Processing stat command from 
/127.0.0.1:54090
[junit] 2014-10-21 20:29:24,011 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn$StatCommand@684] - Stat command output
[junit] 2014-10-21 20:29:24,011 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@1006] - Closed socket connection for client 
/127.0.0.1:54090 (no session established for client)
[junit] 2014-10-21 20:29:24,011 [myid:] - INFO  [main:JMXEnv@224] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2014-10-21 20:29:24,013 [myid:] - INFO  [main:JMXEnv@241] - 
expect:InMemoryDataTree
[junit] 2014-10-21 20:29:24,014 [myid:] - INFO  [main:JMXEnv@245] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2014-10-21 20:29:24,014 [myid:] - INFO  [main:JMXEnv@241] - 
expect:StandaloneServer_port
[junit] 2014-10-21 20:29:24,014 [myid:] - INFO  [main:JMXEnv@245] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2014-10-21 20:29:24,014 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@55] - Memory used 88317
[junit] 2014-10-21 20:29:24,014 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@60] - Number of threads 22
[junit] 2014-10-21 20:29:24,015 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@65] - FINISHED TEST METHOD testQuota
[junit] 2014-10-21 20:29:24,015 [myid:] - INFO  [main:ClientBase@520] - 
tearDown starting
[junit] 2014-10-21 20:29:24,072 [myid:] - INFO  [main:ZooKeeper@968] - 
Session: 0x14934665bc9 closed
[junit] 2014-10-21 20:29:24,073 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2014-10-21 20:29:24,073 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@529] - EventThread shut down
[junit] 2014-10-21 20:29:24,073 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2014-10-21 20:29:24,073 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-1:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2014-10-21 20:29:24,074 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread 

[jira] [Commented] (BOOKKEEPER-792) Split bookkeeper client into a separate maven module

2014-10-21 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14179506#comment-14179506
 ] 

Hadoop QA commented on BOOKKEEPER-792:
--

Testing JIRA BOOKKEEPER-792


Patch 
[0001-Split-the-bookkeeper-client-from-the-server.patch|https://issues.apache.org/jira/secure/attachment/12674744/0001-Split-the-bookkeeper-client-from-the-server.patch]
 downloaded at Wed Oct 22 02:31:00 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:red}-1 TESTS{color}
.Tests run: 929
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  testSimpleChat(org.apache.hedwig.jms.BasicJMSTest)

{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/799/

 Split bookkeeper client into a separate maven module
 

 Key: BOOKKEEPER-792
 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-792
 Project: Bookkeeper
  Issue Type: Bug
Reporter: Ivan Kelly
Assignee: Ivan Kelly
 Fix For: 4.4.0

 Attachments: 0001-Split-the-bookkeeper-client-from-the-server.patch, 
 0001-Split-the-bookkeeper-client-from-the-server.patch, 
 0001-Split-the-bookkeeper-client-from-the-server.patch


 Right now, to include bookkeeper as a dependency, you need to include 
 org.apache.bookkeeper:bookkeeper-server
 This pulls in all the bookkeeper-server code, and all the server dependencies 
 as well as the client. The server dependencies are larger than the client 
 dependencies. For one thing, it pulls in jna and log4j which should never be 
 pulled in from the client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (BOOKKEEPER-634) Provide admin tool to rename bookie identifier in ledger metadata

2014-10-21 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14179533#comment-14179533
 ] 

Hadoop QA commented on BOOKKEEPER-634:
--

Testing JIRA BOOKKEEPER-634


Patch 
[002-BOOKKEEPER-634-rename-bookieid-in-ledger.patch|https://issues.apache.org/jira/secure/attachment/12672247/002-BOOKKEEPER-634-rename-bookieid-in-ledger.patch]
 downloaded at Wed Oct 22 03:04:59 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 1 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:red}-1 TESTS{color}
.Tests run: 933
.Tests failed: 1
.Tests errors: 0

.The patch failed the following testcases:

.  
testRenameWhenAddEntryInProgress(org.apache.bookkeeper.client.UpdateLedgerCmdTest)

{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/800/

 Provide admin tool to rename bookie identifier in ledger metadata
 -

 Key: BOOKKEEPER-634
 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-634
 Project: Bookkeeper
  Issue Type: Sub-task
  Components: bookkeeper-client, bookkeeper-server
Affects Versions: 4.2.1
Reporter: Rakesh R
Assignee: Rakesh R
 Fix For: 4.3.1

 Attachments: 0001-BOOKKEEPER-634-initial-draft-version.patch, 
 001-BOOKKEEPER-634-rename-bookieid-in-ledger.patch, 
 002-BOOKKEEPER-634-rename-bookieid-in-ledger.patch, 
 BOOKKEEPER-634-rename-bookieid-in-ledger.patch, BOOKKEEPER-634.patch, 
 BOOKKEEPER-634.patch


 This JIRA to discuss about admin tool for changing the bookie's IP to 
 hostname.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)