Search before asking
Fluss version
main (development)
Please describe the bug 馃悶
FlussAuthorizationITCase.testAddServerTag adds the PERMANENT_OFFLINE tag to tablet server 0 and starts removing it during cleanup, but does not wait for the returned future.
The next test can therefore create its default replication-factor-3 table while the coordinator still considers only two tablet servers available. This causes InvalidReplicationFactorException: Replication factor: 3 larger than available tablet servers: 2 and may fail several subsequent test setups.
Solution
Wait for removeServerTag(...) to complete before testAddServerTag returns, ensuring the cluster state is restored before the next test starts.
Are you willing to submit a PR?
Search before asking
Fluss version
main (development)
Please describe the bug 馃悶
FlussAuthorizationITCase.testAddServerTagadds thePERMANENT_OFFLINEtag to tablet server 0 and starts removing it during cleanup, but does not wait for the returned future.The next test can therefore create its default replication-factor-3 table while the coordinator still considers only two tablet servers available. This causes
InvalidReplicationFactorException: Replication factor: 3 larger than available tablet servers: 2and may fail several subsequent test setups.Solution
Wait for
removeServerTag(...)to complete beforetestAddServerTagreturns, ensuring the cluster state is restored before the next test starts.Are you willing to submit a PR?