ZooKeeper-trunk-WinVS2008 - Build # 2477 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/2477/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by an SCM change
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
[EnvInject] - Loading node environment variables.
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
Building remotely on windows-2012-2 (Windows) in workspace
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
> git --version # timeout=10
> git fetch --tags --progress git://git.apache.org/zookeeper.git
> +refs/heads/*:refs/remotes/origin/*
> git rev-parse "refs/remotes/origin/master^{commit}" # timeout=10
> git rev-parse "refs/remotes/origin/origin/master^{commit}" # timeout=10
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
Checking out Revision 0c5b320060bdda854b530dc8a22993ba8cbbd655
(refs/remotes/origin/master)
Commit message: "ZOOKEEPER-2870: Improve the efficiency of
AtomicFileOutputStream"
> git config core.sparsecheckout # timeout=10
> git checkout -f 0c5b320060bdda854b530dc8a22993ba8cbbd655
> git rev-list 0c5b320060bdda854b530dc8a22993ba8cbbd655 # timeout=10
No emails were triggered.
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
[ZooKeeper-trunk-WinVS2008] $ cmd.exe /C
"F:\jenkins\tools\ant\latest\bin\ant.bat -Dtest.output=yes
-Dtest.junit.output.format=xml clean compile_jute && exit %%ERRORLEVEL%%"
java.lang.UnsupportedClassVersionError: org/apache/tools/ant/launch/Launcher :
Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
Exception in thread "main" Build step 'Invoke Ant' marked build as failure
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
###
## FAILED TESTS (if any)
##
No tests ran.
ZooKeeper-trunk-WinVS2008 - Build # 2476 - Still Failing
See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/2476/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by timer
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
[EnvInject] - Loading node environment variables.
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
Building remotely on windows-2012-2 (Windows) in workspace
f:\jenkins\jenkins-slave\workspace\ZooKeeper-trunk-WinVS2008
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
> git --version # timeout=10
> git fetch --tags --progress git://git.apache.org/zookeeper.git
> +refs/heads/*:refs/remotes/origin/*
> git rev-parse "refs/remotes/origin/master^{commit}" # timeout=10
> git rev-parse "refs/remotes/origin/origin/master^{commit}" # timeout=10
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
Checking out Revision 0c5b320060bdda854b530dc8a22993ba8cbbd655
(refs/remotes/origin/master)
Commit message: "ZOOKEEPER-2870: Improve the efficiency of
AtomicFileOutputStream"
> git config core.sparsecheckout # timeout=10
> git checkout -f 0c5b320060bdda854b530dc8a22993ba8cbbd655
> git rev-list 0cb4011dac7ec28637426cafd98b4f8f299ef61d # timeout=10
No emails were triggered.
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
[ZooKeeper-trunk-WinVS2008] $ cmd.exe /C
"F:\jenkins\tools\ant\latest\bin\ant.bat -Dtest.output=yes
-Dtest.junit.output.format=xml clean compile_jute && exit %%ERRORLEVEL%%"
java.lang.UnsupportedClassVersionError: org/apache/tools/ant/launch/Launcher :
Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)
Exception in thread "main" Build step 'Invoke Ant' marked build as failure
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
No JDK named ‘JDK 1.8 (unlimited security) 64-bit Windows only’ found
###
## FAILED TESTS (if any)
##
No tests ran.
ZooKeeper_branch34 - Build # 2043 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch34/2043/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 25.06 MB...] [junit] 2017-08-12 00:30:54,147 [myid:] - INFO [main:SyncRequestProcessor@208] - Shutting down [junit] 2017-08-12 00:30:54,147 [myid:] - INFO [ProcessThread(sid:0 cport:11221)::PrepRequestProcessor@144] - PrepRequestProcessor exited loop! [junit] 2017-08-12 00:30:54,148 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@186] - SyncRequestProcessor exited! [junit] 2017-08-12 00:30:54,148 [myid:] - INFO [main:FinalRequestProcessor@403] - shutdown of request processor complete [junit] 2017-08-12 00:30:54,148 [myid:] - INFO [main:FourLetterWordMain@65] - connecting to 127.0.0.1 11221 [junit] 2017-08-12 00:30:54,149 [myid:] - INFO [main:JMXEnv@147] - ensureOnly:[] [junit] 2017-08-12 00:30:54,150 [myid:] - INFO [main:ClientBase@489] - STARTING server [junit] 2017-08-12 00:30:54,150 [myid:] - INFO [main:ClientBase@410] - CREATING server instance 127.0.0.1:11221 [junit] 2017-08-12 00:30:54,150 [myid:] - INFO [main:ServerCnxnFactory@116] - Using org.apache.zookeeper.server.NIOServerCnxnFactory as server connection factory [junit] 2017-08-12 00:30:54,151 [myid:] - INFO [main:NIOServerCnxnFactory@89] - binding to port 0.0.0.0/0.0.0.0:11221 [junit] 2017-08-12 00:30:54,151 [myid:] - INFO [main:ClientBase@385] - STARTING server instance 127.0.0.1:11221 [junit] 2017-08-12 00:30:54,151 [myid:] - INFO [main:ZooKeeperServer@173] - Created server with tickTime 3000 minSessionTimeout 6000 maxSessionTimeout 6 datadir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/test/tmp/test4516343438372651192.junit.dir/version-2 snapdir /home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34/build/test/tmp/test4516343438372651192.junit.dir/version-2 [junit] 2017-08-12 00:30:54,154 [myid:] - ERROR [main:ZooKeeperServer@468] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [junit] 2017-08-12 00:30:54,155 [myid:] - INFO [main:FourLetterWordMain@65] - connecting to 127.0.0.1 11221 [junit] 2017-08-12 00:30:54,155 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@215] - Accepted socket connection from /127.0.0.1:41814 [junit] 2017-08-12 00:30:54,155 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxn@892] - Processing stat command from /127.0.0.1:41814 [junit] 2017-08-12 00:30:54,156 [myid:] - INFO [Thread-4:NIOServerCnxn$StatCommand@683] - Stat command output [junit] 2017-08-12 00:30:54,156 [myid:] - INFO [Thread-4:NIOServerCnxn@1040] - Closed socket connection for client /127.0.0.1:41814 (no session established for client) [junit] 2017-08-12 00:30:54,157 [myid:] - INFO [main:JMXEnv@230] - ensureParent:[InMemoryDataTree, StandaloneServer_port] [junit] 2017-08-12 00:30:54,158 [myid:] - INFO [main:JMXEnv@247] - expect:InMemoryDataTree [junit] 2017-08-12 00:30:54,158 [myid:] - INFO [main:JMXEnv@251] - found:InMemoryDataTree org.apache.ZooKeeperService:name0=StandaloneServer_port11221,name1=InMemoryDataTree [junit] 2017-08-12 00:30:54,159 [myid:] - INFO [main:JMXEnv@247] - expect:StandaloneServer_port [junit] 2017-08-12 00:30:54,159 [myid:] - INFO [main:JMXEnv@251] - found:StandaloneServer_port org.apache.ZooKeeperService:name0=StandaloneServer_port11221 [junit] 2017-08-12 00:30:54,159 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@58] - Memory used 35704 [junit] 2017-08-12 00:30:54,159 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@63] - Number of threads 20 [junit] 2017-08-12 00:30:54,159 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@78] - FINISHED TEST METHOD testQuota [junit] 2017-08-12 00:30:54,160 [myid:] - INFO [main:ClientBase@566] - tearDown starting [junit] 2017-08-12 00:30:54,230 [myid:] - INFO [main:ZooKeeper@687] - Session: 0x1022b4745ad closed [junit] 2017-08-12 00:30:54,231 [myid:] - INFO [main:ClientBase@536] - STOPPING server [junit] 2017-08-12 00:30:54,231 [myid:] - INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.0:11221:NIOServerCnxnFactory@242] - NIOServerCnxn factory exited run method [junit] 2017-08-12 00:30:54,231 [myid:] - INFO [main:ZooKeeperServer@501] - shutting down [junit] 2017-08-12 00:30:54,231 [myid:] - ERROR [main:ZooKeeperServer@468] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [junit] 2017-08-12 00:30:54,231 [myid:] - INFO [main:SessionTrackerImpl@226] - Shutting down [junit] 2017-08-12 00:30:54,232 [myid:] - INFO [main:PrepRequestProcessor@769] - Shutting down [junit] 2017-08-12 00:30:54,232 [myi
Success: ZOOKEEPER- PreCommit Build #940
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/940/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 72.74 MB...] [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +0 tests included. The patch appears to be a documentation patch that doesn't require tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 3.0.1) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [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/940//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/940//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/940//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment added. [exec] 7c98cf843e621c3ec99342977ea5024320ee77ef logged out [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: 20 minutes 5 seconds Archiving artifacts Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Recording test results Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 [description-setter] Description set: ZOOKEEPER-2874 Putting comment on the pull request Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Email was triggered for: Success Sending email for trigger: Success Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-2874) Windows Debug builds don't link with `/MTd`
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124218#comment-16124218
]
Hadoop QA commented on ZOOKEEPER-2874:
--
+1 overall. GitHub Pull Request Build
+1 @author. The patch does not contain any @author tags.
+0 tests included. The patch appears to be a documentation patch that
doesn't require tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 3.0.1)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/940//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/940//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/940//console
This message is automatically generated.
> Windows Debug builds don't link with `/MTd`
> ---
>
> Key: ZOOKEEPER-2874
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2874
> Project: ZooKeeper
> Issue Type: Bug
> Environment: Windows 10 using CMake
>Reporter: Andrew Schwartzmeyer
>Assignee: Andrew Schwartzmeyer
>
> While not apparent when building ZooKeeper stand-alone, further testing when
> linking with Mesos revealed it was ZooKeeper that was causing the warning:
> {noformat}
> LIBCMTD.lib(initializers.obj) : warning LNK4098: defaultlib 'libcmt.lib'
> conflicts with use of other libs; use /NODEFAULTLIB:library
> [C:\Users\andschwa\src\mesos\build\src\slave\mesos-agent.vcxproj]
> {noformat}
> As Mesos is linking with {{/MTd}} in Debug configuration (which is the most
> common practice).
> Once I found the source of the warning, the fix is trivial and I am posting a
> patch.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ZOOKEEPER-2874) Windows Debug builds don't link with `/MTd`
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124186#comment-16124186
]
ASF GitHub Bot commented on ZOOKEEPER-2874:
---
Github user andschwa commented on the issue:
https://github.com/apache/zookeeper/pull/335
Built on Windows:
```powershell
> cmake --build . --config Debug
> cmake --build . --config Release
> rg libcmt
cli.dir\Debug\cli.tlog\link.read.1.tlog
17:C:\PROGRAM FILES (X86)\MICROSOFT VISUAL
STUDIO\2017\COMMUNITY\VC\TOOLS\MSVC\14.10.25017\LIB\X86\LIBCMTD.LIB
cli.dir\Release\cli.tlog\link.read.1.tlog
17:C:\PROGRAM FILES (X86)\MICROSOFT VISUAL
STUDIO\2017\COMMUNITY\VC\TOOLS\MSVC\14.10.25017\LIB\X86\LIBCMT.LIB
```
As you can see from the logs, the correct library is now being linked. I've
also integration tested this with Mesos, and it has eliminated the warning.
> Windows Debug builds don't link with `/MTd`
> ---
>
> Key: ZOOKEEPER-2874
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2874
> Project: ZooKeeper
> Issue Type: Bug
> Environment: Windows 10 using CMake
>Reporter: Andrew Schwartzmeyer
>Assignee: Andrew Schwartzmeyer
>
> While not apparent when building ZooKeeper stand-alone, further testing when
> linking with Mesos revealed it was ZooKeeper that was causing the warning:
> {noformat}
> LIBCMTD.lib(initializers.obj) : warning LNK4098: defaultlib 'libcmt.lib'
> conflicts with use of other libs; use /NODEFAULTLIB:library
> [C:\Users\andschwa\src\mesos\build\src\slave\mesos-agent.vcxproj]
> {noformat}
> As Mesos is linking with {{/MTd}} in Debug configuration (which is the most
> common practice).
> Once I found the source of the warning, the fix is trivial and I am posting a
> patch.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] zookeeper issue #335: ZOOKEEPER-2874: Windows Debug builds don't link with `...
Github user andschwa commented on the issue: https://github.com/apache/zookeeper/pull/335 Built on Windows: ```powershell > cmake --build . --config Debug > cmake --build . --config Release > rg libcmt cli.dir\Debug\cli.tlog\link.read.1.tlog 17:C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2017\COMMUNITY\VC\TOOLS\MSVC\14.10.25017\LIB\X86\LIBCMTD.LIB cli.dir\Release\cli.tlog\link.read.1.tlog 17:C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2017\COMMUNITY\VC\TOOLS\MSVC\14.10.25017\LIB\X86\LIBCMT.LIB ``` As you can see from the logs, the correct library is now being linked. I've also integration tested this with Mesos, and it has eliminated the warning. --- 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. ---
[GitHub] zookeeper issue #335: ZOOKEEPER-2874: Windows Debug builds don't link with `...
Github user andschwa commented on the issue: https://github.com/apache/zookeeper/pull/335 @hanm This should be backported to 3.5 and 3.4 as well; it should be a trivial cherry-pick, but let me know if you'd like two more PRs. --- 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] [Commented] (ZOOKEEPER-2874) Windows Debug builds don't link with `/MTd`
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124181#comment-16124181
]
ASF GitHub Bot commented on ZOOKEEPER-2874:
---
Github user andschwa commented on the issue:
https://github.com/apache/zookeeper/pull/335
@hanm This should be backported to 3.5 and 3.4 as well; it should be a
trivial cherry-pick, but let me know if you'd like two more PRs.
> Windows Debug builds don't link with `/MTd`
> ---
>
> Key: ZOOKEEPER-2874
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2874
> Project: ZooKeeper
> Issue Type: Bug
> Environment: Windows 10 using CMake
>Reporter: Andrew Schwartzmeyer
>Assignee: Andrew Schwartzmeyer
>
> While not apparent when building ZooKeeper stand-alone, further testing when
> linking with Mesos revealed it was ZooKeeper that was causing the warning:
> {noformat}
> LIBCMTD.lib(initializers.obj) : warning LNK4098: defaultlib 'libcmt.lib'
> conflicts with use of other libs; use /NODEFAULTLIB:library
> [C:\Users\andschwa\src\mesos\build\src\slave\mesos-agent.vcxproj]
> {noformat}
> As Mesos is linking with {{/MTd}} in Debug configuration (which is the most
> common practice).
> Once I found the source of the warning, the fix is trivial and I am posting a
> patch.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ZOOKEEPER-2874) Windows Debug builds don't link with `/MTd`
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16124180#comment-16124180
]
ASF GitHub Bot commented on ZOOKEEPER-2874:
---
GitHub user andschwa opened a pull request:
https://github.com/apache/zookeeper/pull/335
ZOOKEEPER-2874: Windows Debug builds don't link with `/MTd`
When building in Debug configuration, this logic ensures that `/MTd` is
used instead of just `/MT`, which on Windows means to link to the
multi-threaded (debug) version of the standard library.
When the user does not add `/MT` as a compile option manually, CMake
would otherwise link to the correct one. Because we are overriding it
for threaded compilations, we also must ensure that Debug configurations
are specially handled.
Furthermore, this must be done using a generator expression over
configuration time logic because the Visual Studio CMake generators are
"multi-configuration generators", that is, the configuration is chosen
at build time instead of compile time. The generator expression handles
this scenario, but checking `CMAKE_BUILD_CONFIG` would not.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/andschwa/zookeeper ZOOKEEPER-2874
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zookeeper/pull/335.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 #335
commit 554e20e1f63c02e058f05010868c3f6b5a4b1f2c
Author: Andrew Schwartzmeyer
Date: 2017-08-11T22:03:28Z
ZOOKEEPER-2874: Windows Debug builds don't link with `/MTd`
When building in Debug configuration, this logic ensures that `/MTd` is
used instead of just `/MT`, which on Windows means to link to the
multi-threaded (debug) version of the standard library.
When the user does not add `/MT` as a compile option manually, CMake
would otherwise link to the correct one. Because we are overriding it
for threaded compilations, we also must ensure that Debug configurations
are specially handled.
Furthermore, this must be done using a generator expression over
configuration time logic because the Visual Studio CMake generators are
"multi-configuration generators", that is, the configuration is chosen
at build time instead of compile time. The generator expression handles
this scenario, but checking `CMAKE_BUILD_CONFIG` would not.
> Windows Debug builds don't link with `/MTd`
> ---
>
> Key: ZOOKEEPER-2874
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2874
> Project: ZooKeeper
> Issue Type: Bug
> Environment: Windows 10 using CMake
>Reporter: Andrew Schwartzmeyer
>Assignee: Andrew Schwartzmeyer
>
> While not apparent when building ZooKeeper stand-alone, further testing when
> linking with Mesos revealed it was ZooKeeper that was causing the warning:
> {noformat}
> LIBCMTD.lib(initializers.obj) : warning LNK4098: defaultlib 'libcmt.lib'
> conflicts with use of other libs; use /NODEFAULTLIB:library
> [C:\Users\andschwa\src\mesos\build\src\slave\mesos-agent.vcxproj]
> {noformat}
> As Mesos is linking with {{/MTd}} in Debug configuration (which is the most
> common practice).
> Once I found the source of the warning, the fix is trivial and I am posting a
> patch.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (ZOOKEEPER-2874) Windows Debug builds don't link with `/MTd`
[
https://issues.apache.org/jira/browse/ZOOKEEPER-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Schwartzmeyer updated ZOOKEEPER-2874:
Summary: Windows Debug builds don't link with `/MTd` (was: Windows Debug
builds don't link to /MTd)
> Windows Debug builds don't link with `/MTd`
> ---
>
> Key: ZOOKEEPER-2874
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2874
> Project: ZooKeeper
> Issue Type: Bug
> Environment: Windows 10 using CMake
>Reporter: Andrew Schwartzmeyer
>Assignee: Andrew Schwartzmeyer
>
> While not apparent when building ZooKeeper stand-alone, further testing when
> linking with Mesos revealed it was ZooKeeper that was causing the warning:
> {noformat}
> LIBCMTD.lib(initializers.obj) : warning LNK4098: defaultlib 'libcmt.lib'
> conflicts with use of other libs; use /NODEFAULTLIB:library
> [C:\Users\andschwa\src\mesos\build\src\slave\mesos-agent.vcxproj]
> {noformat}
> As Mesos is linking with {{/MTd}} in Debug configuration (which is the most
> common practice).
> Once I found the source of the warning, the fix is trivial and I am posting a
> patch.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[GitHub] zookeeper pull request #335: ZOOKEEPER-2874: Windows Debug builds don't link...
GitHub user andschwa opened a pull request: https://github.com/apache/zookeeper/pull/335 ZOOKEEPER-2874: Windows Debug builds don't link with `/MTd` When building in Debug configuration, this logic ensures that `/MTd` is used instead of just `/MT`, which on Windows means to link to the multi-threaded (debug) version of the standard library. When the user does not add `/MT` as a compile option manually, CMake would otherwise link to the correct one. Because we are overriding it for threaded compilations, we also must ensure that Debug configurations are specially handled. Furthermore, this must be done using a generator expression over configuration time logic because the Visual Studio CMake generators are "multi-configuration generators", that is, the configuration is chosen at build time instead of compile time. The generator expression handles this scenario, but checking `CMAKE_BUILD_CONFIG` would not. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andschwa/zookeeper ZOOKEEPER-2874 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zookeeper/pull/335.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 #335 commit 554e20e1f63c02e058f05010868c3f6b5a4b1f2c Author: Andrew Schwartzmeyer Date: 2017-08-11T22:03:28Z ZOOKEEPER-2874: Windows Debug builds don't link with `/MTd` When building in Debug configuration, this logic ensures that `/MTd` is used instead of just `/MT`, which on Windows means to link to the multi-threaded (debug) version of the standard library. When the user does not add `/MT` as a compile option manually, CMake would otherwise link to the correct one. Because we are overriding it for threaded compilations, we also must ensure that Debug configurations are specially handled. Furthermore, this must be done using a generator expression over configuration time logic because the Visual Studio CMake generators are "multi-configuration generators", that is, the configuration is chosen at build time instead of compile time. The generator expression handles this scenario, but checking `CMAKE_BUILD_CONFIG` would not. --- 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] [Created] (ZOOKEEPER-2874) Windows Debug builds don't link to /MTd
Andrew Schwartzmeyer created ZOOKEEPER-2874:
---
Summary: Windows Debug builds don't link to /MTd
Key: ZOOKEEPER-2874
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2874
Project: ZooKeeper
Issue Type: Bug
Environment: Windows 10 using CMake
Reporter: Andrew Schwartzmeyer
Assignee: Andrew Schwartzmeyer
While not apparent when building ZooKeeper stand-alone, further testing when
linking with Mesos revealed it was ZooKeeper that was causing the warning:
{noformat}
LIBCMTD.lib(initializers.obj) : warning LNK4098: defaultlib 'libcmt.lib'
conflicts with use of other libs; use /NODEFAULTLIB:library
[C:\Users\andschwa\src\mesos\build\src\slave\mesos-agent.vcxproj]
{noformat}
As Mesos is linking with {{/MTd}} in Debug configuration (which is the most
common practice).
Once I found the source of the warning, the fix is trivial and I am posting a
patch.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Success: ZOOKEEPER- PreCommit Build #939
Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/939/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 69.67 MB...] [exec] [exec] +1 @author. The patch does not contain any @author tags. [exec] [exec] +1 tests included. The patch appears to include 6 new or modified tests. [exec] [exec] +1 javadoc. The javadoc tool did not generate any warning messages. [exec] [exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings. [exec] [exec] +1 findbugs. The patch does not introduce any new Findbugs (version 3.0.1) warnings. [exec] [exec] +1 release audit. The applied patch does not increase the total number of release audit warnings. [exec] [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/939//testReport/ [exec] Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/939//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html [exec] Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/939//console [exec] [exec] This message is automatically generated. [exec] [exec] [exec] == [exec] == [exec] Adding comment to Jira. [exec] == [exec] == [exec] [exec] [exec] Comment added. [exec] 7be7ed4dbdba18d7cdf81025f8f55405651f8178 logged out [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: 20 minutes 26 seconds Archiving artifacts Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Recording test results Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 [description-setter] Description set: ZOOKEEPER-2872 Putting comment on the pull request Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Email was triggered for: Success Sending email for trigger: Success Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 Setting JDK_1_7_LATEST__HOME=/home/jenkins/tools/java/latest1.7 ### ## FAILED TESTS (if any) ## All tests passed
[jira] [Commented] (ZOOKEEPER-2872) Interrupted snapshot sync causes data loss
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123755#comment-16123755 ] Hadoop QA commented on ZOOKEEPER-2872: -- +1 overall. GitHub Pull Request Build +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 6 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs (version 3.0.1) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/939//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/939//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/939//console This message is automatically generated. > Interrupted snapshot sync causes data loss > -- > > Key: ZOOKEEPER-2872 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2872 > Project: ZooKeeper > Issue Type: Bug > Components: server >Affects Versions: 3.4.10, 3.5.3, 3.6.0 >Reporter: Brian Nixon > > There is a way for observers to permanently lose data from their local data > tree while remaining members of good standing with the ensemble and > continuing to serve client traffic when the following chain of events occurs. > 1. The observer dies in epoch N from machine failure. > 2. The observer comes back up in epoch N+1 and requests a snapshot sync to > catch up. > 3. The machine powers off before the snapshot is synced to disc and after > some txn's have been logged (depending on the OS, this can happen!). > 4. The observer comes back a second time and replays its most recent snapshot > (epoch <= N) as well as the txn logs (epoch N+1). > 5. A diff sync is requested from the leader and the observer broadcasts > availability. > In this scenario, any commits from epoch N that the observer did not receive > before it died the first time will never be exposed to the observer and no > part of the ensemble will complain. > This situation is not unique to observers and can happen to any learner. As a > simple fix, fsync-ing the snapshots received from the leader will avoid the > case of missing snapshots causing data loss. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
ZooKeeper_branch34_openjdk7 - Build # 1606 - Failure
See https://builds.apache.org/job/ZooKeeper_branch34_openjdk7/1606/
###
## LAST 60 LINES OF THE CONSOLE
###
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on qnode1 (ubuntu) in workspace
/home/jenkins/jenkins-slave/workspace/ZooKeeper_branch34_openjdk7
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url git://git.apache.org/zookeeper.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
Fetching upstream changes from git://git.apache.org/zookeeper.git
> git --version # timeout=10
> git fetch --tags --progress git://git.apache.org/zookeeper.git
> +refs/heads/*:refs/remotes/origin/*
> git rev-parse refs/remotes/origin/branch-3.4^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/branch-3.4^{commit} # timeout=10
Checking out Revision 9959b0e4387c02e82fadb0aee8d59f6212a2757e
(refs/remotes/origin/branch-3.4)
Commit message: "ZOOKEEPER-2870: Improve the efficiency of
AtomicFileOutputStream"
> git config core.sparsecheckout # timeout=10
> git checkout -f 9959b0e4387c02e82fadb0aee8d59f6212a2757e
> git rev-list 9959b0e4387c02e82fadb0aee8d59f6212a2757e # timeout=10
No emails were triggered.
[ZooKeeper_branch34_openjdk7] $
/home/jenkins/tools/ant/apache-ant-1.9.9/bin/ant -Dtest.output=yes
-Dtest.junit.threads=8 -Dtest.junit.output.format=xml -Djavac.target=1.7 clean
test-core-java
Error: JAVA_HOME is not defined correctly.
We cannot execute /usr/lib/jvm/java-7-openjdk-amd64//bin/java
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_openjdk7 - Build # 630 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch35_openjdk7/630/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 72.09 MB...] [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-08-11 10:13:19,102 [myid:127.0.0.1:30076] - INFO [main-SendThread(127.0.0.1:30076):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:30076. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-08-11 10:13:19,102 [myid:127.0.0.1:30076] - WARN [main-SendThread(127.0.0.1:30076):ClientCnxn$SendThread@1235] - Session 0x100f2942c25 for server 127.0.0.1/127.0.0.1:30076, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-08-11 10:13:19,303 [myid:127.0.0.1:30073] - INFO [main-SendThread(127.0.0.1:30073):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:30073. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-08-11 10:13:19,304 [myid:127.0.0.1:30073] - WARN [main-SendThread(127.0.0.1:30073):ClientCnxn$SendThread@1235] - Session 0xf294264d0001 for server 127.0.0.1/127.0.0.1:30073, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-08-11 10:13:19,643 [myid:127.0.0.1:30073] - INFO [main-SendThread(127.0.0.1:30073):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:30073. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-08-11 10:13:19,643 [myid:127.0.0.1:30073] - WARN [main-SendThread(127.0.0.1:30073):ClientCnxn$SendThread@1235] - Session 0xf294264d for server 127.0.0.1/127.0.0.1:30073, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-08-11 10:13:19,656 [myid:127.0.0.1:30076] - INFO [main-SendThread(127.0.0.1:30076):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:30076. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-08-11 10:13:19,657 [myid:127.0.0.1:30076] - WARN [main-SendThread(127.0.0.1:30076):ClientCnxn$SendThread@1235] - Session 0x100f2942c250001 for server 127.0.0.1/127.0.0.1:30076, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-08-11 10:13:20,413 [myid:127.0.0.1:30076] - INFO [main-SendThread(127.0.0.1:30076):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:30076. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-08-11 10:13:20,413 [myid:127.0.0.1:30076] - WARN [main-SendThread(127.0.0.1:30076):ClientCnxn$SendThread@1235] - Session 0x100f2942c25 for server 127.0.0.1/127.0.0.1:30076, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739) [junit] at org.apache.zooke
[jira] [Commented] (ZOOKEEPER-2836) QuorumCnxManager.Listener Thread Better handling of SocketTimeoutException
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123067#comment-16123067 ] ASF GitHub Bot commented on ZOOKEEPER-2836: --- Github user bitgaoshu closed the pull request at: https://github.com/apache/zookeeper/pull/334 > QuorumCnxManager.Listener Thread Better handling of SocketTimeoutException > -- > > Key: ZOOKEEPER-2836 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2836 > Project: ZooKeeper > Issue Type: Bug > Components: leaderElection, quorum >Affects Versions: 3.4.6 > Environment: Machine: Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.78-1 > x86_64 GNU/Linux > Java Version: jdk64/jdk1.8.0_40 > zookeeper version: 3.4.6.2.3.2.0-2950 >Reporter: Amarjeet Singh >Priority: Critical > > QuorumCnxManager Listener thread blocks SocketServer on accept but we are > getting SocketTimeoutException on our boxes after 49days 17 hours . As per > current code there is a 3 times retry and after that it says "_As I'm leaving > the listener thread, I won't be able to participate in leader election any > longer: $/$:3888__" , Once server nodes reache this state and > we restart or add a new node ,it fails to join cluster and logs 'WARN > QuorumPeer/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@383 - Cannot open > channel to 3 at election address $/$:3888' . > As there is no timeout specified for ServerSocket it should never > timeout but there are some already discussed issues where people have seen > this issue and added checks for SocketTimeoutException explicitly like > https://issues.apache.org/jira/browse/KARAF-3325 . > I think we need to handle SocketTimeoutException on similar lines for > zookeeper as well -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] zookeeper pull request #334: ZOOKEEPER-2836 SocketTimeoutException
Github user bitgaoshu closed the pull request at: https://github.com/apache/zookeeper/pull/334 --- 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] [Commented] (ZOOKEEPER-2836) QuorumCnxManager.Listener Thread Better handling of SocketTimeoutException
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16123064#comment-16123064 ] ASF GitHub Bot commented on ZOOKEEPER-2836: --- GitHub user bitgaoshu opened a pull request: https://github.com/apache/zookeeper/pull/334 ZOOKEEPER-2836 SocketTimeoutException You can merge this pull request into a Git repository by running: $ git pull https://github.com/bitgaoshu/zookeeper fix/ZOOKEEPER-2836 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zookeeper/pull/334.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 #334 commit 313406fdb0bd247c897409d8dbf800f6a6d62ce4 Author: fengwei Date: 2017-08-11T09:10:06Z ZOOKEEPER-2836 SocketTimeoutException > QuorumCnxManager.Listener Thread Better handling of SocketTimeoutException > -- > > Key: ZOOKEEPER-2836 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2836 > Project: ZooKeeper > Issue Type: Bug > Components: leaderElection, quorum >Affects Versions: 3.4.6 > Environment: Machine: Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.78-1 > x86_64 GNU/Linux > Java Version: jdk64/jdk1.8.0_40 > zookeeper version: 3.4.6.2.3.2.0-2950 >Reporter: Amarjeet Singh >Priority: Critical > > QuorumCnxManager Listener thread blocks SocketServer on accept but we are > getting SocketTimeoutException on our boxes after 49days 17 hours . As per > current code there is a 3 times retry and after that it says "_As I'm leaving > the listener thread, I won't be able to participate in leader election any > longer: $/$:3888__" , Once server nodes reache this state and > we restart or add a new node ,it fails to join cluster and logs 'WARN > QuorumPeer/0:0:0:0:0:0:0:0:2181:QuorumCnxManager@383 - Cannot open > channel to 3 at election address $/$:3888' . > As there is no timeout specified for ServerSocket it should never > timeout but there are some already discussed issues where people have seen > this issue and added checks for SocketTimeoutException explicitly like > https://issues.apache.org/jira/browse/KARAF-3325 . > I think we need to handle SocketTimeoutException on similar lines for > zookeeper as well -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] zookeeper pull request #334: ZOOKEEPER-2836 SocketTimeoutException
GitHub user bitgaoshu opened a pull request: https://github.com/apache/zookeeper/pull/334 ZOOKEEPER-2836 SocketTimeoutException You can merge this pull request into a Git repository by running: $ git pull https://github.com/bitgaoshu/zookeeper fix/ZOOKEEPER-2836 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zookeeper/pull/334.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 #334 commit 313406fdb0bd247c897409d8dbf800f6a6d62ce4 Author: fengwei Date: 2017-08-11T09:10:06Z ZOOKEEPER-2836 SocketTimeoutException --- 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. ---
ZooKeeper_branch35_jdk7 - Build # 1072 - Still Failing
See https://builds.apache.org/job/ZooKeeper_branch35_jdk7/1072/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 69.99 MB...] [junit] 2017-08-11 08:48:08,519 [myid:] - INFO [main:ZooKeeperServer@541] - shutting down [junit] 2017-08-11 08:48:08,519 [myid:] - ERROR [main:ZooKeeperServer@505] - ZKShutdownHandler is not registered, so ZooKeeper server won't take any action on ERROR or SHUTDOWN server state changes [junit] 2017-08-11 08:48:08,519 [myid:] - INFO [main:SessionTrackerImpl@232] - Shutting down [junit] 2017-08-11 08:48:08,519 [myid:] - INFO [main:PrepRequestProcessor@1005] - Shutting down [junit] 2017-08-11 08:48:08,520 [myid:] - INFO [main:SyncRequestProcessor@191] - Shutting down [junit] 2017-08-11 08:48:08,520 [myid:] - INFO [ProcessThread(sid:0 cport:30319)::PrepRequestProcessor@155] - PrepRequestProcessor exited loop! [junit] 2017-08-11 08:48:08,520 [myid:] - INFO [SyncThread:0:SyncRequestProcessor@169] - SyncRequestProcessor exited! [junit] 2017-08-11 08:48:08,520 [myid:] - INFO [main:FinalRequestProcessor@481] - shutdown of request processor complete [junit] 2017-08-11 08:48:08,521 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port30319,name1=InMemoryDataTree] [junit] 2017-08-11 08:48:08,521 [myid:] - INFO [main:MBeanRegistry@128] - Unregister MBean [org.apache.ZooKeeperService:name0=StandaloneServer_port30319] [junit] 2017-08-11 08:48:08,538 [myid:127.0.0.1:30202] - INFO [main-SendThread(127.0.0.1:30202):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:30202. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-08-11 08:48:08,554 [myid:] - INFO [main:FourLetterWordMain@87] - connecting to 127.0.0.1 30319 [junit] 2017-08-11 08:48:08,555 [myid:127.0.0.1:30202] - WARN [main-SendThread(127.0.0.1:30202):ClientCnxn$SendThread@1235] - Session 0x305fba9e2d5 for server 127.0.0.1/127.0.0.1:30202, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-08-11 08:48:08,555 [myid:] - INFO [main:JMXEnv@146] - ensureOnly:[] [junit] 2017-08-11 08:48:08,572 [myid:] - INFO [main:ClientBase@611] - fdcount after test is: 7173 at start it was 7173 [junit] 2017-08-11 08:48:08,572 [myid:] - INFO [main:ZKTestCase$1@68] - SUCCEEDED testWatcherAutoResetWithLocal [junit] 2017-08-11 08:48:08,572 [myid:] - INFO [main:ZKTestCase$1@63] - FINISHED testWatcherAutoResetWithLocal [junit] Tests run: 103, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 407.957 sec, Thread: 8, Class: org.apache.zookeeper.test.NioNettySuiteTest [junit] 2017-08-11 08:48:08,678 [myid:127.0.0.1:30199] - INFO [main-SendThread(127.0.0.1:30199):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:30199. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-08-11 08:48:08,679 [myid:127.0.0.1:30199] - WARN [main-SendThread(127.0.0.1:30199):ClientCnxn$SendThread@1235] - Session 0x205fba9e2d2 for server 127.0.0.1/127.0.0.1:30199, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectException: Connection refused [junit] at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) [junit] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744) [junit] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:357) [junit] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1214) [junit] 2017-08-11 08:48:08,861 [myid:] - INFO [SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop! [junit] 2017-08-11 08:48:08,861 [myid:] - INFO [SessionTracker:SessionTrackerImpl@158] - SessionTrackerImpl exited loop! [junit] 2017-08-11 08:48:08,957 [myid:127.0.0.1:30130] - INFO [VCC0-SendThread(127.0.0.1:30130):ClientCnxn$SendThread@1113] - Opening socket connection to server 127.0.0.1/127.0.0.1:30130. Will not attempt to authenticate using SASL (unknown error) [junit] 2017-08-11 08:48:08,958 [myid:127.0.0.1:30130] - WARN [VCC0-SendThread(127.0.0.1:30130):ClientCnxn$SendThread@1235] - Session 0x0 for server 127.0.0.1/127.0.0.1:30130, unexpected error, closing socket connection and attempting reconnect [junit] java.net.ConnectE
