Details

    • Type: Sub-task Sub-task
    • Status: Patch Available
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: HFile, regionserver, Scanners
    • Labels:
      None

      Description

      Scanners should be able to track mvcc read point and send it to server. This is a subtask, so server can use this mvcc as best it can, but doesn't actually have to guarantee it within the scope of this jira.

      1. HBASE-10241.wip0.patch
        74 kB
        Sergey Shelukhin
      2. HBASE-10242.01.patch
        76 kB
        Sergey Shelukhin
      3. HBASE-10242.patch
        79 kB
        Sergey Shelukhin

        Activity

        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12622331/HBASE-10242.01.patch
        against trunk revision .
        ATTACHMENT ID: 12622331

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

        +1 tests included. The patch appears to include 6 new or modified tests.

        +1 hadoop1.0. The patch compiles against the hadoop 1.0 profile.

        +1 hadoop1.1. The patch compiles against the hadoop 1.1 profile.

        -1 javadoc. The javadoc tool appears to have generated 4 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 lineLengths. The patch introduces the following lines longer than 100:
        + /** See

        {@link #ClientScanner(Configuration, Scan, TableName, HConnection, boolean, RpcRetryingCallerFactory)}

        */
        + /** @deprecated Use

        {@link #ClientScanner(Configuration, Scan, TableName, HConnection, boolean)}

        */
        + this(conf, scan, TableName.valueOf(tableName), connection, new RpcRetryingCallerFactory(conf));
        + "\001(\010\022\013\n\003ttl\030\004 \001(\r\022\030\n\007results\030\005 \003(\0132\007.Resu" +
        + new java.lang.String[]

        { "Region", "Scan", "ScannerId", "NumberOfRows", "CloseScanner", "NextCallSeq", "ClientSideMvcc", }

        );
        + new java.lang.String[]

        { "CellsPerResult", "ScannerId", "MoreResults", "Ttl", "Results", "ClientSideMvcc", }

        );

        -1 site. The patch appears to cause mvn site goal to fail.

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

        Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//testReport/
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
        Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//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/12622331/HBASE-10242.01.patch against trunk revision . ATTACHMENT ID: 12622331 +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 6 new or modified tests. +1 hadoop1.0 . The patch compiles against the hadoop 1.0 profile. +1 hadoop1.1 . The patch compiles against the hadoop 1.1 profile. -1 javadoc . The javadoc tool appears to have generated 4 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 lineLengths . The patch introduces the following lines longer than 100: + /** See {@link #ClientScanner(Configuration, Scan, TableName, HConnection, boolean, RpcRetryingCallerFactory)} */ + /** @deprecated Use {@link #ClientScanner(Configuration, Scan, TableName, HConnection, boolean)} */ + this(conf, scan, TableName.valueOf(tableName), connection, new RpcRetryingCallerFactory(conf)); + "\001(\010\022\013\n\003ttl\030\004 \001(\r\022\030\n\007results\030\005 \003(\0132\007.Resu" + + new java.lang.String[] { "Region", "Scan", "ScannerId", "NumberOfRows", "CloseScanner", "NextCallSeq", "ClientSideMvcc", } ); + new java.lang.String[] { "CellsPerResult", "ScannerId", "MoreResults", "Ttl", "Results", "ClientSideMvcc", } ); -1 site . The patch appears to cause mvn site goal to fail. +1 core tests . The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/8381//console This message is automatically generated.
        Hide
        Sergey Shelukhin added a comment -

        feedback from RB

        Show
        Sergey Shelukhin added a comment - feedback from RB
        Hide
        Sergey Shelukhin added a comment -

        test failure appears to be due to my debug logging that I forgot to remove, test takes a long time as such and logging slows it down beyond timeout. So that will pass after update. I will update w/reaction to first round of comments

        Show
        Sergey Shelukhin added a comment - test failure appears to be due to my debug logging that I forgot to remove, test takes a long time as such and logging slows it down beyond timeout. So that will pass after update. I will update w/reaction to first round of comments
        Hide
        Sergey Shelukhin added a comment -

        https://reviews.apache.org/r/16609/

        let me look at the failed test

        Show
        Sergey Shelukhin added a comment - https://reviews.apache.org/r/16609/ let me look at the failed test
        Hide
        Hadoop QA added a comment -

        -1 overall. Here are the results of testing the latest attachment
        http://issues.apache.org/jira/secure/attachment/12621189/HBASE-10242.patch
        against trunk revision .
        ATTACHMENT ID: 12621189

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

        +1 tests included. The patch appears to include 6 new or modified tests.

        +1 hadoop1.0. The patch compiles against the hadoop 1.0 profile.

        +1 hadoop1.1. The patch compiles against the hadoop 1.1 profile.

        -1 javadoc. The javadoc tool appears to have generated 2 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 lineLengths. The patch introduces the following lines longer than 100:
        + /** See

        {@link #ClientScanner(Configuration, Scan, TableName, HConnection, boolean, RpcRetryingCallerFactory)} */
        + /** See {@link #ClientScanner(Configuration, Scan, TableName, HConnection, boolean, RpcRetryingCallerFactory)}

        */
        + /** @deprecated Use

        {@link #ClientScanner(Configuration, Scan, TableName, HConnection, boolean, RpcRetryingCallerFactory)}

        */
        + /** @deprecated Use

        {@link #ClientScanner(Configuration, Scan, TableName, HConnection, boolean)}

        */
        + this(conf, scan, TableName.valueOf(tableName), connection, new RpcRetryingCallerFactory(conf));
        + "\001(\010\022\013\n\003ttl\030\004 \001(\r\022\030\n\007results\030\005 \003(\0132\007.Resu" +
        + new java.lang.String[]

        { "Region", "Scan", "ScannerId", "NumberOfRows", "CloseScanner", "NextCallSeq", "ClientSideMvcc", }

        );
        + new java.lang.String[]

        { "CellsPerResult", "ScannerId", "MoreResults", "Ttl", "Results", "ClientSideMvcc", }

        );

        -1 site. The patch appears to cause mvn site goal to fail.

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

        -1 core zombie tests. There are 1 zombie test(s): at org.apache.hadoop.hbase.io.encoding.TestEncodedSeekers.testEncodedSeeker(TestEncodedSeekers.java:124)

        Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//testReport/
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
        Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//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/12621189/HBASE-10242.patch against trunk revision . ATTACHMENT ID: 12621189 +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 6 new or modified tests. +1 hadoop1.0 . The patch compiles against the hadoop 1.0 profile. +1 hadoop1.1 . The patch compiles against the hadoop 1.1 profile. -1 javadoc . The javadoc tool appears to have generated 2 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 lineLengths . The patch introduces the following lines longer than 100: + /** See {@link #ClientScanner(Configuration, Scan, TableName, HConnection, boolean, RpcRetryingCallerFactory)} */ + /** See {@link #ClientScanner(Configuration, Scan, TableName, HConnection, boolean, RpcRetryingCallerFactory)} */ + /** @deprecated Use {@link #ClientScanner(Configuration, Scan, TableName, HConnection, boolean, RpcRetryingCallerFactory)} */ + /** @deprecated Use {@link #ClientScanner(Configuration, Scan, TableName, HConnection, boolean)} */ + this(conf, scan, TableName.valueOf(tableName), connection, new RpcRetryingCallerFactory(conf)); + "\001(\010\022\013\n\003ttl\030\004 \001(\r\022\030\n\007results\030\005 \003(\0132\007.Resu" + + new java.lang.String[] { "Region", "Scan", "ScannerId", "NumberOfRows", "CloseScanner", "NextCallSeq", "ClientSideMvcc", } ); + new java.lang.String[] { "CellsPerResult", "ScannerId", "MoreResults", "Ttl", "Results", "ClientSideMvcc", } ); -1 site . The patch appears to cause mvn site goal to fail. -1 core tests . The patch failed these unit tests: -1 core zombie tests . There are 1 zombie test(s): at org.apache.hadoop.hbase.io.encoding.TestEncodedSeekers.testEncodedSeeker(TestEncodedSeekers.java:124) Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/8322//console This message is automatically generated.
        Hide
        Enis Soztutar added a comment -

        Can you please put this in RB?

        Show
        Enis Soztutar added a comment - Can you please put this in RB?
        Hide
        Sergey Shelukhin added a comment -

        Made the tests work for split and merge. So aside from server part that would preserve mvcc in WAL, and for longer in files, this is final patch

        Show
        Sergey Shelukhin added a comment - Made the tests work for split and merge. So aside from server part that would preserve mvcc in WAL, and for longer in files, this is final 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/12620708/HBASE-10241.wip0.patch
        against trunk revision .
        ATTACHMENT ID: 12620708

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

        +1 tests included. The patch appears to include 6 new or modified tests.

        +1 hadoop1.0. The patch compiles against the hadoop 1.0 profile.

        +1 hadoop1.1. The patch compiles against the hadoop 1.1 profile.

        -1 javadoc. The javadoc tool appears to have generated 2 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 lineLengths. The patch does not introduce lines longer than 100

        -1 site. The patch appears to cause mvn site goal to fail.

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

        Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//testReport/
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
        Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
        Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//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/12620708/HBASE-10241.wip0.patch against trunk revision . ATTACHMENT ID: 12620708 +1 @author . The patch does not contain any @author tags. +1 tests included . The patch appears to include 6 new or modified tests. +1 hadoop1.0 . The patch compiles against the hadoop 1.0 profile. +1 hadoop1.1 . The patch compiles against the hadoop 1.1 profile. -1 javadoc . The javadoc tool appears to have generated 2 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 lineLengths . The patch does not introduce lines longer than 100 -1 site . The patch appears to cause mvn site goal to fail. -1 core tests . The patch failed these unit tests: Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/8294//console This message is automatically generated.
        Hide
        Sergey Shelukhin added a comment -

        WIP patch. It already works for restricted reopen scenarios (see hack in test); for split it doesn't work so far because server part is not implemented, so compaction does not preserve mvcc.
        TODOs:

        • rig the test for splits and merges to work
        • make work in reverse scanner (not needed for small scanner?)
        • make the new public methods private for now if this is to be committed before the server part. Or they can go in together, this is not needed.
        Show
        Sergey Shelukhin added a comment - WIP patch. It already works for restricted reopen scenarios (see hack in test); for split it doesn't work so far because server part is not implemented, so compaction does not preserve mvcc. TODOs: rig the test for splits and merges to work make work in reverse scanner (not needed for small scanner?) make the new public methods private for now if this is to be committed before the server part. Or they can go in together, this is not needed.
        Hide
        Sergey Shelukhin added a comment -

        Problem (talking to myself): splits and merges.
        Actually quite a bit of a problem, because by default the scanner will lose consistency on these - it's a new region so new mvcc will be obtained; but the simple alternative (tracking them and reusing mvcc) is even worse, esp. for merge - for example, if the first region had much lower mvcc before merge because it came from different server, the second region data with its old high mvcc numbers could become invisible.
        Probably, when obtaining the first mvcc for the region, the scanner will have track it for key range, and re-use it across splits / separate requests for merges.
        Almost makes you wonder if getting mvccs in advance is worth it for consistent scanner - that would be one request to a few RSes (that hold the requisite regions).

        Show
        Sergey Shelukhin added a comment - Problem (talking to myself): splits and merges. Actually quite a bit of a problem, because by default the scanner will lose consistency on these - it's a new region so new mvcc will be obtained; but the simple alternative (tracking them and reusing mvcc) is even worse, esp. for merge - for example, if the first region had much lower mvcc before merge because it came from different server, the second region data with its old high mvcc numbers could become invisible. Probably, when obtaining the first mvcc for the region, the scanner will have track it for key range, and re-use it across splits / separate requests for merges. Almost makes you wonder if getting mvccs in advance is worth it for consistent scanner - that would be one request to a few RSes (that hold the requisite regions).

          People

          • Assignee:
            Sergey Shelukhin
            Reporter:
            Sergey Shelukhin
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:

              Development