date:20160427

[jira] [Updated] (ZOOKEEPER-2325) Data inconsistency if all snapshots empty or missing

2016-04-27 Thread Flavio Junqueira (JIRA)


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

Flavio Junqueira updated ZOOKEEPER-2325:

Assignee: Andrew Grasso

> Data inconsistency if all snapshots empty or missing
> 
>
> Key: ZOOKEEPER-2325
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2325
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.6
>Reporter: Andrew Grasso
>Assignee: Andrew Grasso
>Priority: Critical
> Attachments: ZOOKEEPER-2325.001.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When loading state from snapshots on startup, FileTxnSnapLog.java ignores the 
> result of FileSnap.deserialize, which is -1L if no valid snapshots are found. 
> Recovery proceeds with dt.lastProcessed == 0, its initial value.
> The result is that Zookeeper will process the transaction logs and then begin 
> serving requests with a different state than the rest of the ensemble.
> To reproduce:
> In a healthy zookeeper cluster of size >= 3, shut down one node.
> Either delete all snapshots for this node or change all to be empty files.
> Restart the node.
> We believe this can happen organically if a node runs out of disk space.



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

[jira] [Commented] (ZOOKEEPER-2325) Data inconsistency if all snapshots empty or missing

2016-04-27 Thread Flavio Junqueira (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15261574#comment-15261574
 ] 

Flavio Junqueira commented on ZOOKEEPER-2325:
-

It sounds like this should be easy to reproduce. Do you think you can add a 
test case for this [~agrasso]?

> Data inconsistency if all snapshots empty or missing
> 
>
> Key: ZOOKEEPER-2325
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2325
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.6
>Reporter: Andrew Grasso
>Priority: Critical
> Attachments: ZOOKEEPER-2325.001.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When loading state from snapshots on startup, FileTxnSnapLog.java ignores the 
> result of FileSnap.deserialize, which is -1L if no valid snapshots are found. 
> Recovery proceeds with dt.lastProcessed == 0, its initial value.
> The result is that Zookeeper will process the transaction logs and then begin 
> serving requests with a different state than the rest of the ensemble.
> To reproduce:
> In a healthy zookeeper cluster of size >= 3, shut down one node.
> Either delete all snapshots for this node or change all to be empty files.
> Restart the node.
> We believe this can happen organically if a node runs out of disk space.



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

[GitHub] zookeeper pull request: Update Op.java

2016-04-27 Thread buptUnixGuys

GitHub user buptUnixGuys opened a pull request:

https://github.com/apache/zookeeper/pull/67

Update Op.java

A minor bug.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/buptUnixGuys/zookeeper patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zookeeper/pull/67.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 #67


commit 00257b53b214be810f14898ac66245c4127b0f4e
Author: bupt_tengteng 
Date:   2016-04-28T04:28:07Z

Update Op.java

this is a bug.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (ZOOKEEPER-2325) Data inconsistency if all snapshots empty or missing

2016-04-27 Thread Ahmed (JIRA)


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

Ahmed updated ZOOKEEPER-2325:
-
Priority: Critical  (was: Major)

> Data inconsistency if all snapshots empty or missing
> 
>
> Key: ZOOKEEPER-2325
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2325
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.6
>Reporter: Andrew Grasso
>Priority: Critical
> Attachments: ZOOKEEPER-2325.001.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When loading state from snapshots on startup, FileTxnSnapLog.java ignores the 
> result of FileSnap.deserialize, which is -1L if no valid snapshots are found. 
> Recovery proceeds with dt.lastProcessed == 0, its initial value.
> The result is that Zookeeper will process the transaction logs and then begin 
> serving requests with a different state than the rest of the ensemble.
> To reproduce:
> In a healthy zookeeper cluster of size >= 3, shut down one node.
> Either delete all snapshots for this node or change all to be empty files.
> Restart the node.
> We believe this can happen organically if a node runs out of disk space.



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

Use of GitHub issues instead of JIRA

2016-04-27 Thread Flavio Junqueira

We have talked about this issue recently and I wanted to share this discussion 
here:

https://issues.apache.org/jira/browse/LEGAL-249 


-Flavio

[jira] [Commented] (ZOOKEEPER-2325) Data inconsistency if all snapshots empty or missing

2016-04-27 Thread Nicholas Wolchko (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15261095#comment-15261095
 ] 

Nicholas Wolchko commented on ZOOKEEPER-2325:
-

I've seen some cases where our zookeeper servers lost data, and this looks like 
it could be the cause. Is there anything blocking this change?

> Data inconsistency if all snapshots empty or missing
> 
>
> Key: ZOOKEEPER-2325
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2325
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.6
>Reporter: Andrew Grasso
> Attachments: ZOOKEEPER-2325.001.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When loading state from snapshots on startup, FileTxnSnapLog.java ignores the 
> result of FileSnap.deserialize, which is -1L if no valid snapshots are found. 
> Recovery proceeds with dt.lastProcessed == 0, its initial value.
> The result is that Zookeeper will process the transaction logs and then begin 
> serving requests with a different state than the rest of the ensemble.
> To reproduce:
> In a healthy zookeeper cluster of size >= 3, shut down one node.
> Either delete all snapshots for this node or change all to be empty files.
> Restart the node.
> We believe this can happen organically if a node runs out of disk space.



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

