Failed: ZOOKEEPER- PreCommit Build #2272

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2272/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 81.22 MB...]
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2272//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2272//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2272//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] 
 [exec] Remote error: User 'hadoopqa' is not allowed to log in at this 
point in time perhaps due to CAPTCHA requirements or too many failed login 
requests. Go to the user interface and login to clear the problem.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1842:
 exec returned: 1

Total time: 12 minutes 20 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Recording test results
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
[description-setter] Description set: ZOOKEEPER-3105
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Adding one-line test results to commit status...
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting status of 24a60d9822a5c7b29a1683bac862e9df0fa99f0b to FAILURE with url 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2272/ and 
message: 'FAILURE
 1735 tests run, 1 skipped, 1 failed.'
Using context: Jenkins

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2272/

Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.ReconfigLegacyTest.testReconfigRemoveClientFromStatic

Error Message:
null

Stack Trace:
junit.framework.AssertionFailedError
at 
org.apache.zookeeper.server.quorum.ReconfigLegacyTest.testReconfigRemoveClientFromStatic(ReconfigLegacyTest.java:206)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

[GitHub] zookeeper issue #586: Zookeeper 3105:Character coding problem occur when cre...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2272/



---

[GitHub] zookeeper pull request #628: ZOOKEEPER-3140: Allow Followers to host Observe...

[enixon]

Github user enixon commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/628#discussion_r220768593
  
