ZooKeeper-trunk-WinVS2008 - Build # 793 - Still Failing

See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/793/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 466 lines...] .\src\cli.c(402): error C2065:

ZooKeeper-trunk-solaris - Build # 517 - Still Failing

See https://builds.apache.org/job/ZooKeeper-trunk-solaris/517/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 204064 lines...] [junit] 2013-04-05

ZooKeeper-trunk-WinVS2008 - Build # 794 - Still Failing

See https://builds.apache.org/job/ZooKeeper-trunk-WinVS2008/794/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 468 lines...] .\src\cli.c(402): error C2065:

wrong check causes continuous Exceptions in ZookeeperSaslClient (apparently)

Hello, I was running a few tests with Zookeeper (3.4.5) lately and found this message continuously in my log files: DEBUG [main-SendThread(localhost:55694):ZooKeeperSaslClient@519][] - Could not retrieve login configuration: java.lang.SecurityException: Unable to locate a login configuration. I

[jira] [Assigned] (ZOOKEEPER-1683) ZooKeeper client NPE when updating server list on disconnected client

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Shraer reassigned ZOOKEEPER-1683: --- Assignee: Alexander Shraer ZooKeeper client NPE when updating

[jira] [Commented] (ZOOKEEPER-1683) ZooKeeper client NPE when updating server list on disconnected client

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624039#comment-13624039 ] Shevek commented on ZOOKEEPER-1683: --- This may be caused by ClientCnxnSocketNIO.java:

[jira] [Commented] (ZOOKEEPER-1683) ZooKeeper client NPE when updating server list on disconnected client

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624042#comment-13624042 ] Shevek commented on ZOOKEEPER-1683: --- Note that since connect() is called by

[jira] [Created] (ZOOKEEPER-1684) Failure to update socket addresses on immedate connection

Shevek created ZOOKEEPER-1684: - Summary: Failure to update socket addresses on immedate connection Key: ZOOKEEPER-1684 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1684 Project: ZooKeeper

[jira] [Commented] (ZOOKEEPER-1683) ZooKeeper client NPE when updating server list on disconnected client

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624048#comment-13624048 ] Alexander Shraer commented on ZOOKEEPER-1683: - Thanks Shevek. I'd like to

[jira] [Created] (ZOOKEEPER-1685) Zookeeper client hard codes the server principal to zookeeper

Arpit Gupta created ZOOKEEPER-1685: -- Summary: Zookeeper client hard codes the server principal to zookeeper Key: ZOOKEEPER-1685 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1685 Project:

[jira] [Commented] (ZOOKEEPER-1685) Zookeeper client hard codes the server principal to zookeeper

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624067#comment-13624067 ] Arpit Gupta commented on ZOOKEEPER-1685: I think we should make it

[jira] [Updated] (ZOOKEEPER-1670) zookeeper should set a default value for SERVER_JVMFLAGS so that memory usage is controlled

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Gupta updated ZOOKEEPER-1670: --- Attachment: ZOOKEEPER-1670.patch Updated the patch to be similar to what Hadoop and

[jira] [Updated] (ZOOKEEPER-1670) zookeeper should set a default value for SERVER_JVMFLAGS and CLIENT_JVMFLAGS so that memory usage is controlled

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Gupta updated ZOOKEEPER-1670: --- Summary: zookeeper should set a default value for SERVER_JVMFLAGS and CLIENT_JVMFLAGS so

[jira] [Commented] (ZOOKEEPER-1683) ZooKeeper client NPE when updating server list on disconnected client

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624086#comment-13624086 ] Shevek commented on ZOOKEEPER-1683: --- The trouble is that there's hidden state in

Failed: ZOOKEEPER-1670 PreCommit Build #1443

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-1670 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1443/ ### ## LAST 60 LINES OF THE CONSOLE ###

[jira] [Commented] (ZOOKEEPER-1670) zookeeper should set a default value for SERVER_JVMFLAGS and CLIENT_JVMFLAGS so that memory usage is controlled

