replication mode: tune persist file timeout

[disksing]

Issue Number: Fix #6672

What is changed and how does it work?

change persist file timeout from 10s to 3s to speed up state change

Check List

Tests

• Unit test

Related changes

• Need to cherry-pick to the release branch

Release note

None.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• nolouch

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.56%. Comparing base (ec99986) to head (d4479a9).
Report is 875 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6669      +/-   ##
==========================================
- Coverage   74.65%   74.56%   -0.09%     
==========================================
  Files         417      417              
  Lines       43278    43278              
==========================================
- Hits        32309    32271      -38     
- Misses       8100     8134      +34     
- Partials     2869     2873       +4     

Flag	Coverage Δ
unittests	74.56% <ø> (-0.09%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[disksing]

/merge

[ti-chi-bot]

@disksing: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: d4479a9

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #8774.