ZooKeeper-trunk-openjdk7 - Build # 1004 - Still Failing

2016-04-27 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper-trunk-openjdk7/1004/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 1516 lines...]
[ivy:retrieve] .. (0kB)
[ivy:retrieve]  [SUCCESSFUL ] commons-cli#commons-cli;1.2!commons-cli.jar (31ms)
[ivy:retrieve] downloading 
http://repo1.maven.org/maven2/log4j/log4j/1.2.17/log4j-1.2.17.jar ...
[ivy:retrieve] . (478kB)
[ivy:retrieve] .. (0kB)
[ivy:retrieve]  [SUCCESSFUL ] log4j#log4j;1.2.17!log4j.jar(bundle) (38ms)
[ivy:retrieve] downloading 
http://repo1.maven.org/maven2/io/netty/netty/3.7.1.Final/netty-3.7.1.Final.jar 
...
[ivy:retrieve] ... (1181kB)
[ivy:retrieve] .. (0kB)
[ivy:retrieve]  [SUCCESSFUL ] io.netty#netty;3.7.1.Final!netty.jar (49ms)
[ivy:retrieve] downloading 
http://repo1.maven.org/maven2/net/java/dev/javacc/javacc/5.0/javacc-5.0.jar ...
[ivy:retrieve] .. (291kB)
[ivy:retrieve] .. (0kB)
[ivy:retrieve]  [SUCCESSFUL ] net.java.dev.javacc#javacc;5.0!javacc.jar (36ms)
[ivy:retrieve] :: resolution report :: resolve 4428ms :: artifacts dl 499ms
-
|  |modules||   artifacts   |
|   conf   | number| search|dwnlded|evicted|| number|dwnlded|
-
|  default |   12  |   12  |   12  |   0   ||   12  |   12  |
-
[ivy:retrieve] :: retrieving :: org.apache.zookeeper#zookeeper
[ivy:retrieve]  confs: [default]
[ivy:retrieve]  12 artifacts copied, 0 already retrieved (4049kB/33ms)

clover.setup:

clover.info:

clover:

generate_jute_parser:
[mkdir] Created dir: 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/jute_compiler/org/apache/jute/compiler/generated
[ivy:artifactproperty] DEPRECATED: 'ivy.conf.file' is deprecated, use 
'ivy.settings.file' instead
[ivy:artifactproperty] :: loading settings :: file = 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/ivysettings.xml
 [move] Moving 1 file to 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build/lib
   [javacc] Java Compiler Compiler Version 5.0 (Parser Generator)
   [javacc] (type "javacc" with no arguments for help)
   [javacc] Reading from file 
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/src/java/main/org/apache/jute/compiler/generated/rcc.jj
 . . .
   [javacc] File "TokenMgrError.java" does not exist.  Will create one.
   [javacc] File "ParseException.java" does not exist.  Will create one.
   [javacc] File "Token.java" does not exist.  Will create one.
   [javacc] File "SimpleCharStream.java" does not exist.  Will create one.
   [javacc] Parser generated successfully.

jute:

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-openjdk7/trunk/build.xml:272:
 Unable to find a javac compiler;
com.sun.tools.javac.Main is not on the classpath.
Perhaps JAVA_HOME does not point to the JDK.
It is currently set to "/usr/lib/jvm/java-7-openjdk-amd64/jre"

Total time: 7 seconds
Build step 'Invoke Ant' marked build as failure
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files 
were found. Configuration error?
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



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

ZooKeeper_branch35_solaris - Build # 80 - Still Failing

