ZooKeeper
  1. ZooKeeper
  2. ZOOKEEPER-2019

Unhandled exception when setting invalid limits data in /zookeeper/quota/some/path/zookeeper_limits

    Details

    • Type: Bug Bug
    • Status: Patch Available
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 3.5.2, 3.6.0
    • Component/s: server
    • Labels:
      None

      Description

      If you have quotas properly set for a given path, i.e.:

      create /zookeeper/quota/test/zookeeper_limits 'count=1,bytes=100'
      create /zookeeper/quota/test/zookeeper_stats 'count=1,bytes=100'
      

      and then you update the limits znode with bogus data, i.e.:

      set /zookeeper/quota/test/zookeeper_limits ''
      

      you'll crash the cluster because IllegalArgumentException isn't handled when dealing with quotas znodes:

      https://github.com/apache/zookeeper/blob/ZOOKEEPER-823/src/java/main/org/apache/zookeeper/server/DataTree.java#L379
      https://github.com/apache/zookeeper/blob/ZOOKEEPER-823/src/java/main/org/apache/zookeeper/server/DataTree.java#L425

      We should handle IllegalArgumentException. Optionally, we should also throw BadArgumentsException from PrepRequestProcessor.

      Review Board: https://reviews.apache.org/r/25968/

      1. ZOOKEEPER-2019.patch
        10 kB
        Raul Gutierrez Segales
      2. ZOOKEEPER-2019.patch
        2 kB
        Raul Gutierrez Segales
      3. ZOOKEEPER-2019-v2.patch
        12 kB
        Hongchao Deng
      4. ZOOKEEPER-2019-v3.patch
        12 kB
        Hongchao Deng
      5. ZOOKEEPER-2019-ver1.patch
        10 kB
        Alexander Shraer

        Activity

        Hide
        Raul Gutierrez Segales added a comment -

        This is does the bare minimum (i.e.: doesn't crash when reading a bad zookeeper_limits znode). We could probably do more, i.e.: sanitize zookeeper_limits znodes as they are being created/updated (the reconfig commands do this). But since the quotas stuff might change (it's very basic currently) Maybe we don't want to set validations yet.

        Thoughts?

        cc: Patrick Hunt, Alexander Shraer, Hongchao Deng

        Show
        Raul Gutierrez Segales added a comment - This is does the bare minimum (i.e.: doesn't crash when reading a bad zookeeper_limits znode). We could probably do more, i.e.: sanitize zookeeper_limits znodes as they are being created/updated (the reconfig commands do this). But since the quotas stuff might change (it's very basic currently) Maybe we don't want to set validations yet. Thoughts? cc: Patrick Hunt , Alexander Shraer , Hongchao Deng
        Hide
        Alexander Shraer added a comment -

        Raul, could you also add a test for this ?

        The parsing function checks the first split but has these two statements that can also fail, without checks:

        count = Integer.parseInt(split[0].split("=")[1]);
        bytes = Long.parseLong(split[1].split("=")[1]);

        perhaps its better to use a Properties object for parsing the string or something similar, not sure.

        Its also weird that updateCount and updateBytes are almost identical and yet they are two different functions, so create and delete have to call them both in a sequence doing twice the same things essentially.

        Show
        Alexander Shraer added a comment - Raul, could you also add a test for this ? The parsing function checks the first split but has these two statements that can also fail, without checks: count = Integer.parseInt(split [0] .split("=") [1] ); bytes = Long.parseLong(split [1] .split("=") [1] ); perhaps its better to use a Properties object for parsing the string or something similar, not sure. Its also weird that updateCount and updateBytes are almost identical and yet they are two different functions, so create and delete have to call them both in a sequence doing twice the same things essentially.
        Hide
        Raul Gutierrez Segales added a comment -

        Thanks for the quick review Alexander Shraer, I've addressed the items you mentioned.

        Show
        Raul Gutierrez Segales added a comment - Thanks for the quick review Alexander Shraer , I've addressed the items you mentioned.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12664289/ZOOKEEPER-2019.patch
        against trunk revision 1620111.

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

        +1 tests included. The patch appears to include 3 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 2.0.3) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        -1 core tests. The patch failed core unit tests.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2300//testReport/
        Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2300//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
        Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2300//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12664289/ZOOKEEPER-2019.patch against trunk revision 1620111. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 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 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2300//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2300//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2300//console This message is automatically generated.
        Hide
        Raul Gutierrez Segales added a comment -

        Failures seem unrelated:

            [exec]     [junit] 2014-08-26 02:53:32,839 [myid:] - INFO  [main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED testReadArrayOffsetLength_LengthTooLarge
             [exec]     [junit] 2014-08-26 02:56:13,636 [myid:] - INFO  [main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED testTooManySnapshotsNonessential
             [exec]     [junit] 2014-08-26 02:56:13,641 [myid:] - INFO  [main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED testTooManySnapshotsEssential
             [exec]     [junit] 2014-08-26 02:56:13,650 [myid:] - INFO  [main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED testTryWithResourceThrottle
             [exec]     [junit] Test org.apache.zookeeper.test.NioNettySuiteHammerTest FAILED (crashed)
             [exec]     [junit] 2014-08-26 03:21:37,644 [myid:] - INFO  [main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED testPortChange
             [exec]     [junit] 2014-08-26 03:21:37,683 [myid:] - INFO  [main:ZKTestCase$1@70] - FAILED testPortChange
             [exec]     [junit] Test org.apache.zookeeper.test.ReconfigTest FAILED
             [exec]     [junit] 2014-08-26 03:24:11,194 [myid:] - INFO  [main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED testTwoInvalidHostAddresses
             [exec] BUILD FAILED
        
        Show
        Raul Gutierrez Segales added a comment - Failures seem unrelated: [exec] [junit] 2014-08-26 02:53:32,839 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED testReadArrayOffsetLength_LengthTooLarge [exec] [junit] 2014-08-26 02:56:13,636 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED testTooManySnapshotsNonessential [exec] [junit] 2014-08-26 02:56:13,641 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED testTooManySnapshotsEssential [exec] [junit] 2014-08-26 02:56:13,650 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED testTryWithResourceThrottle [exec] [junit] Test org.apache.zookeeper.test.NioNettySuiteHammerTest FAILED (crashed) [exec] [junit] 2014-08-26 03:21:37,644 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED testPortChange [exec] [junit] 2014-08-26 03:21:37,683 [myid:] - INFO [main:ZKTestCase$1@70] - FAILED testPortChange [exec] [junit] Test org.apache.zookeeper.test.ReconfigTest FAILED [exec] [junit] 2014-08-26 03:24:11,194 [myid:] - INFO [main:JUnit4ZKTestRunner$LoggedInvokeMethod@62] - TEST METHOD FAILED testTwoInvalidHostAddresses [exec] BUILD FAILED
        Hide
        Alexander Shraer added a comment -

        Thanks Raul! I made a small change to the code that was doing the parsing, take a look. The motivation is to check not only the numbers but also the strings 'count' and 'bytes' and throw an exception if something is wrong.

        Show
        Alexander Shraer added a comment - Thanks Raul! I made a small change to the code that was doing the parsing, take a look. The motivation is to check not only the numbers but also the strings 'count' and 'bytes' and throw an exception if something is wrong.
        Hide
        Raul Gutierrez Segales added a comment -

        This indeed reads much better, thanks Alexander Shraer! Much easier to extend (i.e.: I suspect we'll want to add more things like write/read rates, etc.) too.

        Show
        Raul Gutierrez Segales added a comment - This indeed reads much better, thanks Alexander Shraer ! Much easier to extend (i.e.: I suspect we'll want to add more things like write/read rates, etc.) too.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12664311/ZOOKEEPER-2019-ver1.patch
        against trunk revision 1620111.

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

        +1 tests included. The patch appears to include 3 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 2.0.3) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        -1 core tests. The patch failed core unit tests.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2301//testReport/
        Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2301//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
        Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2301//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12664311/ZOOKEEPER-2019-ver1.patch against trunk revision 1620111. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 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 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2301//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2301//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2301//console This message is automatically generated.
        Hide
        Alexander Shraer added a comment -

        +1, failures look unrelated.

        Show
        Alexander Shraer added a comment - +1, failures look unrelated.
        Hide
        Raul Gutierrez Segales added a comment -

        Alexander Shraer: slightly worried about the perf implications of parsing the stats & limits znodes on every request (plus the costs of instantiating a Properties object, etc.)... thoughts?

        Show
        Raul Gutierrez Segales added a comment - Alexander Shraer : slightly worried about the perf implications of parsing the stats & limits znodes on every request (plus the costs of instantiating a Properties object, etc.)... thoughts?
        Hide
        Alexander Shraer added a comment -

        well, I see that DataTree uses a trie to find the max prefix with quota before going to the znodes and doing parsing.
        unfortunately the info in each trie node is just a boolean. But I guess each node could also store an object
        such as StatsTrack, which could make things a bit faster.

        Show
        Alexander Shraer added a comment - well, I see that DataTree uses a trie to find the max prefix with quota before going to the znodes and doing parsing. unfortunately the info in each trie node is just a boolean. But I guess each node could also store an object such as StatsTrack, which could make things a bit faster.
        Hide
        Alexander Shraer added a comment -

        Raul Gutierrez Segales, should I commit this ?

        Show
        Alexander Shraer added a comment - Raul Gutierrez Segales , should I commit this ?
        Hide
        Raul Gutierrez Segales added a comment -

        Alexander Shraer: I'd say yes, to have basic safety checks, and we can revisit afterwards - thanks Alex!

        Show
        Raul Gutierrez Segales added a comment - Alexander Shraer : I'd say yes, to have basic safety checks, and we can revisit afterwards - thanks Alex!
        Hide
        Patrick Hunt added a comment -

        Any insight on how big an impact this is to performance? You could use zkpython for e.g. to try a few scenarios...

        Show
        Patrick Hunt added a comment - Any insight on how big an impact this is to performance? You could use zkpython for e.g. to try a few scenarios...
        Hide
        Hongchao Deng added a comment -

        I do some change and also address the perf concern.

        Show
        Hongchao Deng added a comment - I do some change and also address the perf concern.
        Hide
        Hongchao Deng added a comment -
        Show
        Hongchao Deng added a comment - Also created a RB: https://reviews.apache.org/r/25968/
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12670848/ZOOKEEPER-2019-v2.patch
        against trunk revision 1626008.

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

        +1 tests included. The patch appears to include 3 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 appears to introduce 1 new Findbugs (version 2.0.3) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        -1 core tests. The patch failed core unit tests.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2347//testReport/
        Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2347//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
        Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2347//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12670848/ZOOKEEPER-2019-v2.patch against trunk revision 1626008. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 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 appears to introduce 1 new Findbugs (version 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2347//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2347//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2347//console This message is automatically generated.
        Hide
        Hongchao Deng added a comment -

        fix findbug warning.

        Show
        Hongchao Deng added a comment - fix findbug warning.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12670883/ZOOKEEPER-2019-v3.patch
        against trunk revision 1626008.

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

        +1 tests included. The patch appears to include 3 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 appears to introduce 1 new Findbugs (version 2.0.3) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        -1 core tests. The patch failed core unit tests.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2348//testReport/
        Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2348//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
        Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2348//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12670883/ZOOKEEPER-2019-v3.patch against trunk revision 1626008. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 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 appears to introduce 1 new Findbugs (version 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2348//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2348//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2348//console This message is automatically generated.
        Hide
        Hongchao Deng added a comment -

        The previous v3 was a wrong one uploaded...

        Show
        Hongchao Deng added a comment - The previous v3 was a wrong one uploaded...
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12670891/ZOOKEEPER-2019-v3.patch
        against trunk revision 1626008.

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

        +1 tests included. The patch appears to include 3 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 2.0.3) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        -1 core tests. The patch failed core unit tests.

        +1 contrib tests. The patch passed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2349//testReport/
        Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2349//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
        Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2349//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12670891/ZOOKEEPER-2019-v3.patch against trunk revision 1626008. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 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 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2349//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2349//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2349//console This message is automatically generated.
        Hide
        Hongchao Deng added a comment -

        Raul Gutierrez SegalesAlexander Shraer

        I made an optional quota and limit stat inside DataNode. This makes parsing only required on first time.

        Show
        Hongchao Deng added a comment - Raul Gutierrez Segales Alexander Shraer I made an optional quota and limit stat inside DataNode. This makes parsing only required on first time.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12670891/ZOOKEEPER-2019-v3.patch
        against trunk revision 1672934.

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

        +1 tests included. The patch appears to include 3 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 2.0.3) warnings.

        +1 release audit. The applied patch does not increase the total number of release audit warnings.

        -1 core tests. The patch failed core unit tests.

        -1 contrib tests. The patch failed contrib unit tests.

        Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2621//testReport/
        Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2621//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
        Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2621//console

        This message is automatically generated.

        Show
        Hadoop QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12670891/ZOOKEEPER-2019-v3.patch against trunk revision 1672934. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 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 2.0.3) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. -1 contrib tests. The patch failed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2621//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2621//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/2621//console This message is automatically generated.

          People

          • Assignee:
            Raul Gutierrez Segales
            Reporter:
            Raul Gutierrez Segales
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:

              Development