--- Diff: src/java/test/org/apache/zookeeper/test/ObserverMasterTest.java 
---
@@ -0,0 +1,764 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.zookeeper.test;
+
+import static org.apache.zookeeper.test.ClientBase.CONNECTION_TIMEOUT;
+
+import java.io.IOException;
+import java.util.ArrayList;
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.List;
+import java.util.Map;
+import java.util.Set;
+import java.util.concurrent.CountDownLatch;
+import java.util.concurrent.LinkedBlockingQueue;
+import java.util.concurrent.TimeUnit;
+
+import org.apache.zookeeper.AsyncCallback;
+import org.apache.zookeeper.KeeperException;
+import org.apache.zookeeper.jmx.CommonNames;
+import org.apache.zookeeper.jmx.MBeanRegistry;
+import org.apache.zookeeper.jmx.ZKMBeanInfo;
+import org.apache.zookeeper.server.admin.Commands;
+import org.apache.zookeeper.server.quorum.DelayRequestProcessor;
+import org.apache.zookeeper.server.quorum.FollowerZooKeeperServer;
+import org.apache.zookeeper.server.quorum.QuorumPeerConfig;
+import org.apache.zookeeper.server.util.PortForwarder;
+import org.junit.runner.RunWith;
+import org.junit.runners.Parameterized;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+import org.apache.zookeeper.CreateMode;
+import org.apache.zookeeper.KeeperException.ConnectionLossException;
+import org.apache.zookeeper.PortAssignment;
+import org.apache.zookeeper.WatchedEvent;
+import org.apache.zookeeper.Watcher;
+import org.apache.zookeeper.Watcher.Event.KeeperState;
+import org.apache.zookeeper.ZooDefs.Ids;
+import org.apache.zookeeper.ZooKeeper;
+import org.apache.zookeeper.ZooKeeper.States;
+import org.apache.zookeeper.admin.ZooKeeperAdmin;
+import org.apache.zookeeper.server.quorum.QuorumPeerTestBase;
+import org.junit.Assert;
+import org.junit.Test;
+
+import javax.management.Attribute;
+import javax.management.AttributeNotFoundException;
+import javax.management.InstanceNotFoundException;
+import javax.management.InvalidAttributeValueException;
+import javax.management.MBeanException;
+import javax.management.MalformedObjectNameException;
+import javax.management.ObjectName;
+import javax.management.ReflectionException;
+import javax.management.RuntimeMBeanException;
+
+@RunWith(Parameterized.class)
+public class ObserverMasterTest extends QuorumPeerTestBase implements 
Watcher{
+protected static final Logger LOG = 
LoggerFactory.getLogger(ObserverTest.class);
+
+public ObserverMasterTest(Boolean testObserverMaster) {
+this.testObserverMaster = testObserverMaster;
+}
+
+@Parameterized.Parameters
+public static List data() { return Arrays.asList(new Object 
[][] {
+{Boolean.TRUE},
+{Boolean.FALSE}});
+}
+
+private Boolean testObserverMaster;
+
+private CountDownLatch latch;
+ZooKeeper zk;
+private WatchedEvent lastEvent = null;
+
+private int CLIENT_PORT_QP1;
+private int CLIENT_PORT_QP2;
+private int CLIENT_PORT_OBS;
+private int OM_PORT;
+private MainThread q1;
+private MainThread q2;
+private MainThread q3;
+
+private PortForwarder setUp(final int omProxyPort) throws IOException {
--- End diff --

That method will not launch an Observer for us and to get a properly 
configured Observer and PortForwarder out of the method, I would need to 
refactor QuorumServer in QuorumPeerMainTest. Consolidation of the configuration 
setup between ObserverMasterTest and QuorumPeerMainTest is nice to have but I 
don't think it's critical for this patch.


---

ZooKeeper_branch34_jdk8 - Build # 1542 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper_branch34_jdk8/1542/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 42.48 KB...]
[junit] Running org.apache.zookeeper.test.RestoreCommittedLogTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
22.297 sec
[junit] Running org.apache.zookeeper.test.SaslAuthDesignatedClientTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.858 sec
[junit] Running org.apache.zookeeper.test.SaslAuthDesignatedServerTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.771 sec
[junit] Running org.apache.zookeeper.test.SaslAuthFailDesignatedClientTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.713 sec
[junit] Running org.apache.zookeeper.test.SaslAuthFailNotifyTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.676 sec
[junit] Running org.apache.zookeeper.test.SaslAuthFailTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.777 sec
[junit] Running org.apache.zookeeper.test.SaslAuthMissingClientConfigTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.638 sec
[junit] Running org.apache.zookeeper.test.SaslClientTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.078 sec
[junit] Running org.apache.zookeeper.test.SessionInvalidationTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.959 sec
[junit] Running org.apache.zookeeper.test.SessionTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
11.109 sec
[junit] Running org.apache.zookeeper.test.SessionTimeoutTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.981 sec
[junit] Running org.apache.zookeeper.test.StandaloneTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.949 sec
[junit] Running org.apache.zookeeper.test.StatTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.096 sec
[junit] Running org.apache.zookeeper.test.StaticHostProviderTest
[junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.81 sec
[junit] Running org.apache.zookeeper.test.SyncCallTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.717 sec
[junit] Running org.apache.zookeeper.test.TruncateTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
9.615 sec
[junit] Running org.apache.zookeeper.test.UpgradeTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.964 sec
[junit] Running org.apache.zookeeper.test.WatchedEventTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.084 sec
[junit] Running org.apache.zookeeper.test.WatcherFuncTest
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.745 sec
[junit] Running org.apache.zookeeper.test.WatcherTest
[junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
30.392 sec
[junit] Running org.apache.zookeeper.test.ZkDatabaseCorruptionTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
9.524 sec
[junit] Running org.apache.zookeeper.test.ZooKeeperQuotaTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.818 sec
[junit] Running org.apache.jute.BinaryInputArchiveTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.077 sec

fail.build.on.test.failure:

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build.xml:1419: 
The following error occurred while executing this line:
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_jdk8/build.xml:1422: 
Tests failed!

Total time: 48 minutes 44 seconds
Build step 'Invoke Ant' marked build as failure
Archiving artifacts
Recording test results
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



###
## FAILED TESTS (if any) 
##
4 tests failed.
FAILED:  org.apache.zookeeper.server.PurgeTxnTest.testPurge

Error Message:
KeeperErrorCode = ConnectionLoss for /invalidsnap-1414

Stack Trace:
org.apache.zookeeper.KeeperException$ConnectionLossException: KeeperErrorCode = 
ConnectionLoss for /invalidsnap-1414
at org.apache.zookeeper.KeeperException.create(KeeperException.java:102)
at org.apache.zookeeper.KeeperException.create(KeeperException.java:54)
at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:792)
at 

[GitHub] zookeeper pull request #628: ZOOKEEPER-3140: Allow Followers to host Observe...

[enixon]

Github user enixon commented on a diff in the pull request:

https://github.com/apache/zookeeper/pull/628#discussion_r220765363
  
--- Diff: src/java/main/org/apache/zookeeper/server/quorum/Follower.java ---
@@ -196,6 +224,10 @@ protected long getLastQueued() {
 return lastQueued;
 }
 
+public Integer getSyncedObserverSize() {
+return  om == null ? null : om.getNumActiveObservers();
--- End diff --

I was allowing the `synced_observers` stat to distinguish between "this 
follower CAN support observers, it just currently isn't" and "this follower 
CANNOT support observers (and so it isn't)" by outputting a value of 0 or by 
being omitted respectively.

It's a style choice. I'm not terribly attached to my current implementation 
and can change it if you think outputting `synced_observers` of 0 in both cases 
is more straightforward.


---

[GitHub] zookeeper issue #645: ZOOKEEPER-3153: Create MarkDown files and build proces...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2271/



---

Success: ZOOKEEPER- PreCommit Build #2271

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2271/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 41.19 MB...]
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2271//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2271//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2271//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] 
 [exec] Remote error: User 'hadoopqa' is not allowed to log in at this 
point in time perhaps due to CAPTCHA requirements or too many failed login 
requests. Go to the user interface and login to clear the problem.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD SUCCESSFUL
Total time: 34 minutes 58 seconds
Archiving artifacts
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Recording test results
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
[description-setter] Description set: ZOOKEEPER-3153
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Adding one-line test results to commit status...
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting status of 810160cbf0eefd6e92fa31750950ba241c7312e8 to SUCCESS with url 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2271/ and 
message: 'SUCCESS 
 657 tests run, 3 skipped, 0 failed.'
Using context: Jenkins

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2271/

Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8



###
## FAILED TESTS (if any) 
##
All tests passed

ZooKeeper-trunk - Build # 206 - Still Failing

[Apache Jenkins Server]

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

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 146.45 KB...]
[junit] Running org.apache.zookeeper.test.SessionTest in thread 1
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
3.489 sec, Thread: 5, Class: org.apache.zookeeper.test.ServerCnxnTest
[junit] Running org.apache.zookeeper.test.SessionTimeoutTest in thread 5
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.82 sec, Thread: 5, Class: org.apache.zookeeper.test.SessionTimeoutTest
[junit] Running org.apache.zookeeper.test.SessionTrackerCheckTest in thread 
5
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.108 sec, Thread: 5, Class: org.apache.zookeeper.test.SessionTrackerCheckTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
45.208 sec, Thread: 3, Class: org.apache.zookeeper.test.RecoveryTest
[junit] Running org.apache.zookeeper.test.SessionUpgradeTest in thread 5
[junit] Running org.apache.zookeeper.test.StandaloneTest in thread 3
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
31.464 sec, Thread: 2, Class: org.apache.zookeeper.test.RestoreCommittedLogTest
[junit] Running org.apache.zookeeper.test.StatTest in thread 2
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.736 sec, Thread: 3, Class: org.apache.zookeeper.test.StandaloneTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.575 sec, Thread: 2, Class: org.apache.zookeeper.test.StatTest
[junit] Running org.apache.zookeeper.test.StaticHostProviderTest in thread 3
[junit] Running org.apache.zookeeper.test.StringUtilTest in thread 2
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.076 sec, Thread: 2, Class: org.apache.zookeeper.test.StringUtilTest
[junit] Running org.apache.zookeeper.test.SyncCallTest in thread 2
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.832 sec, Thread: 2, Class: org.apache.zookeeper.test.SyncCallTest
[junit] Tests run: 26, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.941 sec, Thread: 3, Class: org.apache.zookeeper.test.StaticHostProviderTest
[junit] Running org.apache.zookeeper.test.TruncateTest in thread 2
[junit] Running org.apache.zookeeper.test.WatchEventWhenAutoResetTest in 
thread 3
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
17.176 sec, Thread: 1, Class: org.apache.zookeeper.test.SessionTest
[junit] Running org.apache.zookeeper.test.WatchedEventTest in thread 1
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.099 sec, Thread: 1, Class: org.apache.zookeeper.test.WatchedEventTest
[junit] Running org.apache.zookeeper.test.WatcherFuncTest in thread 1
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
9.444 sec, Thread: 2, Class: org.apache.zookeeper.test.TruncateTest
[junit] Running org.apache.zookeeper.test.WatcherTest in thread 2
[junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
3.318 sec, Thread: 1, Class: org.apache.zookeeper.test.WatcherFuncTest
[junit] Running org.apache.zookeeper.test.X509AuthTest in thread 1
[junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.086 sec, Thread: 1, Class: org.apache.zookeeper.test.X509AuthTest
[junit] Running org.apache.zookeeper.test.ZkDatabaseCorruptionTest in 
thread 1
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
22.691 sec, Thread: 5, Class: org.apache.zookeeper.test.SessionUpgradeTest
[junit] Running org.apache.zookeeper.test.ZooKeeperQuotaTest in thread 5
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.125 sec, Thread: 5, Class: org.apache.zookeeper.test.ZooKeeperQuotaTest
[junit] Running org.apache.jute.BinaryInputArchiveTest in thread 5
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.074 sec, Thread: 5, Class: org.apache.jute.BinaryInputArchiveTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
22.713 sec, Thread: 3, Class: 
org.apache.zookeeper.test.WatchEventWhenAutoResetTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
10.996 sec, Thread: 1, Class: org.apache.zookeeper.test.ZkDatabaseCorruptionTest
[junit] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
32.474 sec, Thread: 2, Class: org.apache.zookeeper.test.WatcherTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
388.172 sec, Thread: 4, Class: org.apache.zookeeper.test.DisconnectedWatcherTest
[junit] Tests run: 106, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
429.082 sec, 

[jira] [Commented] (ZOOKEEPER-1936) Server exits when unable to create data directory due to race

[Ted Yu (JIRA)]

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

Ted Yu commented on ZOOKEEPER-1936:
---

Can you outline how you plan to fix ?

thanks

> Server exits when unable to create data directory due to race 
> --
>
> Key: ZOOKEEPER-1936
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1936
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: server
>Affects Versions: 3.4.6, 3.5.0
>Reporter: Harald Musum
>Assignee: Ted Yu
>Priority: Minor
> Fix For: 3.6.0, 3.5.5
>
> Attachments: ZOOKEEPER-1936.branch-3.4.patch, ZOOKEEPER-1936.patch, 
> ZOOKEEPER-1936.v2.patch, ZOOKEEPER-1936.v3.patch, ZOOKEEPER-1936.v3.patch, 
> ZOOKEEPER-1936.v4.patch, ZOOKEEPER-1936.v5.patch
>
>
> We sometime see issues with ZooKeeper server not starting and seeing this 
> error in the log:
> [2014-05-27 09:29:48.248] ERROR   : -   
> .org.apache.zookeeper.server.ZooKeeperServerMainUnexpected exception,
> exiting abnormally\nexception=\njava.io.IOException: Unable to create data
> directory /home/y/var/zookeeper/version-2\n\tat
> org.apache.zookeeper.server.persistence.FileTxnSnapLog.(FileTxnSnapLog.java:85)\n\tat
> org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(ZooKeeperServerMain.java:103)\n\tat
> org.apache.zookeeper.server.ZooKeeperServerMain.initializeAndRun(ZooKeeperServerMain.java:86)\n\tat
> org.apache.zookeeper.server.ZooKeeperServerMain.main(ZooKeeperServerMain.java:52)\n\tat
> org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:116)\n\tat
> org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:78)\n\t
> [...]
> Stack trace from JVM gives this:
> "PurgeTask" daemon prio=10 tid=0x0201d000 nid=0x1727 runnable
> [0x7f55d7dc7000]
>java.lang.Thread.State: RUNNABLE
> at java.io.UnixFileSystem.createDirectory(Native Method)
> at java.io.File.mkdir(File.java:1310)
> at java.io.File.mkdirs(File.java:1337)
> at
> org.apache.zookeeper.server.persistence.FileTxnSnapLog.(FileTxnSnapLog.java:84)
> at org.apache.zookeeper.server.PurgeTxnLog.purge(PurgeTxnLog.java:68)
> at
> org.apache.zookeeper.server.DatadirCleanupManager$PurgeTask.run(DatadirCleanupManager.java:140)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> "zookeeper server" prio=10 tid=0x027df800 nid=0x1715 runnable
> [0x7f55d7ed8000]
>java.lang.Thread.State: RUNNABLE
> at java.io.UnixFileSystem.createDirectory(Native Method)
> at java.io.File.mkdir(File.java:1310)
> at java.io.File.mkdirs(File.java:1337)
> at
> org.apache.zookeeper.server.persistence.FileTxnSnapLog.(FileTxnSnapLog.java:84)
> at
> org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(ZooKeeperServerMain.java:103)
> at
> org.apache.zookeeper.server.ZooKeeperServerMain.initializeAndRun(ZooKeeperServerMain.java:86)
> at
> org.apache.zookeeper.server.ZooKeeperServerMain.main(ZooKeeperServerMain.java:52)
> at
> org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:116)
> at
> org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:78)
> [...]
> So it seems that when autopurge is used (as it is in our case), it might 
> happen at the same time as starting the server itself. In FileTxnSnapLog() it 
> will check if the directory exists and create it if not. These two tasks do 
> this at the same time, and mkdir fails and server exits the JVM.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] zookeeper pull request #645: ZOOKEEPER-3153: Create MarkDown files and build...

