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

CRZbulabula pushed a change to branch fix-region-allocation-it-timeout
in repository https://gitbox.apache.org/repos/asf/iotdb.git


    omit 39f89f52f03 Fix per-database region allocation IT timeout
     add dc4493b84af Remove IoTConsensus auto leader balance toggle

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   (39f89f52f03)
            \
             N -- N -- N   refs/heads/fix-region-allocation-it-timeout 
(dc4493b84af)

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:
 .../apache/iotdb/it/env/cluster/config/MppCommonConfig.java  |  9 ---------
 .../iotdb/it/env/cluster/config/MppSharedCommonConfig.java   |  8 --------
 .../iotdb/it/env/remote/config/RemoteCommonConfig.java       |  6 ------
 .../main/java/org/apache/iotdb/itbase/env/CommonConfig.java  |  3 ---
 .../it/load/IoTDBMultiDBRegionGroupLeaderDistributionIT.java |  1 -
 .../it/load/IoTDBPerDatabaseRegionGroupAllocationIT.java     |  5 +----
 .../it/load/IoTDBRegionGroupLeaderDistributionIT.java        |  1 -
 .../org/apache/iotdb/confignode/conf/ConfigNodeConfig.java   | 12 ------------
 .../apache/iotdb/confignode/conf/ConfigNodeDescriptor.java   |  6 ------
 .../confignode/manager/load/balancer/RouteBalancer.java      |  9 +++------
 .../assembly/resources/conf/iotdb-system.properties.template |  7 -------
 11 files changed, 4 insertions(+), 63 deletions(-)

Reply via email to