[ignite-3] branch ignite-18323 updated (581a3cdeb4 -> 0a63f10acb)

[am...@apache.org]

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

amashenkov pushed a change to branch ignite-18323
in repository https://gitbox.apache.org/repos/asf/ignite-3.git


 discard 581a3cdeb4 Disable broken tests.
 discard 25e9ca45b3 wip. fix hanging on synchronous operation inside busylock in RebalanceRaftGroupEventsListener
 discard 094643382e wip. fix hanging on synchronous operation inside busylock in TableManager
 discard 1ef6b3a32d wip. fix wrong busylock usage in MetaStorageManager
 discard e07cd9f254 wip. init raft group in a background.
 discard 4f7bc83b0c wip. fix leader await
     add 2bc985b64a wip. fix leader await
     add b354a7d110 wip. init raft group in a background.
     add 3361b8798a wip. fix wrong busylock usage in MetaStorageManager
     add 69becdcf4b wip. fix hanging on synchronous operation inside busylock in TableManager
     add 7881e6f229 wip. fix hanging on synchronous operation inside busylock in RebalanceRaftGroupEventsListener
     add 0a63f10acb Disable broken tests.

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   (581a3cdeb4)
            \
             N -- N -- N   refs/heads/ignite-18323 (0a63f10acb)

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:
 .../ignite/internal/raft/RaftGroupServiceImpl.java       | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)