2016-04-27 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper_branch35_solaris/80/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 323345 lines...]
[junit] 2016-04-27 17:08:32,414 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-04-27 17:08:32,415 [myid:] - INFO  [main:ClientBase@460] - 
STARTING server
[junit] 2016-04-27 17:08:32,415 [myid:] - INFO  [main:ClientBase@380] - 
CREATING server instance 127.0.0.1:11222
[junit] 2016-04-27 17:08:32,415 [myid:] - INFO  
[main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 
kB direct buffers.
[junit] 2016-04-27 17:08:32,416 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-04-27 17:08:32,416 [myid:] - INFO  [main:ClientBase@355] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-04-27 17:08:32,417 [myid:] - INFO  [main:ZooKeeperServer@858] 
- minSessionTimeout set to 6000
[junit] 2016-04-27 17:08:32,417 [myid:] - INFO  [main:ZooKeeperServer@867] 
- maxSessionTimeout set to 6
[junit] 2016-04-27 17:08:32,417 [myid:] - INFO  [main:ZooKeeperServer@156] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test6159822570603529004.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test6159822570603529004.junit.dir/version-2
[junit] 2016-04-27 17:08:32,418 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test6159822570603529004.junit.dir/version-2/snapshot.b
[junit] 2016-04-27 17:08:32,420 [myid:] - INFO  [main:FileTxnSnapLog@298] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper_branch35_solaris/branch-3.5/build/test/tmp/test6159822570603529004.junit.dir/version-2/snapshot.b
[junit] 2016-04-27 17:08:32,422 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-04-27 17:08:32,422 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:51601
[junit] 2016-04-27 17:08:32,423 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:51601
[junit] 2016-04-27 17:08:32,423 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-04-27 17:08:32,424 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:51601 (no session established for client)
[junit] 2016-04-27 17:08:32,424 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-04-27 17:08:32,425 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-04-27 17:08:32,425 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-04-27 17:08:32,426 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-04-27 17:08:32,426 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-04-27 17:08:32,426 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17670
[junit] 2016-04-27 17:08:32,426 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-04-27 17:08:32,426 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-04-27 17:08:32,427 [myid:] - INFO  [main:ClientBase@537] - 
tearDown starting
[junit] 2016-04-27 17:08:32,502 [myid:] - INFO  [main:ZooKeeper@1110] - 
Session: 0x120d5af316f closed
[junit] 2016-04-27 17:08:32,502 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for 
session: 0x120d5af316f
[junit] 2016-04-27 17:08:32,502 [myid:] - INFO  [main:ClientBase@507] - 
STOPPING server
[junit] 2016-04-27 17:08:32,503 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-04-27 17:08:32,503 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-04-27 17:08:32,503 [myid:] - INFO

ZooKeeper_branch34_openjdk7 - Build # 1058 - Failure

2016-04-27 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1058/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 221019 lines...]
[junit] 2016-04-27 15:23:57,443 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-04-27 15:23:57,443 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-04-27 15:23:57,443 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2016-04-27 15:23:57,444 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@219] - 
NIOServerCnxn factory exited run method
[junit] 2016-04-27 15:23:57,444 [myid:] - INFO  [main:ZooKeeperServer@469] 
- shutting down
[junit] 2016-04-27 15:23:57,444 [myid:] - INFO  
[main:SessionTrackerImpl@225] - Shutting down
[junit] 2016-04-27 15:23:57,444 [myid:] - INFO  
[main:PrepRequestProcessor@765] - Shutting down
[junit] 2016-04-27 15:23:57,444 [myid:] - INFO  
[main:SyncRequestProcessor@209] - Shutting down
[junit] 2016-04-27 15:23:57,445 [myid:] - INFO  [ProcessThread(sid:0 
cport:11221)::PrepRequestProcessor@143] - PrepRequestProcessor exited loop!
[junit] 2016-04-27 15:23:57,445 [myid:] - INFO  
[SyncThread:0:SyncRequestProcessor@187] - SyncRequestProcessor exited!
[junit] 2016-04-27 15:23:57,445 [myid:] - INFO  
[main:FinalRequestProcessor@402] - shutdown of request processor complete
[junit] 2016-04-27 15:23:57,445 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-04-27 15:23:57,446 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-04-27 15:23:57,447 [myid:] - INFO  [main:ClientBase@443] - 
STARTING server
[junit] 2016-04-27 15:23:57,447 [myid:] - INFO  [main:ClientBase@364] - 
CREATING server instance 127.0.0.1:11221
[junit] 2016-04-27 15:23:57,448 [myid:] - INFO  
[main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221
[junit] 2016-04-27 15:23:57,448 [myid:] - INFO  [main:ClientBase@339] - 
STARTING server instance 127.0.0.1:11221
[junit] 2016-04-27 15:23:57,448 [myid:] - INFO  [main:ZooKeeperServer@170] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/branch-3.4/build/test/tmp/test1001546076029836179.junit.dir/version-2
 snapdir 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7/branch-3.4/build/test/tmp/test1001546076029836179.junit.dir/version-2
[junit] 2016-04-27 15:23:57,452 [myid:] - INFO  
[main:FourLetterWordMain@62] - connecting to 127.0.0.1 11221
[junit] 2016-04-27 15:23:57,452 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@192] - 
Accepted socket connection from /127.0.0.1:55650
[junit] 2016-04-27 15:23:57,453 [myid:] - INFO  
[NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@827] - Processing 
stat command from /127.0.0.1:55650
[junit] 2016-04-27 15:23:57,453 [myid:] - INFO  
[Thread-4:NIOServerCnxn$StatCommand@663] - Stat command output
[junit] 2016-04-27 15:23:57,453 [myid:] - INFO  
[Thread-4:NIOServerCnxn@1008] - Closed socket connection for client 
/127.0.0.1:55650 (no session established for client)
[junit] 2016-04-27 15:23:57,453 [myid:] - INFO  [main:JMXEnv@229] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-04-27 15:23:57,455 [myid:] - INFO  [main:JMXEnv@246] - 
expect:InMemoryDataTree
[junit] 2016-04-27 15:23:57,455 [myid:] - INFO  [main:JMXEnv@250] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree
[junit] 2016-04-27 15:23:57,455 [myid:] - INFO  [main:JMXEnv@246] - 
expect:StandaloneServer_port
[junit] 2016-04-27 15:23:57,456 [myid:] - INFO  [main:JMXEnv@250] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11221
[junit] 2016-04-27 15:23:57,456 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 26414
[junit] 2016-04-27 15:23:57,456 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20
[junit] 2016-04-27 15:23:57,456 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota
[junit] 2016-04-27 15:23:57,456 [myid:] - INFO  [main:ClientBase@520] - 
tearDown starting
[junit] 2016-04-27 15:23:57,530 [myid:] - INFO  [main:ZooKeeper@684] - 
Session: 0x1545851cf22 closed
[junit] 2016-04-27 15:23:57,531 [myid:] - INFO  [main:ClientBase@490] - 
STOPPING server
[junit] 2016-04-27 15:23:57,531 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@519] - EventThread shut down for 
session: 0x1545851cf22
[junit] 2016-04-27 15:23:57,531 [myid:] - INFO