[tamaashu]

GitHub user tamaashu opened a pull request:

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

ZOOKEEPER-3153: Create MarkDown files and build process for them for …

…branch 3.4

In this sub-task we have transformed the Forest XML documents into MarkDown 
(.md) files and provided a (maven based) solution to create HTML documentation 
from them.
PDF support is dropped since it is not really used and makes everything 
overcomplicated.

The generated HTML content looks similar to the one generated from Forest 
XMLs, but not identical with them.

Change-Id: Id35984eca5d37b9e3074eab939be5c9b4cc80257

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

$ git pull https://github.com/tamaashu/zookeeper ZOOKEEPER-3153-3.4

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

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


commit 810160cbf0eefd6e92fa31750950ba241c7312e8
Author: Tamas Penzes 
Date:   2018-09-26T22:54:02Z

ZOOKEEPER-3153: Create MarkDown files and build process for them for branch 
3.4

In this sub-task we have transformed the Forest XML documents into MarkDown 
(.md) files and provided a (maven based) solution to create HTML documentation 
from them.
PDF support is dropped since it is not really used and makes everything 
overcomplicated.

The generated HTML content looks similar to the one generated from Forest 
XMLs, but not identical with them.

Change-Id: Id35984eca5d37b9e3074eab939be5c9b4cc80257




---

Failed: ZOOKEEPER- PreCommit Build #2270

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2270/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 75.69 MB...]
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2270//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2270//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2270//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] Session logged out. Session was 
JSESSIONID=829616A093F6514E01EF9281D4E5026F.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1945:
 exec returned: 1

Total time: 16 minutes 39 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Recording test results
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
[description-setter] Description set: ZOOKEEPER-3032
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Adding one-line test results to commit status...
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting status of 52e94e2147fbbac1d9c8f8bac38b974802be1864 to FAILURE with url 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2270/ and 
message: 'FAILURE
 1735 tests run, 1 skipped, 2 failed.'
Using context: Jenkins

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2270/

Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8



###
## FAILED TESTS (if any) 
##
2 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElectionWithDisloyalVoter_stillHasMajority

Error Message:
Server 0 should have joined quorum by now

Stack Trace:
junit.framework.AssertionFailedError: Server 0 should have joined quorum by now
at 
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElection(QuorumPeerMainTest.java:1486)
at 
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElectionWithDisloyalVoter_stillHasMajority(QuorumPeerMainTest.java:1435)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)


FAILED:  
org.apache.zookeeper.server.quorum.ReconfigLegacyTest.testReconfigRemoveClientFromStatic

Error Message:
null

Stack Trace:
junit.framework.AssertionFailedError
at 
org.apache.zookeeper.server.quorum.ReconfigLegacyTest.testReconfigRemoveClientFromStatic(ReconfigLegacyTest.java:206)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

[GitHub] zookeeper issue #633: ZOOKEEPER-3032 - MAVEN MIGRATION - move java server, c...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2270/



---

[GitHub] zookeeper issue #633: ZOOKEEPER-3032 - MAVEN MIGRATION - move java server, c...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2269/



---

Failed: ZOOKEEPER- PreCommit Build #2269

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2269/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 71.06 MB...]
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2269//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2269//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2269//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] Session logged out. Session was 
JSESSIONID=5F5CB683E49DA8049755FA75A17EFB85.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess’
 and 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess’
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1945:
 exec returned: 1

Total time: 18 minutes 58 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Recording test results
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
[description-setter] Description set: ZOOKEEPER-3032
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Adding one-line test results to commit status...
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting status of 801ccca3cfaf626782d42f5fbd63c13559da1676 to FAILURE with url 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2269/ and 
message: 'FAILURE
 1735 tests run, 1 skipped, 2 failed.'
Using context: Jenkins

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2269/

Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8



###
## FAILED TESTS (if any) 
##
2 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElectionWithDisloyalVoter_stillHasMajority

Error Message:
Server 0 should have joined quorum by now

