[iotdb] branch jira3188 updated (1067865a13 -> 49c5913f24)

[ta...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

tanxinyu pushed a change to branch jira3188
in repository https://gitbox.apache.org/repos/asf/iotdb.git


 discard 1067865a13 split dataRegion/schemaRegion consensus protocol && multiLeaderConsensus init
     add 49c5913f24 split dataRegion/schemaRegion consensus protocol && multiLeaderConsensus init

This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version.  This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:

 * -- * -- B -- O -- O -- O   (1067865a13)
            \
             N -- N -- N   refs/heads/jira3188 (49c5913f24)

You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.

Any revisions marked "omit" are not gone; other references still
refer to them.  Any revisions marked "discard" are gone forever.

No new revisions were added by this update.

Summary of changes:
 .../resources/conf/iotdb-confignode.properties     |  2 +-
 .../confignode/conf/ConfigNodeStartupCheck.java    | 22 +++++++-----
 .../iotdb/confignode/persistence/NodeInfoTest.java |  2 +-
 .../common/response/ConsensusReadResponse.java     |  6 +++-
 .../common/response/ConsensusResponse.java         |  2 +-
 .../apache/iotdb/commons/service/ServiceType.java  |  1 -
 .../db/consensus/SchemaRegionConsensusImpl.java    |  2 +-
 .../scheduler/FragmentInstanceDispatcherImpl.java  | 34 ++++++++++---------
 .../service/thrift/impl/InternalServiceImpl.java   | 39 +++++++++++++---------
 thrift-multi-leader-consensus/pom.xml              | 20 +++++++++++
 10 files changed, 85 insertions(+), 45 deletions(-)