[ https://issues.apache.org/jira/browse/ZOOKEEPER-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624107#comment-13624107 ] Hadoop QA commented on ZOOKEEPER-1670: -- -1 overall. Here are the results of

[jira] [Created] (ZOOKEEPER-1686) Publish ZK 3.4.5 test jar

Todd Lipcon created ZOOKEEPER-1686: -- Summary: Publish ZK 3.4.5 test jar Key: ZOOKEEPER-1686 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1686 Project: ZooKeeper Issue Type: Bug

Failed: ZOOKEEPER-548 PreCommit Build #1444

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-548 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1444/ ### ## LAST 60 LINES OF THE CONSOLE ###

[jira] [Updated] (ZOOKEEPER-297) centralize version numbering in the source/build

[ https://issues.apache.org/jira/browse/ZOOKEEPER-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Diego de Oliveira updated ZOOKEEPER-297: Attachment: build_version.patch Build version patch

Failed: ZOOKEEPER-297 PreCommit Build #1445

Jira: https://issues.apache.org/jira/browse/ZOOKEEPER-297 Build: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/1445/ ### ## LAST 60 LINES OF THE CONSOLE ###

[jira] [Commented] (ZOOKEEPER-297) centralize version numbering in the source/build

[ https://issues.apache.org/jira/browse/ZOOKEEPER-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624307#comment-13624307 ] Hadoop QA commented on ZOOKEEPER-297: - -1 overall. Here are the results of testing

[jira] [Commented] (BOOKKEEPER-572) Make the journal a write ahead log

[ https://issues.apache.org/jira/browse/BOOKKEEPER-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623496#comment-13623496 ] Ivan Kelly commented on BOOKKEEPER-572: --- Quick bench with new patch. TPT 1000

[jira] [Commented] (BOOKKEEPER-572) Make the journal a write ahead log

[ https://issues.apache.org/jira/browse/BOOKKEEPER-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623499#comment-13623499 ] Hadoop QA commented on BOOKKEEPER-572: -- Testing JIRA BOOKKEEPER-572 Patch

[jira] [Commented] (BOOKKEEPER-598) Fails to compile - RESUBSCRIBE_EXCEPTION conflict

[ https://issues.apache.org/jira/browse/BOOKKEEPER-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623555#comment-13623555 ] Jiannan Wang commented on BOOKKEEPER-598: - I have a try on my new laptop and

[jira] [Commented] (BOOKKEEPER-572) Make the journal a write ahead log

[ https://issues.apache.org/jira/browse/BOOKKEEPER-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623613#comment-13623613 ] Flavio Junqueira commented on BOOKKEEPER-572: - [~ikelly] do you have by

[jira] [Updated] (BOOKKEEPER-572) Make the journal a write ahead log

[ https://issues.apache.org/jira/browse/BOOKKEEPER-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-572: -- Attachment: 0001-BOOKKEEPER-572-Write-to-the-journal-before-writing-t.patch Attached

[jira] [Commented] (BOOKKEEPER-572) Make the journal a write ahead log

[ https://issues.apache.org/jira/browse/BOOKKEEPER-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623681#comment-13623681 ] Flavio Junqueira commented on BOOKKEEPER-572: - bq. 4.2.1 results are in

[jira] [Commented] (BOOKKEEPER-572) Make the journal a write ahead log

[ https://issues.apache.org/jira/browse/BOOKKEEPER-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623688#comment-13623688 ] Hadoop QA commented on BOOKKEEPER-572: -- Testing JIRA BOOKKEEPER-572 Patch

[jira] [Updated] (BOOKKEEPER-572) Make the journal a write ahead log

[ https://issues.apache.org/jira/browse/BOOKKEEPER-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-572: -- Attachment: 0001-BOOKKEEPER-572-Write-to-the-journal-before-writing-t.patch Fixed

[jira] [Updated] (BOOKKEEPER-564) Better checkpoint mechanism

[ https://issues.apache.org/jira/browse/BOOKKEEPER-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated BOOKKEEPER-564: -- Attachment: 0002-BOOKKEEPER-564-Better-checkpoint-mechanism.patch I've rejigged this to

[jira] [Commented] (BOOKKEEPER-564) Better checkpoint mechanism

[ https://issues.apache.org/jira/browse/BOOKKEEPER-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623832#comment-13623832 ] Sijie Guo commented on BOOKKEEPER-564: -- the jira is to separate checkpoint with

[jira] [Commented] (BOOKKEEPER-599) NPE in PerChannelBookieClient

[ https://issues.apache.org/jira/browse/BOOKKEEPER-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623851#comment-13623851 ] Sijie Guo commented on BOOKKEEPER-599: -- looks good. but since handleResponse is

[jira] [Commented] (BOOKKEEPER-598) Fails to compile - RESUBSCRIBE_EXCEPTION conflict

[ https://issues.apache.org/jira/browse/BOOKKEEPER-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623865#comment-13623865 ] Sijie Guo commented on BOOKKEEPER-598: -- yes. I think this issue is introduced

[jira] [Updated] (BOOKKEEPER-598) Fails to compile - RESUBSCRIBE_EXCEPTION conflict

[ https://issues.apache.org/jira/browse/BOOKKEEPER-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo updated BOOKKEEPER-598: - Fix Version/s: 4.3.0 Fails to compile - RESUBSCRIBE_EXCEPTION conflict

[jira] [Updated] (BOOKKEEPER-598) Fails to compile - RESUBSCRIBE_EXCEPTION conflict

[ https://issues.apache.org/jira/browse/BOOKKEEPER-598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sijie Guo updated BOOKKEEPER-598: - Affects Version/s: (was: 4.3.0) Fails to compile - RESUBSCRIBE_EXCEPTION conflict

[jira] [Commented] (BOOKKEEPER-598) Fails to compile - RESUBSCRIBE_EXCEPTION conflict

[ https://issues.apache.org/jira/browse/BOOKKEEPER-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623866#comment-13623866 ] Sijie Guo commented on BOOKKEEPER-598: -- BTW, [~ikelly] [~fpj] could any one of

[jira] [Created] (BOOKKEEPER-600) shouldClaim flag isn't cleared for hedwig multiplex java client

Sijie Guo created BOOKKEEPER-600: Summary: shouldClaim flag isn't cleared for hedwig multiplex java client Key: BOOKKEEPER-600 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-600 Project:

[jira] [Created] (BOOKKEEPER-601) readahead cache size isn't updated correctly

Sijie Guo created BOOKKEEPER-601: Summary: readahead cache size isn't updated correctly Key: BOOKKEEPER-601 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-601 Project: Bookkeeper

[jira] [Commented] (BOOKKEEPER-598) Fails to compile - RESUBSCRIBE_EXCEPTION conflict

[ https://issues.apache.org/jira/browse/BOOKKEEPER-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623920#comment-13623920 ] Hadoop QA commented on BOOKKEEPER-598: -- Testing JIRA BOOKKEEPER-598 Patch

[jira] [Commented] (BOOKKEEPER-602) we should have request timeouts rather than channel timeout in PerChannelBookieClient

[ https://issues.apache.org/jira/browse/BOOKKEEPER-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623967#comment-13623967 ] Ivan Kelly commented on BOOKKEEPER-602: --- I think the original implementation did

[jira] [Commented] (BOOKKEEPER-602) we should have request timeouts rather than channel timeout in PerChannelBookieClient

[ https://issues.apache.org/jira/browse/BOOKKEEPER-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623969#comment-13623969 ] Sijie Guo commented on BOOKKEEPER-602: -- yes. would attach the patch later.

[jira] [Commented] (BOOKKEEPER-582) Make bookie and client use protobuf for requests (non-wire part)

[ https://issues.apache.org/jira/browse/BOOKKEEPER-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623976#comment-13623976 ] Ivan Kelly commented on BOOKKEEPER-582: --- I think the two can converge towards

[jira] [Commented] (BOOKKEEPER-564) Better checkpoint mechanism

[ https://issues.apache.org/jira/browse/BOOKKEEPER-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13623992#comment-13623992 ] Ivan Kelly commented on BOOKKEEPER-564: --- With BOOKKEEPER-572 the way we

[jira] [Commented] (BOOKKEEPER-564) Better checkpoint mechanism

[ https://issues.apache.org/jira/browse/BOOKKEEPER-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624238#comment-13624238 ] Sijie Guo commented on BOOKKEEPER-564: -- the patch here already covered the most

[jira] [Commented] (BOOKKEEPER-582) Make bookie and client use protobuf for requests (non-wire part)

[ https://issues.apache.org/jira/browse/BOOKKEEPER-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624260#comment-13624260 ] Sijie Guo commented on BOOKKEEPER-582: -- for server side BC, server is easy to

[jira] [Commented] (BOOKKEEPER-599) NPE in PerChannelBookieClient

[ https://issues.apache.org/jira/browse/BOOKKEEPER-599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13624331#comment-13624331 ] Hadoop QA commented on BOOKKEEPER-599: -- Testing JIRA BOOKKEEPER-599 Patch