Stack Trace:
junit.framework.AssertionFailedError: Server 0 should have joined quorum by now
at 
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElection(QuorumPeerMainTest.java:1486)
at 
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElectionWithDisloyalVoter_stillHasMajority(QuorumPeerMainTest.java:1435)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)


FAILED:  
org.apache.zookeeper.server.quorum.ReconfigLegacyTest.testReconfigRemoveClientFromStatic

Error Message:
null

Stack Trace:
junit.framework.AssertionFailedError
at 
org.apache.zookeeper.server.quorum.ReconfigLegacyTest.testReconfigRemoveClientFromStatic(ReconfigLegacyTest.java:206)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

[GitHub] zookeeper issue #633: ZOOKEEPER-3032 - MAVEN MIGRATION - move java server, c...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2268/



---

Failed: ZOOKEEPER- PreCommit Build #2268

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2268/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 80.10 MB...]
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2268//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2268//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2268//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] Session logged out. Session was 
JSESSIONID=A750869B40F7116330F7414E0275CA04.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess’
 and 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess’
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1945:
 exec returned: 1

Total time: 19 minutes 0 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Recording test results
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
[description-setter] Description set: ZOOKEEPER-3032
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Adding one-line test results to commit status...
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting status of 2b4fcf3285fec2b773cd471dd2fcaeaf694c9df4 to FAILURE with url 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2268/ and 
message: 'FAILURE
 1735 tests run, 1 skipped, 3 failed.'
Using context: Jenkins

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2268/

Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8



###
## FAILED TESTS (if any) 
##
3 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.CommitProcessorConcurrencyTest.noStarvationOfNonLocalCommittedRequestsTest

Error Message:
test timed out after 1000 milliseconds

Stack Trace:
org.junit.runners.model.TestTimedOutException: test timed out after 1000 
milliseconds
at 
org.apache.zookeeper.server.quorum.CommitProcessor.run(CommitProcessor.java:200)
at 
org.apache.zookeeper.server.quorum.CommitProcessorConcurrencyTest.noStarvationOfNonLocalCommittedRequestsTest(CommitProcessorConcurrencyTest.java:300)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.lang.Thread.run(Thread.java:748)


FAILED:  
org.apache.zookeeper.test.DisconnectedWatcherTest.testManyChildWatchersAutoReset

Error Message:
test timed out after 84 milliseconds

Stack Trace:
org.junit.runners.model.TestTimedOutException: test timed out after 84 
milliseconds
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:502)
at org.apache.zookeeper.ClientCnxn.submitRequest(ClientCnxn.java:1524)
at 

[GitHub] zookeeper issue #633: ZOOKEEPER-3032 - MAVEN MIGRATION - move java server, c...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2267/



---

Failed: ZOOKEEPER- PreCommit Build #2267

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2267/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 81.71 MB...]
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2267//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2267//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2267//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] Session logged out. Session was 
JSESSIONID=7AE521C19B6BA6C8284067ECB3C102B2.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess’
 and 
‘/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess’
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1945:
 exec returned: 1

Total time: 19 minutes 16 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Recording test results
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
[description-setter] Description set: ZOOKEEPER-3032
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Adding one-line test results to commit status...
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting status of d8bfbf9f9120b47cd3419c9fa82b45e1c179d707 to FAILURE with url 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2267/ and 
message: 'FAILURE
 1735 tests run, 1 skipped, 1 failed.'
Using context: Jenkins

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2267/

Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.ReconfigLegacyTest.testReconfigRemoveClientFromStatic

Error Message:
null

Stack Trace:
junit.framework.AssertionFailedError
at 
org.apache.zookeeper.server.quorum.ReconfigLegacyTest.testReconfigRemoveClientFromStatic(ReconfigLegacyTest.java:206)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

[jira] [Comment Edited] (ZOOKEEPER-3156) ZOOKEEPER-2184 causes kerberos principal to not have resolved host name

[Andor Molnar (JIRA)]

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

Andor Molnar edited comment on ZOOKEEPER-3156 at 9/26/18 8:13 PM:
--

We should use getCanonicalHostName() to force reverse ip lookup and get the 
FQDN of the server according to this javadoc:
https://docs.oracle.com/javase/7/docs/api/java/net/InetAddress.html#getCanonicalHostName()

Introducing a switch to enable reverse dns lookups would be inline with 
Kerberos client behaviour:
http://web.mit.edu/kerberos/krb5-current/doc/admin/princ_dns.html

In the krb5 client you can disable canonicalization with rdns=false setting.

I can put together a patch tomorrow if needed.


was (Author: andorm):
We should use getCanonicalHostName() to force reverse ip lookup and get the 
FQDN of the server according to this javadoc:
https://docs.oracle.com/javase/7/docs/api/java/net/InetAddress.html#getCanonicalHostName()

Introducing a switch to enable reverse dns lookups would be inline with 
Kerberos client behaviour:
http://web.mit.edu/kerberos/krb5-current/doc/admin/princ_dns.html

In the krb5 client you can disable canonicalization with rdns=false setting.

> ZOOKEEPER-2184 causes kerberos principal to not have resolved host name
> ---
>
> Key: ZOOKEEPER-3156
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3156
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.6.0, 3.4.13, 3.5.5
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>Priority: Blocker
>
> Prior to ZOOKEEPER-2184 the zookeeper client would canonicalize a configured 
> host name before creating the SASL client which is used to create the 
> principal name.  After ZOOKEEPER-2184 that canonicalization does not happen 
> so the principal that the ZK client tries to use when it is configured to 
> talk to a CName is different between 3.4.13 and all previous versions of ZK.
>  
> For example
>  
> zk1.mycluster.mycompany.com maps to real-node.mycompany.com.
>  
> 3.4.13 will want the server to have 
> [zookeeper/zk1.mycluster@kdc.mycompany.com|mailto:zookeeper/zk1.mycluster@kdc.mycompany.com]
> 3.4.12 wants the server to have 
> [zookeeper/real-node.mycompany@kdc.mycompany.com|mailto:zookeeper/real-node.mycompany@kdc.mycompany.com]
>  
> This makes 3.4.13 incompatible with many ZK setups currently in existence.  
> It would be nice to have that resolution be optional because in some cases it 
> might be nice to have a single principal tied to the cname.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ZOOKEEPER-3156) ZOOKEEPER-2184 causes kerberos principal to not have resolved host name

[Andor Molnar (JIRA)]

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

Andor Molnar commented on ZOOKEEPER-3156:
-

We should use getCanonicalHostName() to force reverse ip lookup and get the 
FQDN of the server according to this javadoc:
https://docs.oracle.com/javase/7/docs/api/java/net/InetAddress.html#getCanonicalHostName()

Introducing a switch to enable reverse dns lookups would be inline with 
Kerberos client behaviour:
http://web.mit.edu/kerberos/krb5-current/doc/admin/princ_dns.html

In the krb5 client you can disable canonicalization with rdns=false setting.

