mcs: async evict-leader-scheduler config in api server #7388
Labels
Comments
|
It appears that there is a synchronization discrepancy between the API server and the scheduling server regarding the paused state of the store. During testing, we observed that the scheduling server reflects store 2 as being paused, whereas the API server indicates that store 3 is paused. This misalignment may be attributed to a lack of initial configuration and cleanup, which has led to an inconsistency in the in-memory representation of the store's state on the API server when compared to the persisted configuration. |
|
Is it duplicated with #7257? |
ti-chi-bot bot
added a commit
that referenced
this issue
Nov 20, 2023
close #7388 Signed-off-by: lhy1024 <admin@liudos.us> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
rleungx
pushed a commit
to rleungx/pd
that referenced
this issue
Dec 1, 2023
close tikv#7388 Signed-off-by: lhy1024 <admin@liudos.us> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
What did you do?
add evict leader scheduler config and check it
What did you expect to see?
It is synced
What did you see instead?
It is async between memory and persist config in api server.
Of course, because scheduling server is sync with persist config, so the memory data in api server is different from scheduling server
What version of PD are you using (
pd-server -V)?The text was updated successfully, but these errors were encountered: