HBase
  1. HBase
  2. HBASE-5886

Add new metric for possible data loss due to puts without WAL

    Details

    • Hadoop Flags:
      Reviewed

      Description

      Add a metrics to keep track of puts without WAL and possible data loss size.

      1. 5886-0.94.patch
        7 kB
        Lars Hofhansl
      2. HBASE-5886-v4.patch
        7 kB
        Matteo Bertozzi
      3. HBASE-5886-v3.patch
        7 kB
        stack
      4. HBASE-5886-v2.patch
        7 kB
        Matteo Bertozzi
      5. HBASE-5886-v1.patch
        6 kB
        Matteo Bertozzi
      6. HBASE-5886-v0.patch
        7 kB
        Matteo Bertozzi

        Activity

        Hide
        Todd Lipcon added a comment -

        I think the metrics names could be improved here – "putWithoutWAL" could be "numPutsWithoutWAL" and "possibleDataLossSize" perhaps "mbInMemoryWithoutWAL"?

        • in recordPossibleDataLossNoWal, use getAndIncrement instead of incrementAndGet, and compare the result to 0 – otherwise you're doing an extra atomic op and have a potential race
        • the warning message should include the client IP address as well as the region ID. Perhaps something like "Client 123.123.123.123 writing data to region abcdef12345 with WAL disabled. Data may be lost in the event of a crash. Will not log further warnings for this region."
        • the debug message when setting possibleDataLossSize back to 0 seems unnecessary.
        • DEFAULT_WARN_NO_WAL_INTERVAL is unused
        Show
        Todd Lipcon added a comment - I think the metrics names could be improved here – "putWithoutWAL" could be "numPutsWithoutWAL" and "possibleDataLossSize" perhaps "mbInMemoryWithoutWAL"? in recordPossibleDataLossNoWal, use getAndIncrement instead of incrementAndGet , and compare the result to 0 – otherwise you're doing an extra atomic op and have a potential race the warning message should include the client IP address as well as the region ID. Perhaps something like "Client 123.123.123.123 writing data to region abcdef12345 with WAL disabled. Data may be lost in the event of a crash. Will not log further warnings for this region." the debug message when setting possibleDataLossSize back to 0 seems unnecessary. DEFAULT_WARN_NO_WAL_INTERVAL is unused
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12524562/HBASE-5886-v0.patch
        against trunk revision .

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

        -1 tests included. The patch doesn't appear to include any new or modified tests.
        Please justify why no new tests are needed for this patch.
        Also please list what manual steps were performed to verify this patch.

        +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 2 new Findbugs (version 1.3.9) warnings.

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

        -1 core tests. The patch failed these unit tests:
        org.apache.hadoop.hbase.io.TestHeapSize

        Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1659//testReport/
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1659//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
        Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1659//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/12524562/HBASE-5886-v0.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +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 2 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.io.TestHeapSize Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1659//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1659//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1659//console This message is automatically generated.
        Hide
        Elliott Clark added a comment -
        • This patch fails unit tests. org.apache.hadoop.hbase.io.TestHeapSize
        • recordPossibleDataLossNoWal seems like the wrong name. There's no possible data loss until a region server crashes without flushing. Maybe something like recordPutWithoutWal.
        • I don't think the warn in recordPossibleDataLossNoWal is the right level. Nothing has gone wrong; someone has just decided to opt for a speedy put vs a safe one. I'm not even sure that a log is needed here.
        • How far off of the actual size of the data is the heapSize of the kv ?
        • Putting data about puts without WAL into org.apache.hadoop.hbase.regionserver.metrics.OperationMetrics seems like it would be good.
        Show
        Elliott Clark added a comment - This patch fails unit tests. org.apache.hadoop.hbase.io.TestHeapSize recordPossibleDataLossNoWal seems like the wrong name. There's no possible data loss until a region server crashes without flushing. Maybe something like recordPutWithoutWal. I don't think the warn in recordPossibleDataLossNoWal is the right level. Nothing has gone wrong; someone has just decided to opt for a speedy put vs a safe one. I'm not even sure that a log is needed here. How far off of the actual size of the data is the heapSize of the kv ? Putting data about puts without WAL into org.apache.hadoop.hbase.regionserver.metrics.OperationMetrics seems like it would be good.
        Hide
        Matteo Bertozzi added a comment -

        Renamed metrics and function, removed unused DEFAULT_ constant and the log on flush.

        I'm not sure about how to get the client ip from the region, since the region shouldn't be aware of the client. Maybe moving something in Region Server?

        heapSize() reflect the in memory state, so you've pointer size and so on... maybe using kv.getValueLength() + kv.getKeyLength() or just valueLength()?

        I've to look at OperationMetrics, but seems that updatePutMetrics() is not called for doMiniBatchPut()... (I've to take a look at that)

        Show
        Matteo Bertozzi added a comment - Renamed metrics and function, removed unused DEFAULT_ constant and the log on flush. I'm not sure about how to get the client ip from the region, since the region shouldn't be aware of the client. Maybe moving something in Region Server? heapSize() reflect the in memory state, so you've pointer size and so on... maybe using kv.getValueLength() + kv.getKeyLength() or just valueLength()? I've to look at OperationMetrics, but seems that updatePutMetrics() is not called for doMiniBatchPut()... (I've to take a look at that)
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12524847/HBASE-5886-v1.patch
        against trunk revision .

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

        -1 tests included. The patch doesn't appear to include any new or modified tests.
        Please justify why no new tests are needed for this patch.
        Also please list what manual steps were performed to verify this patch.

        +1 hadoop23. The patch compiles against the hadoop 0.23.x profile.

        +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 2 new Findbugs (version 1.3.9) warnings.

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

        -1 core tests. The patch failed these unit tests:
        org.apache.hadoop.hbase.io.TestHeapSize

        Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1668//testReport/
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1668//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
        Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1668//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/12524847/HBASE-5886-v1.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 hadoop23. The patch compiles against the hadoop 0.23.x profile. +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 2 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.io.TestHeapSize Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1668//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1668//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1668//console This message is automatically generated.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12524910/HBASE-5886-v2.patch
        against trunk revision .

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

        -1 tests included. The patch doesn't appear to include any new or modified tests.
        Please justify why no new tests are needed for this patch.
        Also please list what manual steps were performed to verify this patch.

        +1 hadoop23. The patch compiles against the hadoop 0.23.x profile.

        +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 1.3.9) warnings.

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

        -1 core tests. The patch failed these unit tests:
        org.apache.hadoop.hbase.io.TestHeapSize

        Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1671//testReport/
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1671//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
        Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1671//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/12524910/HBASE-5886-v2.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 hadoop23. The patch compiles against the hadoop 0.23.x profile. +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 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.io.TestHeapSize Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1671//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1671//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1671//console This message is automatically generated.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12524913/HBASE-5886-v2.patch
        against trunk revision .

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

        -1 tests included. The patch doesn't appear to include any new or modified tests.
        Please justify why no new tests are needed for this patch.
        Also please list what manual steps were performed to verify this patch.

        +1 hadoop23. The patch compiles against the hadoop 0.23.x profile.

        +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 1.3.9) warnings.

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

        +1 core tests. The patch passed unit tests in .

        Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1672//testReport/
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1672//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
        Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1672//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/12524913/HBASE-5886-v2.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 hadoop23. The patch compiles against the hadoop 0.23.x profile. +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 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1672//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1672//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1672//console This message is automatically generated.
        Hide
        Nicolas Spiegelberg added a comment - - edited

        I'm confused about why this metric is useful. This metric is never accurate at determining data loss because querying it is async from the Put path. If you are looking for a restart point, you should have another thread call HTable.flush() and checkpoint or add an API to query for the latest timestamp in a CF's storefile.

        Edit: s/and/at

        Show
        Nicolas Spiegelberg added a comment - - edited I'm confused about why this metric is useful. This metric is never accurate at determining data loss because querying it is async from the Put path. If you are looking for a restart point, you should have another thread call HTable.flush() and checkpoint or add an API to query for the latest timestamp in a CF's storefile. Edit: s/and/at
        Hide
        Matteo Bertozzi added a comment -

        @Nicolas the metric is not meant to be precise but just to give an hint about possible data loss.

        Show
        Matteo Bertozzi added a comment - @Nicolas the metric is not meant to be precise but just to give an hint about possible data loss.
        Hide
        Todd Lipcon added a comment -

        To fill in some color, we had a customer complaining of data loss after a crash. We spent many hours doing post mortem analysis, and only after we ruled out lots and lots of corner case possibilities did we come to find out that the user's application had set the writeToWAL flag false in a small number of their puts. Having the log message and the metric make it easy to say "yea, you got data loss, but here's a smoking gun which shows you explicitly disabled WAL for some puts in that region". This is important in lots of environments where HBase ops/support may be distinct from the users writing applications, and may not even have access to the source code of those applications.

        Show
        Todd Lipcon added a comment - To fill in some color, we had a customer complaining of data loss after a crash. We spent many hours doing post mortem analysis, and only after we ruled out lots and lots of corner case possibilities did we come to find out that the user's application had set the writeToWAL flag false in a small number of their puts. Having the log message and the metric make it easy to say "yea, you got data loss, but here's a smoking gun which shows you explicitly disabled WAL for some puts in that region". This is important in lots of environments where HBase ops/support may be distinct from the users writing applications, and may not even have access to the source code of those applications.
        Hide
        Matteo Bertozzi added a comment -

        Any other feedback on the patch?
        Add a config option "hbase.warn.nowal" to write the warn message only if the option is set?

        Show
        Matteo Bertozzi added a comment - Any other feedback on the patch? Add a config option "hbase.warn.nowal" to write the warn message only if the option is set?
        Hide
        Todd Lipcon added a comment -

        Or maybe drop it to INFO level?

        Show
        Todd Lipcon added a comment - Or maybe drop it to INFO level?
        Hide
        stack added a comment -

        I love the war story. Any more where that came from for our entertainment?

        Patch looks good to me. I can drop the log level on commit if thats what you want Matteo.

        Show
        stack added a comment - I love the war story. Any more where that came from for our entertainment? Patch looks good to me. I can drop the log level on commit if thats what you want Matteo.
        Hide
        Matteo Bertozzi added a comment -

        INFO level is good for me. The ideas is having something to grep.

        Show
        Matteo Bertozzi added a comment - INFO level is good for me. The ideas is having something to grep.
        Hide
        stack added a comment -

        Hmm... trunk has changed. Here is an updated patch.

        Show
        stack added a comment - Hmm... trunk has changed. Here is an updated patch.
        Hide
        stack added a comment -

        Retrying to see that I got the heap sizings right.

        Show
        stack added a comment - Retrying to see that I got the heap sizings right.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12525470/HBASE-5886-v4.patch
        against trunk revision .

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

        -1 tests included. The patch doesn't appear to include any new or modified tests.
        Please justify why no new tests are needed for this patch.
        Also please list what manual steps were performed to verify this patch.

        +1 hadoop23. The patch compiles against the hadoop 0.23.x profile.

        +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 1.3.9) warnings.

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

        +1 core tests. The patch passed unit tests in .

        Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1746//testReport/
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1746//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html
        Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1746//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/12525470/HBASE-5886-v4.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 hadoop23. The patch compiles against the hadoop 0.23.x profile. +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 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1746//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1746//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1746//console This message is automatically generated.
        Hide
        stack added a comment -

        Committed to trunk. Want this is 0.94 Lars?

        Show
        stack added a comment - Committed to trunk. Want this is 0.94 Lars?
        Hide
        stack added a comment -

        Leaving open till we figure if it belongs in 0.94.1

        Show
        stack added a comment - Leaving open till we figure if it belongs in 0.94.1
        Hide
        Lars Hofhansl added a comment -

        Yeah, would be good in 0.94. Here's the 0.94 patch.

        Show
        Lars Hofhansl added a comment - Yeah, would be good in 0.94. Here's the 0.94 patch.
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12525532/5886-0.94.patch
        against trunk revision .

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

        -1 tests included. The patch doesn't appear to include any new or modified tests.
        Please justify why no new tests are needed for this patch.
        Also please list what manual steps were performed to verify this patch.

        -1 patch. The patch command could not apply the patch.

        Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1756//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/12525532/5886-0.94.patch against trunk revision . +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1756//console This message is automatically generated.
        Hide
        Hudson added a comment -

        Integrated in HBase-TRUNK #2845 (See https://builds.apache.org/job/HBase-TRUNK/2845/)
        HBASE-5886 Add new metric for possible data loss due to puts without WAL (Revision 1333676)

        Result = SUCCESS
        stack :
        Files :

        • /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
        • /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
        • /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/metrics/RegionServerMetrics.java
        Show
        Hudson added a comment - Integrated in HBase-TRUNK #2845 (See https://builds.apache.org/job/HBase-TRUNK/2845/ ) HBASE-5886 Add new metric for possible data loss due to puts without WAL (Revision 1333676) Result = SUCCESS stack : Files : /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/metrics/RegionServerMetrics.java
        Hide
        Lars Hofhansl added a comment -

        Committed to 0.94 too.

        Show
        Lars Hofhansl added a comment - Committed to 0.94 too.
        Hide
        Hudson added a comment -

        Integrated in HBase-0.94 #177 (See https://builds.apache.org/job/HBase-0.94/177/)
        HBASE-5886 Add new metric for possible data loss due to puts without WAL (Revision 1333689)

        Result = SUCCESS
        larsh :
        Files :

        • /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
        • /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
        • /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/metrics/RegionServerMetrics.java
        Show
        Hudson added a comment - Integrated in HBase-0.94 #177 (See https://builds.apache.org/job/HBase-0.94/177/ ) HBASE-5886 Add new metric for possible data loss due to puts without WAL (Revision 1333689) Result = SUCCESS larsh : Files : /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/metrics/RegionServerMetrics.java
        Hide
        Hudson added a comment -

        Integrated in HBase-TRUNK-security #191 (See https://builds.apache.org/job/HBase-TRUNK-security/191/)
        HBASE-5886 Add new metric for possible data loss due to puts without WAL (Revision 1333676)

        Result = SUCCESS
        stack :
        Files :

        • /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
        • /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
        • /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/metrics/RegionServerMetrics.java
        Show
        Hudson added a comment - Integrated in HBase-TRUNK-security #191 (See https://builds.apache.org/job/HBase-TRUNK-security/191/ ) HBASE-5886 Add new metric for possible data loss due to puts without WAL (Revision 1333676) Result = SUCCESS stack : Files : /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java /hbase/trunk/src/main/java/org/apache/hadoop/hbase/regionserver/metrics/RegionServerMetrics.java
        Hide
        Hudson added a comment -

        Integrated in HBase-0.94-security #26 (See https://builds.apache.org/job/HBase-0.94-security/26/)
        HBASE-5886 Add new metric for possible data loss due to puts without WAL (Revision 1333689)

        Result = SUCCESS
        larsh :
        Files :

        • /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
        • /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java
        • /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/metrics/RegionServerMetrics.java
        Show
        Hudson added a comment - Integrated in HBase-0.94-security #26 (See https://builds.apache.org/job/HBase-0.94-security/26/ ) HBASE-5886 Add new metric for possible data loss due to puts without WAL (Revision 1333689) Result = SUCCESS larsh : Files : /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/metrics/RegionServerMetrics.java

          People

          • Assignee:
            Matteo Bertozzi
            Reporter:
            Matteo Bertozzi
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development