> ZOOKEEPER-2184 causes kerberos principal to not have resolved host name
> ---
>
> Key: ZOOKEEPER-3156
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3156
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.6.0, 3.4.13, 3.5.5
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>Priority: Blocker
>
> Prior to ZOOKEEPER-2184 the zookeeper client would canonicalize a configured 
> host name before creating the SASL client which is used to create the 
> principal name.  After ZOOKEEPER-2184 that canonicalization does not happen 
> so the principal that the ZK client tries to use when it is configured to 
> talk to a CName is different between 3.4.13 and all previous versions of ZK.
>  
> For example
>  
> zk1.mycluster.mycompany.com maps to real-node.mycompany.com.
>  
> 3.4.13 will want the server to have 
> [zookeeper/zk1.mycluster@kdc.mycompany.com|mailto:zookeeper/zk1.mycluster@kdc.mycompany.com]
> 3.4.12 wants the server to have 
> [zookeeper/real-node.mycompany@kdc.mycompany.com|mailto:zookeeper/real-node.mycompany@kdc.mycompany.com]
>  
> This makes 3.4.13 incompatible with many ZK setups currently in existence.  
> It would be nice to have that resolution be optional because in some cases it 
> might be nice to have a single principal tied to the cname.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ZOOKEEPER-3156) ZOOKEEPER-2184 causes kerberos principal to not have resolved host name

[Andor Molnar (JIRA)]

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

Andor Molnar commented on ZOOKEEPER-3156:
-

Is this the logic that we're talking about?
{code:java}
if (ZooKeeperSaslClient.isEnabled()) {
try {
String principalUserName = System.getProperty(
ZK_SASL_CLIENT_USERNAME, "zookeeper");
zooKeeperSaslClient =
new ZooKeeperSaslClient(
principalUserName+"/"+addr.getHostName());
...{code}

> ZOOKEEPER-2184 causes kerberos principal to not have resolved host name
> ---
>
> Key: ZOOKEEPER-3156
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3156
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.6.0, 3.4.13, 3.5.5
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>Priority: Blocker
>
> Prior to ZOOKEEPER-2184 the zookeeper client would canonicalize a configured 
> host name before creating the SASL client which is used to create the 
> principal name.  After ZOOKEEPER-2184 that canonicalization does not happen 
> so the principal that the ZK client tries to use when it is configured to 
> talk to a CName is different between 3.4.13 and all previous versions of ZK.
>  
> For example
>  
> zk1.mycluster.mycompany.com maps to real-node.mycompany.com.
>  
> 3.4.13 will want the server to have 
> [zookeeper/zk1.mycluster@kdc.mycompany.com|mailto:zookeeper/zk1.mycluster@kdc.mycompany.com]
> 3.4.12 wants the server to have 
> [zookeeper/real-node.mycompany@kdc.mycompany.com|mailto:zookeeper/real-node.mycompany@kdc.mycompany.com]
>  
> This makes 3.4.13 incompatible with many ZK setups currently in existence.  
> It would be nice to have that resolution be optional because in some cases it 
> might be nice to have a single principal tied to the cname.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ZOOKEEPER-3156) ZOOKEEPER-2184 causes kerberos principal to not have resolved host name

[Andor Molnar (JIRA)]

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

Andor Molnar commented on ZOOKEEPER-3156:
-

I like the idea of having a configuration switch for that, because I'm not 
entirely sure what would be the right behaviour.

[~revans2] Do you have a patch already?

> ZOOKEEPER-2184 causes kerberos principal to not have resolved host name
> ---
>
> Key: ZOOKEEPER-3156
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3156
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.6.0, 3.4.13, 3.5.5
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>Priority: Blocker
>
> Prior to ZOOKEEPER-2184 the zookeeper client would canonicalize a configured 
> host name before creating the SASL client which is used to create the 
> principal name.  After ZOOKEEPER-2184 that canonicalization does not happen 
> so the principal that the ZK client tries to use when it is configured to 
> talk to a CName is different between 3.4.13 and all previous versions of ZK.
>  
> For example
>  
> zk1.mycluster.mycompany.com maps to real-node.mycompany.com.
>  
> 3.4.13 will want the server to have 
> [zookeeper/zk1.mycluster@kdc.mycompany.com|mailto:zookeeper/zk1.mycluster@kdc.mycompany.com]
> 3.4.12 wants the server to have 
> [zookeeper/real-node.mycompany@kdc.mycompany.com|mailto:zookeeper/real-node.mycompany@kdc.mycompany.com]
>  
> This makes 3.4.13 incompatible with many ZK setups currently in existence.  
> It would be nice to have that resolution be optional because in some cases it 
> might be nice to have a single principal tied to the cname.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (ZOOKEEPER-3156) ZOOKEEPER-2184 causes kerberos principal to not have resolved host name

[Enrico Olivelli (JIRA)]

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

Enrico Olivelli edited comment on ZOOKEEPER-3156 at 9/26/18 7:01 PM:
-

I see the problem.

Do you have already a patch?

Maybe a good idea is to add a client configuration flag or system property.

 


was (Author: eolivelli):
I see the problem.

So you have already a patch?

Maybe a good idea is to add a client configuration flag or system property.

 

> ZOOKEEPER-2184 causes kerberos principal to not have resolved host name
> ---
>
> Key: ZOOKEEPER-3156
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3156
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.6.0, 3.4.13, 3.5.5
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>Priority: Blocker
>
> Prior to ZOOKEEPER-2184 the zookeeper client would canonicalize a configured 
> host name before creating the SASL client which is used to create the 
> principal name.  After ZOOKEEPER-2184 that canonicalization does not happen 
> so the principal that the ZK client tries to use when it is configured to 
> talk to a CName is different between 3.4.13 and all previous versions of ZK.
>  
> For example
>  
> zk1.mycluster.mycompany.com maps to real-node.mycompany.com.
>  
> 3.4.13 will want the server to have 
> [zookeeper/zk1.mycluster@kdc.mycompany.com|mailto:zookeeper/zk1.mycluster@kdc.mycompany.com]
> 3.4.12 wants the server to have 
> [zookeeper/real-node.mycompany@kdc.mycompany.com|mailto:zookeeper/real-node.mycompany@kdc.mycompany.com]
>  
> This makes 3.4.13 incompatible with many ZK setups currently in existence.  
> It would be nice to have that resolution be optional because in some cases it 
> might be nice to have a single principal tied to the cname.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

ZooKeeper-trunk-windows-cmake - Build # 2951 - Still Failing

[Apache Jenkins Server]

See https://builds.apache.org/job/ZooKeeper-trunk-windows-cmake/2951/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 9.79 KB...]
[ivy:retrieve]  confs: [javacc]
[ivy:retrieve]  found net.java.dev.javacc#javacc;5.0 in maven2
[ivy:retrieve] :: resolution report :: resolve 38ms :: artifacts dl 0ms
-
|  |modules||   artifacts   |
|   conf   | number| search|dwnlded|evicted|| number|dwnlded|
-
|  javacc  |   1   |   0   |   0   |   0   ||   1   |   0   |
-
[ivy:retrieve] :: retrieving :: org.apache.zookeeper#zookeeper
[ivy:retrieve]  confs: [javacc]
[ivy:retrieve]  1 artifacts copied, 0 already retrieved (291kB/11ms)

generate_jute_parser:
[mkdir] Created dir: 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-windows-cmake\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 = 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-windows-cmake\ivysettings.xml
 [move] Moving 1 file to 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-windows-cmake\build\javacc\lib
   [javacc] Java Compiler Compiler Version 5.0 (Parser Generator)
   [javacc] (type "javacc" with no arguments for help)
   [javacc] Reading from file 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-windows-cmake\zookeeper-jute\src\main\java\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:
[javac] Compiling 39 source files to 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-windows-cmake\build\classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.8
[javac] 1 warning

compile_jute_uptodate:

compile_jute:
[mkdir] Created dir: 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-windows-cmake\src\java\generated
[mkdir] Created dir: 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-windows-cmake\zookeeper-client\zookeeper-client-c\generated
 [java] ../../../zookeeper-jute/src/main/resources/zookeeper.jute Parsed 
Successfully
 [java] ../../../zookeeper-jute/src/main/resources/zookeeper.jute Parsed 
Successfully
[touch] Creating 
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-windows-cmake\src\java\generated\.generated

BUILD SUCCESSFUL
Total time: 5 seconds
[ZooKeeper-trunk-windows-cmake] $ cmd /c call 
F:\jenkins\jenkins-slave\temp\jenkins78520160839977132.bat

f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-windows-cmake>cd src/c 
The system cannot find the path specified.

f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-windows-cmake>cmake . 
CMake Error: The source directory 
"F:/jenkins/jenkins-slave/workspace/ZooKeeper-trunk-windows-cmake" does not 
appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.

f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-windows-cmake>cmake --build 
. 
Error: could not load cache

f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-windows-cmake>exit 1 
Build step 'Execute Windows batch command' marked build as failure
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any



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

[jira] [Commented] (ZOOKEEPER-3156) ZOOKEEPER-2184 causes kerberos principal to not have resolved host name

[Enrico Olivelli (JIRA)]

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

Enrico Olivelli commented on ZOOKEEPER-3156:


I see the problem.

So you have already a patch?

Maybe a good idea is to add a client configuration flag or system property.

 

> ZOOKEEPER-2184 causes kerberos principal to not have resolved host name
> ---
>
> Key: ZOOKEEPER-3156
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3156
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.6.0, 3.4.13, 3.5.5
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>Priority: Blocker
>
> Prior to ZOOKEEPER-2184 the zookeeper client would canonicalize a configured 
> host name before creating the SASL client which is used to create the 
> principal name.  After ZOOKEEPER-2184 that canonicalization does not happen 
> so the principal that the ZK client tries to use when it is configured to 
> talk to a CName is different between 3.4.13 and all previous versions of ZK.
>  
> For example
>  
> zk1.mycluster.mycompany.com maps to real-node.mycompany.com.
>  
> 3.4.13 will want the server to have 
> [zookeeper/zk1.mycluster@kdc.mycompany.com|mailto:zookeeper/zk1.mycluster@kdc.mycompany.com]
> 3.4.12 wants the server to have 
> [zookeeper/real-node.mycompany@kdc.mycompany.com|mailto:zookeeper/real-node.mycompany@kdc.mycompany.com]
>  
> This makes 3.4.13 incompatible with many ZK setups currently in existence.  
> It would be nice to have that resolution be optional because in some cases it 
> might be nice to have a single principal tied to the cname.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ZOOKEEPER-3156) ZOOKEEPER-2184 causes kerberos principal to not have resolved host name

