Regarding the random killing test, I has already simulated the following exception for testing:
1. master node exception: One or two master nodes have an abnormality and hang up for half a minute each time. 2. worker node exception: One or two worker nodes will hang for half a minute each time. 3. disk corruption: Randomly select a worker and test one disk and two disks. All disks are unwritable. 4. disk io hang: Randomly select a worker, test one disk, two disks, and io hang on all disks. 5. master metadata exception: Randomly select one or two of master nodes to test the ratis meta corruption. The method of results verification is that running a query that will last for several minutes, which query runs successfully in most cases and failure is allowed under certain circumstances. To summarize, I've tested with the following exception behavior: 1. Kill the master process[PASSED] 2. Kill the worker process[PASSED] 3. The worker directory is not writable[PASSED] 4. worker disk io hang[PASSED] 5. High CPU load[PASSED] 6. Delete ratis metadata of master node[PASSED] Meanwhile, the resource statuses of master and worker are as expected. +1 for the random killing test. Regards, Nicholas Jiang At 2024-05-21 05:05:17, "Mridul Muralidharan" <[email protected]> wrote: >+1 > >Signatures, digests, etc check out fine. >Checked out tag and build/tested with "-Pspark3.1" > >Regards, >Mridul > > >On Sun, May 19, 2024 at 10:19 PM rexxiong <[email protected]> wrote: > >> +1 (binding) >> I checked >> - Download links are valid. >> - git commit hash is correct >> - Checksums and signatures are valid. >> - No binary files in the source release >> - Successfully built the binary from the source on MacOs with Command: >> ./build/make-distribution.sh -Pspark-3.3 >> >> I also tested compatibility with version 0.4.0 by upgrading the >> master/worker from 0.4.0 to 0.4.1. Using a 0.4.0 client to access the 0.4.1 >> master/worker, everything worked well. >> >> Thanks, >> Jiashu Xiong >> >> Yihe Li <[email protected]> 于2024年5月17日周五 18:47写道： >> >> > +1 (non-binding) >> > I checked the following things: >> > - git commit hash is correct. >> > - download links are valid. >> > - release files are in correct location. >> > - signatures and checksums are good. >> > - LICENSE and NOTICE files exist. >> > - build success from source code(ubuntu 16.04). >> > ``` >> > ./build/make-distribution.sh --sbt-enabled -Pspark-3.3 >> > ``` >> > >> > Thanks, >> > Yihe Li >> > >> > On 2024/05/17 01:53:48 angers zhu wrote: >> > > +1 >> > > >> > > - Checked license >> > > - checked doc >> > > - checked build from source with spark-32 >> > > >> > > Nicholas Jiang <[email protected]> 于2024年5月14日周二 12:13写道： >> > > >> > > > Hi Celeborn community, >> > > > >> > > > This is a call for a vote to release Apache Celeborn >> > > > >> > > > 0.4.1-rc1 >> > > > >> > > > >> > > > The git tag to be voted upon: >> > > > >> > > > https://github.com/apache/celeborn/releases/tag/v0.4.1-rc1 >> > > > >> > > > The git commit hash: >> > > > 641180142c5ef36430a6afcd702c9487a6007458 source and binary artifacts >> > can be >> > > > found at: >> > > > >> > > > https://dist.apache.org/repos/dist/dev/celeborn/v0.4.1-rc1 >> > > > >> > > > The staging repo: >> > > > >> > > > >> > >> https://repository.apache.org/content/repositories/orgapacheceleborn-1055 >> > > > >> > > > >> > > > Fingerprint of the PGP key release artifacts are signed with: >> > > > D73CADC1DAB63BD3C770BB6D9476842D24B7C885 >> > > > >> > > > My public key to verify signatures can be found in: >> > > > >> > > > https://dist.apache.org/repos/dist/release/celeborn/KEYS >> > > > >> > > > The vote will be open for at least 72 hours or until the necessary >> > > > number of votes are reached. >> > > > >> > > > Please vote accordingly: >> > > > >> > > > [ ] +1 approve >> > > > [ ] +0 no opinion >> > > > [ ] -1 disapprove (and the reason) >> > > > >> > > > Steps to validate the release: >> > > > >> > > > https://www.apache.org/info/verification.html >> > > > >> > > > * Download links, checksums and PGP signatures are valid. >> > > > * Source code distributions have correct names matching the current >> > > > release. >> > > > * LICENSE and NOTICE files are correct. >> > > > * All files have license headers if necessary. >> > > > * No unlicensed compiled archives bundled in source archive. >> > > > * The source tarball matches the git tag. >> > > > * Build from source is successful. >> > > > >> > > > Regards, >> > > > Nicholas Jiang >> > > >> > >>
