This is an automated email from the ASF dual-hosted git repository.
nicholasjiang pushed a change to branch branch-0.4
in repository https://gitbox.apache.org/repos/asf/celeborn.git
omit 5c384f1a1 [CELEBORN-1316] Override toString method for StoreVersion
omit 25093ef00 [CELEBORN-1315] Manually close the RocksDB/LevelDB instance
when checkVersion throw Exception
omit 3f3e0a78b [CELEBORN-1280] Change default value of
celeborn.worker.graceful.shutdown.recoverDbBackend to ROCKSDB
omit f294bb084 [CELEBORN-1391] Retry when MasterClient receiving a
RpcTimeoutException
omit 8dbe29df6 [CELEBORN-1384] Manually excluding workers should not depend
on whether the workers are alive
omit 1ebe13e62 [CELEBORN-1386] LevelDBProvider/RocksDBProvider should
create non-existent multi-level directory for LevelDB/RocksDB initialization
new b67e2389f [CELEBORN-1315] Manually close the RocksDB/LevelDB instance
when checkVersion throw Exception
new 0aa625ead [CELEBORN-1316] Override toString method for StoreVersion
new 657675b36 [CELEBORN-1386] LevelDBProvider/RocksDBProvider should
create non-existent multi-level directory for LevelDB/RocksDB initialization
new ed31df44d [CELEBORN-1384] Manually excluding workers should not depend
on whether the workers are alive
new 1672887f8 [CELEBORN-1391] Retry when MasterClient receiving a
RpcTimeoutException
new 52d1e08bd [CELEBORN-1280] Change default value of
celeborn.worker.graceful.shutdown.recoverDbBackend to ROCKSDB
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 (5c384f1a1)
\
N -- N -- N refs/heads/branch-0.4 (52d1e08bd)
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.
The 6 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