[Robert Joseph Evans (JIRA)]

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

Robert Joseph Evans updated ZOOKEEPER-3156:
---
Affects Version/s: 3.5.5
   3.6.0

> ZOOKEEPER-2184 causes kerberos principal to not have resolved host name
> ---
>
> Key: ZOOKEEPER-3156
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3156
> Project: ZooKeeper
>  Issue Type: Bug
>  Components: java client
>Affects Versions: 3.6.0, 3.4.13, 3.5.5
>Reporter: Robert Joseph Evans
>Assignee: Robert Joseph Evans
>Priority: Blocker
>
> Prior to ZOOKEEPER-2184 the zookeeper client would canonicalize a configured 
> host name before creating the SASL client which is used to create the 
> principal name.  After ZOOKEEPER-2184 that canonicalization does not happen 
> so the principal that the ZK client tries to use when it is configured to 
> talk to a CName is different between 3.4.13 and all previous versions of ZK.
>  
> For example
>  
> zk1.mycluster.mycompany.com maps to real-node.mycompany.com.
>  
> 3.4.13 will want the server to have 
> [zookeeper/zk1.mycluster@kdc.mycompany.com|mailto:zookeeper/zk1.mycluster@kdc.mycompany.com]
> 3.4.12 wants the server to have 
> [zookeeper/real-node.mycompany@kdc.mycompany.com|mailto:zookeeper/real-node.mycompany@kdc.mycompany.com]
>  
> This makes 3.4.13 incompatible with many ZK setups currently in existence.  
> It would be nice to have that resolution be optional because in some cases it 
> might be nice to have a single principal tied to the cname.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] zookeeper issue #644: ZOOKEEPER-3153: Create MarkDown files and build proces...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2266/



---

Success: ZOOKEEPER- PreCommit Build #2266

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2266/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 78.66 MB...]
 [exec] +1 core tests.  The patch passed core unit tests.
 [exec] 
 [exec] +1 contrib tests.  The patch passed contrib unit tests.
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2266//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2266//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2266//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] Session logged out. Session was 
JSESSIONID=3E3F13506858416AF25B5A4986424B20.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD SUCCESSFUL
Total time: 17 minutes 46 seconds
Archiving artifacts
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Recording test results
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
[description-setter] Description set: ZOOKEEPER-3153
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Adding one-line test results to commit status...
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting status of 017b75dda1804a457ae8e3be65c06d58252c6fc4 to SUCCESS with url 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2266/ and 
message: 'SUCCESS 
 1681 tests run, 2 skipped, 0 failed.'
Using context: Jenkins

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2266/

Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Email was triggered for: Success
Sending email for trigger: Success
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8



###
## FAILED TESTS (if any) 
##
All tests passed

[GitHub] zookeeper pull request #644: ZOOKEEPER-3153: Create MarkDown files and build...

[tamaashu]

GitHub user tamaashu opened a pull request:

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

ZOOKEEPER-3153: Create MarkDown files and build process for them for …

…branch 3.5

In this sub-task we have transformed the Forest XML documents into MarkDown 
(.md) files and provided a (maven based) solution to create HTML documentation 
from them.
PDF support is dropped since it is not really used and makes everything 
overcomplicated.

The generated HTML content looks similar to the one generated from Forest 
XMLs, but not identical with them.

Change-Id: Id35984eca5d37b9e3074eab939be5c9b4cc80257

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

$ git pull https://github.com/tamaashu/zookeeper ZOOKEEPER-3153-3.5

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

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


commit 017b75dda1804a457ae8e3be65c06d58252c6fc4
Author: Tamas Penzes 
Date:   2018-09-26T17:39:30Z

ZOOKEEPER-3153: Create MarkDown files and build process for them for branch 
3.5

In this sub-task we have transformed the Forest XML documents into MarkDown 
(.md) files and provided a (maven based) solution to create HTML documentation 
from them.
PDF support is dropped since it is not really used and makes everything 
overcomplicated.

The generated HTML content looks similar to the one generated from Forest 
XMLs, but not identical with them.

Change-Id: Id35984eca5d37b9e3074eab939be5c9b4cc80257




---

[GitHub] zookeeper issue #633: ZOOKEEPER-3032 - MAVEN MIGRATION - move java server, c...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2265/