[jira] [Issue Comment Deleted] (ZOOKEEPER-2416) Remove Java System property usage from ZooKeeper server code

2016-04-27 Thread Flavio Junqueira (JIRA)

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

Flavio Junqueira updated ZOOKEEPER-2416:

Comment: was deleted

(was: Pogo techical support number call# 844-880-6776, we provide pogo game
technical support , pogo games, how to contact pogo by phone
call#-844-880-6776, pogo games contact number, help pogo game, pogo games help,
online pogo game help.

We are a Pogo Games Customer Support Company providing quality Pogo Games help
with Pogo Support Number- 844-880-6776. We are a Pogo Games Customer Support
Company providing quality Pogo Games help with Pogo Support Number-
844-880-6776 Pogo Techical Support Number CLUB Games.
Get quick support- 844-880-6776 & complete Pogo Games help at by just one call
at our Pogo Games Customer Support Number- 844-880-6776.
Call us at our Pogo Games Customer Support Number- 844-880-6776 to experience
the quick and best Pogo games Helpline Number-844-880-6776.
Pogo Games Customer Support Number 844-880-6776.Company Pogo Games help with
Pogo Support Number- 844-880-6776.
Contact us for the quick pogo games customer support number-844-880-6776. Our
experts provide quick pogo games help number-844-880-6776.
Pogo techical support number call# 844-880-6776, we provide pogo game technical
support , pogo games, how to contact pogo by phone call#-844-880-6776, pogo
games contact number, help pogo game, pogo games help, online pogo game help.

[jira] [Deleted] (ZOOKEEPER-2417) Pogo Support Number +1-844-446 4460| Club Pogo Games Technical support number...

2016-04-27 Thread Flavio Junqueira (JIRA)


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

Flavio Junqueira deleted ZOOKEEPER-2417:



> Pogo Support Number +1-844-446 4460| Club Pogo Games Technical support 
> number...
> 
>
> Key: ZOOKEEPER-2417
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2417
> Project: ZooKeeper
>  Issue Type: Bug
>Reporter: Amit Kumar
>
> The is pogo tech support phone number 1 844 446 4460,pogo support phone 
> number USA,Dial 1 844 844 2433 Pogo games tech Support phone number,Pogo 
> games Support number Pogo h.e.l.p.l.i.n.e p.h.o.n.e Number Pogo Desktop 
> S.u.p.p.o.r.t Number usa Helpline TECH ))1 844 446 4460  ((Pogo Desktop 
> technical support phone number Pogo Desktop phone number QB SUPPORT ON ((1 
> 844 446 4460  )) Pogo PHONE NUMBER AND Pogo SUPPORT PHONE NUMBER Pogo Toll 
> Free, Microsoft@(1 844 446 4460  )@ Pogo Tech Support Phone Number Desktop 
> vides online solution for all USA/CANADA clients. For any help of query call 
> 1 844 446 4460  to get all Pogo account solution. call, 1 844 446 4460  for 
> all type help by Pogo tech support phone number, Microsoft Pogo Tech Support 
> Phone Number, Pogo Help Desk Phone Number, Pogo tech support number, Pogo 
> technical support phone number,@@@ Pogo phone number, Pogo technical support 
> number, Pogo support phone number, Pogo technical support, Pogo Customer 
> Service Phone Number, Pogo Customer Service Number, Pogo Customer Support 
> Phone Number, Pogo Customer Support Number, Pogo Customer Service 
> Helpline Number, Pogo Customer Care Number, Pogo support team phone number, 
> @ Pogo help number-Pogo Helpline Number; Pogo help phone number-Pogo 
> Helpline Number, Pogo Tech Support Toll free Number, Pogo Support Telephone 
> Number, Pogo Tech Support Telephone number, Pogo Tech Support contact number, 
> Pogo support contact number, Pogo technical support contact number. Call, 
> Pogo tech support phone number, Microsoft Pogo Tech Support Phone Number, 
> Pogo Help Desk Phone Number, Pogo tech support number, Pogo technical support 
> phone number, Pogo phone number, Pogo technical support number, Pogo support 
> phone number. It is very popular toll free number which Desktop vide by Pogo 
> technical support, Pogo Customer Service Phone Number, Pogo Customer Service 
> Number, Pogo Customer Support Phone Number, Pogo Customer Support Number, 
> Pogo Customer Service Helpline Number, Pogo Customer Care Number, Pogo 
> support team phone number. Call, Pogo tech support phone number, Microsoft 
> Pogo Tech Support Phone Number, Pogo Help Desk Phone Number, Pogo tech 
> support number, Pogo technical support phone number, Pogo phone number, Pogo 
> technical support number, Pogo support phone number, Pogo technical support, 
> Pogo Customer Service Phone Number, Pogo Customer Service Number, Pogo 
> Customer Support Phone Number, Pogo Customer Support Number, Pogo Customer 
> Service Helpline Number, Pogo Customer Care Number, Pogo support team phone 
> number, Pogo help number-Pogo Helpline Number; Pogo help phone number, Pogo 
> Helpline Number, Pogo Tech Support Toll free Number, Pogo Support Telephone 
> Number, Pogo Tech Support Telephone number, Pogo Tech Support contact number, 
> Pogo support contact number, Pogo technical support contact number, Pogo 
> Desktop support phone number, Pogo pay.roll support phone number. Pogo 
> pay.roll customer support phone number 1844-513-5978 Pogo technical help 
> telephone number, Pogo technical help contact number, Pogo technical support 
> contact number, Pogo contact number, Pogo contact phone number, Pogo contact 
> telephone number, Pogo 24 hour contact number, Pogo customer support contact 
> number, Pogo customer service contact number, Pogo official number, Pogo 
> official contact number, Pogo 844 contact number, Pogo toll free number, 844 
> number for Pogo support, Pogo 24/7 support phone number Pogo Desktop support 
> phone number,Pogo Desktop support phone number,Pogo Desktop help phone 
> number, Pogo Desktop technical support number.Pogo Desktop support number, 
> Pogo Desktop phone number, Pogo Desktop tech support number, Pogo Desktop 
> customer support number, Pogo Desktop customer support phone number, Pogo 
> Desktop customer service phone number, Pogo Desktop pay.roll customer service 
> phone number, Pogo Desktop support phone number. Help@Call 1 844 446 4460  
> /.Pogo 24/7 support phone number,Pogo telephone number for support? call 1 
> 844 446 4460 @./Pogo contact number, Pogo contact phone number, Pogo contact 
> telephone number,,telephone number for Pogo online support,Pogo official 
> support number,Pogo official number,Pogo pay.roll official phone 
> number,,,phone number for Pogo pay.roll

[jira] [Updated] (ZOOKEEPER-2417) Pogo Support Number +1-844-446 4460| Club Pogo Games Technical support number...

2016-04-27 Thread vinny3004 (JIRA)


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

vinny3004 updated ZOOKEEPER-2417:
-
Description: The is pogo tech support phone number 1 844 446 4460,pogo 
support phone number USA,Dial 1 844 844 2433 Pogo games tech Support phone 
number,Pogo games Support number Pogo h.e.l.p.l.i.n.e p.h.o.n.e Number Pogo 
Desktop S.u.p.p.o.r.t Number usa Helpline TECH ))1 844 446 4460  ((Pogo Desktop 
technical support phone number Pogo Desktop phone number QB SUPPORT ON ((1 844 
446 4460  )) Pogo PHONE NUMBER AND Pogo SUPPORT PHONE NUMBER Pogo Toll Free, 
Microsoft@(1 844 446 4460  )@ Pogo Tech Support Phone Number Desktop vides 
online solution for all USA/CANADA clients. For any help of query call 1 844 
446 4460  to get all Pogo account solution. call, 1 844 446 4460  for all type 
help by Pogo tech support phone number, Microsoft Pogo Tech Support Phone 
Number, Pogo Help Desk Phone Number, Pogo tech support number, Pogo technical 
support phone number,@@@ Pogo phone number, Pogo technical support number, Pogo 
support phone number, Pogo technical support, Pogo Customer Service Phone 
Number, Pogo Customer Service Number, Pogo Customer Support Phone Number, Pogo 
Customer Support Number, Pogo Customer Service Helpline Number, Pogo 
Customer Care Number, Pogo support team phone number, @ Pogo help 
number-Pogo Helpline Number; Pogo help phone number-Pogo Helpline Number, Pogo 
Tech Support Toll free Number, Pogo Support Telephone Number, Pogo Tech Support 
Telephone number, Pogo Tech Support contact number, Pogo support contact 
number, Pogo technical support contact number. Call, Pogo tech support phone 
number, Microsoft Pogo Tech Support Phone Number, Pogo Help Desk Phone Number, 
Pogo tech support number, Pogo technical support phone number, Pogo phone 
number, Pogo technical support number, Pogo support phone number. It is very 
popular toll free number which Desktop vide by Pogo technical support, Pogo 
Customer Service Phone Number, Pogo Customer Service Number, Pogo Customer 
Support Phone Number, Pogo Customer Support Number, Pogo Customer Service 
Helpline Number, Pogo Customer Care Number, Pogo support team phone number. 
Call, Pogo tech support phone number, Microsoft Pogo Tech Support Phone Number, 
Pogo Help Desk Phone Number, Pogo tech support number, Pogo technical support 
phone number, Pogo phone number, Pogo technical support number, Pogo support 
phone number, Pogo technical support, Pogo Customer Service Phone Number, Pogo 
Customer Service Number, Pogo Customer Support Phone Number, Pogo Customer 
Support Number, Pogo Customer Service Helpline Number, Pogo Customer Care 
Number, Pogo support team phone number, Pogo help number-Pogo Helpline Number; 
Pogo help phone number, Pogo Helpline Number, Pogo Tech Support Toll free 
Number, Pogo Support Telephone Number, Pogo Tech Support Telephone number, Pogo 
Tech Support contact number, Pogo support contact number, Pogo technical 
support contact number, Pogo Desktop support phone number, Pogo pay.roll 
support phone number. Pogo pay.roll customer support phone number 1844-513-5978 
Pogo technical help telephone number, Pogo technical help contact number, Pogo 
technical support contact number, Pogo contact number, Pogo contact phone 
number, Pogo contact telephone number, Pogo 24 hour contact number, Pogo 
customer support contact number, Pogo customer service contact number, Pogo 
official number, Pogo official contact number, Pogo 844 contact number, Pogo 
toll free number, 844 number for Pogo support, Pogo 24/7 support phone number 
Pogo Desktop support phone number,Pogo Desktop support phone number,Pogo 
Desktop help phone number, Pogo Desktop technical support number.Pogo Desktop 
support number, Pogo Desktop phone number, Pogo Desktop tech support number, 
Pogo Desktop customer support number, Pogo Desktop customer support phone 
number, Pogo Desktop customer service phone number, Pogo Desktop pay.roll 
customer service phone number, Pogo Desktop support phone number. Help@Call 1 
844 446 4460  /.Pogo 24/7 support phone number,Pogo telephone number for 
support? call 1 844 446 4460 @./Pogo contact number, Pogo contact phone number, 
Pogo contact telephone number,,telephone number for Pogo online support,Pogo 
official support number,Pogo official number,Pogo pay.roll official phone 
number,,,phone number for Pogo pay.roll support,,Pogo 24/7 support phone 
number,,Pogo support number,Pogo telephone number for support Pogo Toll Free, 
Microsoft@(1844 4464460  )@ Pogo Tech Support Phone Number Desktop vides online 
solution for all USA/CANADA clients. For any help of query call 1844 446 4460  
to get all Pogo account solution. call, 1844 446 4460  for all type help by 
Pogo tech support phone number, Microsoft Pogo Tech Support Phone Number, Pogo 
Help Desk Phone Number, Pogo tech support number, Pogo technical support

[jira] [Commented] (ZOOKEEPER-2139) Support multiple ZooKeeper client, with different configurations, in a single JVM

2016-04-27 Thread Arshad Mohammad (JIRA)


[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15260135#comment-15260135
 ] 

Arshad Mohammad commented on ZOOKEEPER-2139:


ping [~fpj]

> Support multiple ZooKeeper client, with different configurations, in a single 
> JVM
> -
>
> Key: ZOOKEEPER-2139
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2139
> Project: ZooKeeper
>  Issue Type: Improvement
>  Components: java client
>Affects Versions: 3.5.0
>Reporter: Surendra Singh Lilhore
>Assignee: Arshad Mohammad
>Priority: Blocker
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2139-05.patch, ZOOKEEPER-2139-06.patch, 
> ZOOKEEPER-2139-07.patch, ZOOKEEPER-2139-08.patch, ZOOKEEPER-2139-09.patch, 
> ZOOKEEPER-2139-10.patch, ZOOKEEPER-2139-11.patch, ZOOKEEPER-2139-12.patch, 
> ZOOKEEPER-2139-13.patch, ZOOKEEPER-2139-14.patch, ZOOKEEPER-2139.patch, 
> ZOOKEEPER-2139.patch, ZOOKEEPER-2139_1.patch, ZOOKEEPER-2139_2.patch
>
>
> I have two ZK client in one JVM, one is secure client and second is normal 
> client (For non secure cluster).
> "zookeeper.sasl.client" system property is "true" by default, because of this 
> my second client connection is failing.
> We should pass all client configurations in client constructor like HDFS 
> client.
> For example :
> {code}
> public ZooKeeper(String connectString, int sessionTimeout, Watcher watcher, 
> Configuration conf) throws IOException
>   {
>   ..
>   ..
>   }
> {code}



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

ZooKeeper-trunk-jdk8 - Build # 578 - Still Failing

2016-04-27 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper-trunk-jdk8/578/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 385070 lines...]
[junit] 2016-04-27 12:45:00,880 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-04-27 12:45:00,881 [myid:] - INFO  [main:ClientBase@460] - 
STARTING server
[junit] 2016-04-27 12:45:00,881 [myid:] - INFO  [main:ClientBase@380] - 
CREATING server instance 127.0.0.1:11222
[junit] 2016-04-27 12:45:00,882 [myid:] - INFO  
[main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 3 selector thread(s), 48 worker threads, and 64 
kB direct buffers.
[junit] 2016-04-27 12:45:00,882 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-04-27 12:45:00,882 [myid:] - INFO  [main:ClientBase@355] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-04-27 12:45:00,882 [myid:] - INFO  [main:ZooKeeperServer@858] 
- minSessionTimeout set to 6000
[junit] 2016-04-27 12:45:00,882 [myid:] - INFO  [main:ZooKeeperServer@867] 
- maxSessionTimeout set to 6
[junit] 2016-04-27 12:45:00,883 [myid:] - INFO  [main:ZooKeeperServer@156] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test4714179491758175146.junit.dir/version-2
 snapdir 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test4714179491758175146.junit.dir/version-2
[junit] 2016-04-27 12:45:00,883 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test4714179491758175146.junit.dir/version-2/snapshot.b
[junit] 2016-04-27 12:45:00,885 [myid:] - INFO  [main:FileTxnSnapLog@298] - 
Snapshotting: 0xb to 
/x1/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-jdk8/trunk/build/test/tmp/test4714179491758175146.junit.dir/version-2/snapshot.b
[junit] 2016-04-27 12:45:00,886 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-04-27 12:45:00,887 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:34694
[junit] 2016-04-27 12:45:00,888 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:34694
[junit] 2016-04-27 12:45:00,888 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-04-27 12:45:00,888 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:34694 (no session established for client)
[junit] 2016-04-27 12:45:00,888 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-04-27 12:45:00,890 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-04-27 12:45:00,890 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-04-27 12:45:00,890 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-04-27 12:45:00,890 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-04-27 12:45:00,890 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 5800
[junit] 2016-04-27 12:45:00,890 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 25
[junit] 2016-04-27 12:45:00,891 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-04-27 12:45:00,891 [myid:] - INFO  [main:ClientBase@537] - 
tearDown starting
[junit] 2016-04-27 12:45:00,960 [myid:] - INFO  [main:ZooKeeper@1110] - 
Session: 0x100316d615b closed
[junit] 2016-04-27 12:45:00,960 [myid:] - INFO  [main:ClientBase@507] - 
STOPPING server
[junit] 2016-04-27 12:45:00,960 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for 
session: 0x100316d615b
[junit] 2016-04-27 12:45:00,960 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-2:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-04-27 12:45:00,961 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-04-27 12:45:00,960 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@219]
 - accept thread exitted run method
[junit] 2016-04-27 12:45:00,961 [myid:] - INFO

ZooKeeper-trunk-solaris - Build # 1137 - Failure

2016-04-27 Thread Apache Jenkins Server

See https://builds.apache.org/job/ZooKeeper-trunk-solaris/1137/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 345570 lines...]
[junit] 2016-04-27 08:15:16,567 [myid:] - INFO  [main:JMXEnv@146] - 
ensureOnly:[]
[junit] 2016-04-27 08:15:16,568 [myid:] - INFO  [main:ClientBase@460] - 
STARTING server
[junit] 2016-04-27 08:15:16,569 [myid:] - INFO  [main:ClientBase@380] - 
CREATING server instance 127.0.0.1:11222
[junit] 2016-04-27 08:15:16,569 [myid:] - INFO  
[main:NIOServerCnxnFactory@673] - Configuring NIO connection handler with 10s 
sessionless connection timeout, 2 selector thread(s), 16 worker threads, and 64 
kB direct buffers.
[junit] 2016-04-27 08:15:16,569 [myid:] - INFO  
[main:NIOServerCnxnFactory@686] - binding to port 0.0.0.0/0.0.0.0:11222
[junit] 2016-04-27 08:15:16,570 [myid:] - INFO  [main:ClientBase@355] - 
STARTING server instance 127.0.0.1:11222
[junit] 2016-04-27 08:15:16,570 [myid:] - INFO  [main:ZooKeeperServer@858] 
- minSessionTimeout set to 6000
[junit] 2016-04-27 08:15:16,570 [myid:] - INFO  [main:ZooKeeperServer@867] 
- maxSessionTimeout set to 6
[junit] 2016-04-27 08:15:16,571 [myid:] - INFO  [main:ZooKeeperServer@156] 
- Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 
6 datadir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test532776919305995.junit.dir/version-2
 snapdir 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test532776919305995.junit.dir/version-2
[junit] 2016-04-27 08:15:16,572 [myid:] - INFO  [main:FileSnap@83] - 
Reading snapshot 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test532776919305995.junit.dir/version-2/snapshot.b
[junit] 2016-04-27 08:15:16,574 [myid:] - INFO  [main:FileTxnSnapLog@298] - 
Snapshotting: 0xb to 
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/ZooKeeper-trunk-solaris/trunk/build/test/tmp/test532776919305995.junit.dir/version-2/snapshot.b
[junit] 2016-04-27 08:15:16,575 [myid:] - INFO  
[main:FourLetterWordMain@85] - connecting to 127.0.0.1 11222
[junit] 2016-04-27 08:15:16,576 [myid:] - INFO  
[NIOServerCxnFactory.AcceptThread:0.0.0.0/0.0.0.0:11222:NIOServerCnxnFactory$AcceptThread@296]
 - Accepted socket connection from /127.0.0.1:50277
[junit] 2016-04-27 08:15:16,577 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@485] - Processing stat command from 
/127.0.0.1:50277
[junit] 2016-04-27 08:15:16,577 [myid:] - INFO  
[NIOWorkerThread-1:StatCommand@49] - Stat command output
[junit] 2016-04-27 08:15:16,578 [myid:] - INFO  
[NIOWorkerThread-1:NIOServerCnxn@607] - Closed socket connection for client 
/127.0.0.1:50277 (no session established for client)
[junit] 2016-04-27 08:15:16,578 [myid:] - INFO  [main:JMXEnv@228] - 
ensureParent:[InMemoryDataTree, StandaloneServer_port]
[junit] 2016-04-27 08:15:16,579 [myid:] - INFO  [main:JMXEnv@245] - 
expect:InMemoryDataTree
[junit] 2016-04-27 08:15:16,579 [myid:] - INFO  [main:JMXEnv@249] - 
found:InMemoryDataTree 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222,name1=InMemoryDataTree
[junit] 2016-04-27 08:15:16,580 [myid:] - INFO  [main:JMXEnv@245] - 
expect:StandaloneServer_port
[junit] 2016-04-27 08:15:16,580 [myid:] - INFO  [main:JMXEnv@249] - 
found:StandaloneServer_port 
org.apache.ZooKeeperService:name0=StandaloneServer_port11222
[junit] 2016-04-27 08:15:16,580 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@82] - Memory used 17647
[junit] 2016-04-27 08:15:16,580 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@87] - Number of threads 24
[junit] 2016-04-27 08:15:16,580 [myid:] - INFO  
[main:JUnit4ZKTestRunner$LoggedInvokeMethod@102] - FINISHED TEST METHOD 
testQuota
[junit] 2016-04-27 08:15:16,581 [myid:] - INFO  [main:ClientBase@537] - 
tearDown starting
[junit] 2016-04-27 08:15:16,772 [myid:] - INFO  [main:ZooKeeper@1110] - 
Session: 0x120d3c6f7ea closed
[junit] 2016-04-27 08:15:16,772 [myid:] - INFO  
[main-EventThread:ClientCnxn$EventThread@543] - EventThread shut down for 
session: 0x120d3c6f7ea
[junit] 2016-04-27 08:15:16,772 [myid:] - INFO  [main:ClientBase@507] - 
STOPPING server
[junit] 2016-04-27 08:15:16,773 [myid:] - INFO  
[ConnnectionExpirer:NIOServerCnxnFactory$ConnectionExpirerThread@583] - 
ConnnectionExpirerThread interrupted
[junit] 2016-04-27 08:15:16,773 [myid:] - INFO  
[NIOServerCxnFactory.SelectorThread-0:NIOServerCnxnFactory$SelectorThread@420] 
- selector thread exitted run method
[junit] 2016-04-27 08:15:16,773 [myid:] - INFO

[jira] [Updated] (ZOOKEEPER-2325) Data inconsistency if all snapshots empty or missing

[jira] [Commented] (ZOOKEEPER-2325) Data inconsistency if all snapshots empty or missing

[GitHub] zookeeper pull request: Update Op.java

[jira] [Updated] (ZOOKEEPER-2325) Data inconsistency if all snapshots empty or missing

Use of GitHub issues instead of JIRA

[jira] [Commented] (ZOOKEEPER-2325) Data inconsistency if all snapshots empty or missing

ZooKeeper-trunk-openjdk7 - Build # 1004 - Still Failing

ZooKeeper_branch35_solaris - Build # 80 - Still Failing

ZooKeeper_branch34_openjdk7 - Build # 1058 - Failure

[jira] [Issue Comment Deleted] (ZOOKEEPER-2416) Remove Java System property usage from ZooKeeper server code

[jira] [Deleted] (ZOOKEEPER-2417) Pogo Support Number +1-844-446 4460| Club Pogo Games Technical support number...

[jira] [Updated] (ZOOKEEPER-2417) Pogo Support Number +1-844-446 4460| Club Pogo Games Technical support number...

[jira] [Commented] (ZOOKEEPER-2139) Support multiple ZooKeeper client, with different configurations, in a single JVM

ZooKeeper-trunk-jdk8 - Build # 578 - Still Failing

ZooKeeper-trunk-solaris - Build # 1137 - Failure

15 matches

Site Navigation

Mail list logo

Footer information