---

Failed: ZOOKEEPER- PreCommit Build #2265

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2265/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 67.72 MB...]
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2265//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2265//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2265//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] Session logged out. Session was 
JSESSIONID=4DB970F7C181C90A5318BC6693BA5403.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1945:
 exec returned: 1

Total time: 12 minutes 7 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Recording test results
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
[description-setter] Description set: ZOOKEEPER-3032
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Adding one-line test results to commit status...
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting status of 6e21a6ee56ed95de331bec817891acb68c2ee1f0 to FAILURE with url 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2265/ and 
message: 'FAILURE
 1735 tests run, 1 skipped, 2 failed.'
Using context: Jenkins

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2265/

Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8



###
## FAILED TESTS (if any) 
##
2 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElectionWithDisloyalVoter_stillHasMajority

Error Message:
Server 0 should have joined quorum by now

Stack Trace:
junit.framework.AssertionFailedError: Server 0 should have joined quorum by now
at 
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElection(QuorumPeerMainTest.java:1486)
at 
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testLeaderElectionWithDisloyalVoter_stillHasMajority(QuorumPeerMainTest.java:1435)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)


FAILED:  
org.apache.zookeeper.server.quorum.ReconfigLegacyTest.testReconfigRemoveClientFromStatic

Error Message:
null

Stack Trace:
junit.framework.AssertionFailedError
at 
org.apache.zookeeper.server.quorum.ReconfigLegacyTest.testReconfigRemoveClientFromStatic(ReconfigLegacyTest.java:206)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

[jira] [Created] (ZOOKEEPER-3156) ZOOKEEPER-2184 causes kerberos principal to not have resolved host name

[Robert Joseph Evans (JIRA)]

Robert Joseph Evans created ZOOKEEPER-3156:
--

 Summary: ZOOKEEPER-2184 causes kerberos principal to not have 
resolved host name
 Key: ZOOKEEPER-3156
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3156
 Project: ZooKeeper
  Issue Type: Bug
  Components: java client
Affects Versions: 3.4.13
Reporter: Robert Joseph Evans
Assignee: Robert Joseph Evans


Prior to ZOOKEEPER-2184 the zookeeper client would canonicalize a configured 
host name before creating the SASL client which is used to create the principal 
name.  After ZOOKEEPER-2184 that canonicalization does not happen so the 
principal that the ZK client tries to use when it is configured to talk to a 
CName is different between 3.4.13 and all previous versions of ZK.

 

For example

 

zk1.mycluster.mycompany.com maps to real-node.mycompany.com.

 

3.4.13 will want the server to have 
[zookeeper/zk1.mycluster@kdc.mycompany.com|mailto:zookeeper/zk1.mycluster@kdc.mycompany.com]

3.4.12 wants the server to have 
[zookeeper/real-node.mycompany@kdc.mycompany.com|mailto:zookeeper/real-node.mycompany@kdc.mycompany.com]

 

This makes 3.4.13 incompatible with many ZK setups currently in existence.  It 
would be nice to have that resolution be optional because in some cases it 
might be nice to have a single principal tied to the cname.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] zookeeper issue #639: ZOOKEEPER-2122: add openssl to zookeeper c client to s...

[roodkcab]

Github user roodkcab commented on the issue:

https://github.com/apache/zookeeper/pull/639
  
problem solved, I've already push the latest code into a new branch and 
will run more test cases until I can confirm it works.


---

Jenkins build is back to normal : ZooKeeper-trunk-owasp #122

[Apache Jenkins Server]

See 

Failed: ZOOKEEPER- PreCommit Build #2264

[Apache Jenkins Server]

Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2264/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 81.45 MB...]
 [exec] 
 [exec] Test results: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2264//testReport/
 [exec] Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2264//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
 [exec] Console output: 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2264//console
 [exec] 
 [exec] This message is automatically generated.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Adding comment to Jira.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] 
 [exec] Error: No value specified for option "issue"
 [exec] Session logged out. Session was 
JSESSIONID=BF14787DD16948206D243AD5AEC082E6.
 [exec] 
 [exec] 
 [exec] 
==
 [exec] 
==
 [exec] Finished build.
 [exec] 
==
 [exec] 
==
 [exec] 
 [exec] 
 [exec] mv: 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 and 
'/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/patchprocess'
 are the same file

BUILD FAILED
/home/jenkins/jenkins-slave/workspace/PreCommit-ZOOKEEPER-github-pr-build/build.xml:1842:
 exec returned: 1

Total time: 12 minutes 31 seconds
Build step 'Execute shell' marked build as failure
Archiving artifacts
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Recording test results
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
[description-setter] Description set: ZOOKEEPER-3153
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Adding one-line test results to commit status...
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting status of 72d30441c4565434fc7870fb2e6fb2ee031184cb to FAILURE with url 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2264/ and 
message: 'FAILURE
 1735 tests run, 1 skipped, 1 failed.'
Using context: Jenkins

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2264/

Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8
Setting JDK_1_8_LATEST__HOME=/home/jenkins/tools/java/latest1.8



###
## FAILED TESTS (if any) 
##
1 tests failed.
FAILED:  
org.apache.zookeeper.server.quorum.ReconfigLegacyTest.testReconfigRemoveClientFromStatic

Error Message:
null

Stack Trace:
junit.framework.AssertionFailedError
at 
org.apache.zookeeper.server.quorum.ReconfigLegacyTest.testReconfigRemoveClientFromStatic(ReconfigLegacyTest.java:206)
at 
org.apache.zookeeper.JUnit4ZKTestRunner$LoggedInvokeMethod.evaluate(JUnit4ZKTestRunner.java:79)

[GitHub] zookeeper issue #643: ZOOKEEPER-3153: Create MarkDown files and build proces...

[asfgit]

Github user asfgit commented on the issue:

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

Refer to this link for build results (access rights to CI server needed): 
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/2264/



---

[jira] [Updated] (ZOOKEEPER-3155) Remove Forrest XMLs and their build process from the project

[Tamas Penzes (JIRA)]

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

Tamas Penzes updated ZOOKEEPER-3155:

Description: Remove obsoleted Forrest XML files and their build process 
from the project.  (was: Remove obsoleted Forest XML files and their build 
process from the project.)

> Remove Forrest XMLs and their build process from the project
> 
>
> Key: ZOOKEEPER-3155
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3155
> Project: ZooKeeper
>  Issue Type: Sub-task
>Reporter: Tamas Penzes
>Priority: Major
>
> Remove obsoleted Forrest XML files and their build process from the project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ZOOKEEPER-3155) Remove Forrest XMLs and their build process from the project

[Tamas Penzes (JIRA)]

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

Tamas Penzes updated ZOOKEEPER-3155:

Summary: Remove Forrest XMLs and their build process from the project  
(was: Remove Forest XMLs and their build process from the project)

> Remove Forrest XMLs and their build process from the project
> 
>
> Key: ZOOKEEPER-3155
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3155
> Project: ZooKeeper
>  Issue Type: Sub-task
>Reporter: Tamas Penzes
>Priority: Major
>
> Remove obsoleted Forest XML files and their build process from the project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ZOOKEEPER-3153) Create MarkDown files and build process for them

[Tamas Penzes (JIRA)]

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

Tamas Penzes updated ZOOKEEPER-3153:

Description: 
In this sub-task we have to transform the Forrest XML documents into MarkDown 
(.md) files and provide a (maven based) solution to create HTML documentation 
from them.

PDF support is dropped since it is not really used and makes everything 
overcomplicated.

The generated HTML content should look similar to the one generated from 
Forrest XMLs, but not needed to be identical with them.

  was:
In this sub-task we have to transform the Forest XML documents into MarkDown 
(.md) files and provide a (maven based) solution to create HTML documentation 
from them.

PDF support is dropped since it is not really used and makes everything 
overcomplicated.

The generated HTML content should look similar to the one generated from Forest 
XMLs, but not needed to be identical with them.


> Create MarkDown files and build process for them
> 
>
> Key: ZOOKEEPER-3153
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3153
> Project: ZooKeeper
>  Issue Type: Sub-task
>  Components: documentation
>Affects Versions: 3.5.4, 3.4.13
>Reporter: Tamas Penzes
>Assignee: Tamas Penzes
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> In this sub-task we have to transform the Forrest XML documents into MarkDown 
> (.md) files and provide a (maven based) solution to create HTML documentation 
> from them.
> PDF support is dropped since it is not really used and makes everything 
> overcomplicated.
> The generated HTML content should look similar to the one generated from 
> Forrest XMLs, but not needed to be identical with them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ZOOKEEPER-3155) Remove Forest XMLs and their build process from the project

[Tamas Penzes (JIRA)]

Tamas Penzes created ZOOKEEPER-3155:
---

 Summary: Remove Forest XMLs and their build process from the 
project
 Key: ZOOKEEPER-3155
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3155
 Project: ZooKeeper
  Issue Type: Sub-task
Reporter: Tamas Penzes


Remove obsoleted Forest XML files and their build process from the project.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ZOOKEEPER-3154) Update release process to use the MarkDown solution

[Tamas Penzes (JIRA)]

Tamas Penzes created ZOOKEEPER-3154:
---

 Summary: Update release process to use the MarkDown solution
 Key: ZOOKEEPER-3154
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3154
 Project: ZooKeeper
  Issue Type: Sub-task
Reporter: Tamas Penzes


We have to update the release process to use the MarkDown solution.

We have to add the zookeeper-docs/src/main/resources/markdown and the 
zookeeper-docs/target/html directories and their content to the tarball.

We also have to remove the old mechanism of adding PDFs and old generated HTML 
files to the tarball in the same time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ZOOKEEPER-3153) Create MarkDown files and build process for them

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot updated ZOOKEEPER-3153:
--
Labels: pull-request-available  (was: )

> Create MarkDown files and build process for them
> 
>
> Key: ZOOKEEPER-3153
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3153
> Project: ZooKeeper
>  Issue Type: Sub-task
>  Components: documentation
>Affects Versions: 3.5.4, 3.4.13
>Reporter: Tamas Penzes
>Assignee: Tamas Penzes
>Priority: Major
>  Labels: pull-request-available
>
> In this sub-task we have to transform the Forest XML documents into MarkDown 
> (.md) files and provide a (maven based) solution to create HTML documentation 
> from them.
> PDF support is dropped since it is not really used and makes everything 
> overcomplicated.
> The generated HTML content should look similar to the one generated from 
> Forest XMLs, but not needed to be identical with them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] zookeeper pull request #643: ZOOKEEPER-3153: Create MarkDown files and build...

[tamaashu]

GitHub user tamaashu opened a pull request:

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

ZOOKEEPER-3153: Create MarkDown files and build process for them

In this sub-task we have transformed the Forest XML documents into MarkDown 
(.md) files and provided a (maven based) solution to create HTML documentation 
from them.
PDF support is dropped since it is not really used and makes everything 
overcomplicated.

The generated HTML content looks similar to the one generated from Forest 
XMLs, but not identical with them.

Change-Id: Id35984eca5d37b9e3074eab939be5c9b4cc80257

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

$ git pull https://github.com/tamaashu/zookeeper ZOOKEEPER-3153

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

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


commit 72d30441c4565434fc7870fb2e6fb2ee031184cb
Author: Tamas Penzes 
Date:   2018-09-26T06:34:51Z

ZOOKEEPER-3153: Create MarkDown files and build process for them

In this sub-task we have transformed the Forest XML documents into MarkDown 
(.md) files and provided a (maven based) solution to create HTML documentation 
from them.
PDF support is dropped since it is not really used and makes everything 
overcomplicated.

The generated HTML content looks similar to the one generated from Forest 
XMLs, but not identical with them.

Change-Id: Id35984eca5d37b9e3074eab939be5c9b4cc80257




---

[jira] [Created] (ZOOKEEPER-3153) Create MarkDown files and build process for them

[Tamas Penzes (JIRA)]

Tamas Penzes created ZOOKEEPER-3153:
---

 Summary: Create MarkDown files and build process for them
 Key: ZOOKEEPER-3153
 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3153
 Project: ZooKeeper
  Issue Type: Sub-task
  Components: documentation
Affects Versions: 3.4.13, 3.5.4
Reporter: Tamas Penzes
Assignee: Tamas Penzes


In this sub-task we have to transform the Forest XML documents into MarkDown 
(.md) files and provide a (maven based) solution to create HTML documentation 
from them.

PDF support is dropped since it is not really used and makes everything 
overcomplicated.

The generated HTML content should look similar to the one generated from Forest 
XMLs, but not needed to be identical with them.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ZOOKEEPER-925) Consider maven site generation to replace our forrest site and documentation generation

[Tamas Penzes (JIRA)]

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

Tamas Penzes updated ZOOKEEPER-925:
---
Issue Type: Task  (was: Wish)

> Consider maven site generation to replace our forrest site and documentation 
> generation
> ---
>
> Key: ZOOKEEPER-925
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-925
> Project: ZooKeeper
>  Issue Type: Task
>  Components: documentation
>Reporter: Patrick Hunt
>Assignee: Tamas Penzes
>Priority: Major
> Attachments: CMS_w_RST.patch, ZOOKEEPER-925.patch, ZOOKEEPER-925.patch
>
>
> See WHIRR-19 for some background.
> In whirr we looked at a number of site/doc generation facilities. In the end 
> Maven site generation plugin turned out to be by far the best option. You can 
> see our nascent site here (no attempt at styling,etc so far):
> http://incubator.apache.org/whirr/
> In particular take a look at the quick start:
> http://incubator.apache.org/whirr/quick-start-guide.html
> which was generated from
> http://svn.apache.org/repos/asf/incubator/whirr/trunk/src/site/confluence/quick-start-guide.confluence
> notice this was standard wiki markup (confluence wiki markup, same as 
> available from apache)
> You can read more about mvn site plugin here:
> http://maven.apache.org/guides/mini/guide-site.html
> Notice that other formats are available, not just confluence markup, also 
> note that you can use different markup formats if you like in the same site 
> (although probably not a great idea, but in some cases might be handy, for 
> example whirr uses the confluence wiki, so we can pretty much copy/paste 
> source docs from wiki to our site (svn) if we like)
> Re maven vs our current ant based build. It's probably a good idea for us to 
> move the build to maven at some point. We could initially move just the doc 
> generation, and then incrementally move functionality from build.xml to mvn 
> over a longer time period.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)