Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

enhance: avoid the coexistence of the old coordinator and the new node/proxy #35720

Merged

Conversation

weiliu1031
Copy link
Contributor

issue: #35719
In standalone mode, block the start process until the new coordinator is active to avoid the coexistence of the old coordinator and the new node/proxy
1. In the start/restart process, the new coordinator will become active immediately and will not be blocked
2. In the rolling upgrade process, the new coordinator will not be active until the old coordinator is down, and it will be blocked

@sre-ci-robot sre-ci-robot added the size/S Denotes a PR that changes 10-29 lines. label Aug 27, 2024
@weiliu1031 weiliu1031 force-pushed the block_standalone_start_progress branch from 7bd2f31 to 5dc32bc Compare August 27, 2024 06:28
@weiliu1031
Copy link
Contributor Author

/run-cpu-e2e

@mergify mergify bot added dco-passed DCO check passed. kind/enhancement Issues or changes related to enhancement labels Aug 27, 2024
Copy link
Contributor

mergify bot commented Aug 27, 2024

@weiliu1031 E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@weiliu1031 weiliu1031 force-pushed the block_standalone_start_progress branch from 5dc32bc to 36edb6e Compare August 27, 2024 13:21
Copy link
Contributor

mergify bot commented Aug 27, 2024

@weiliu1031 E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

Copy link

codecov bot commented Aug 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.66%. Comparing base (56b3490) to head (4367a7e).
Report is 14 commits behind head on master.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #35720      +/-   ##
==========================================
+ Coverage   81.32%   84.66%   +3.34%     
==========================================
  Files        1238      960     -278     
  Lines      148082   123447   -24635     
==========================================
- Hits       120425   104516   -15909     
+ Misses      22887    14154    -8733     
- Partials     4770     4777       +7     

see 302 files with indirect coverage changes

…e/proxy

In standalone mode, block the start process until the new coordinator is active to avoid the coexistence of the old coordinator and the new node/proxy
    1. In the start/restart process, the new coordinator will become active immediately and will not be blocked
    2. In the rolling upgrade process, the new coordinator will not be active until the old coordinator is down, and it will be blocked

Signed-off-by: Wei Liu <wei.liu@zilliz.com>
@weiliu1031 weiliu1031 force-pushed the block_standalone_start_progress branch from 36edb6e to 4367a7e Compare August 28, 2024 09:16
Copy link
Contributor

mergify bot commented Aug 28, 2024

@weiliu1031 E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@xiaofan-luan
Copy link
Contributor

/lgtm
/approve

@sre-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: weiliu1031, xiaofan-luan

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

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

sre-ci-robot pushed a commit that referenced this pull request Aug 29, 2024
…e/proxy (#35760)

issue: #35719
pr: #35720 
In standalone mode, block the start process until the new coordinator is
active to avoid the coexistence of the old coordinator and the new
node/proxy
1. In the start/restart process, the new coordinator will become active
immediately and will not be blocked
2. In the rolling upgrade process, the new coordinator will not be
active until the old coordinator is down, and it will be blocked

Signed-off-by: Wei Liu <wei.liu@zilliz.com>
@weiliu1031
Copy link
Contributor Author

/run-cpu-e2e

Copy link
Contributor

mergify bot commented Aug 29, 2024

@weiliu1031 E2e jenkins job failed, comment /run-cpu-e2e can trigger the job again.

@weiliu1031
Copy link
Contributor Author

/run-cpu-e2e

@mergify mergify bot added the ci-passed label Aug 29, 2024
@sre-ci-robot sre-ci-robot merged commit 73be0ba into milvus-io:master Aug 29, 2024
15 of 16 checks passed
weiliu1031 added a commit to weiliu1031/milvus that referenced this pull request Sep 9, 2024
weiliu1031 added a commit to weiliu1031/milvus that referenced this pull request Sep 9, 2024
weiliu1031 added a commit to weiliu1031/milvus that referenced this pull request Sep 9, 2024
…d the new node/proxy (milvus-io#35720)"

This reverts commit 73be0ba.

Signed-off-by: Wei Liu <wei.liu@zilliz.com>
sre-ci-robot pushed a commit that referenced this pull request Sep 10, 2024
…d the new node/proxy (#35720)" (#36113)

issue: #36100
This reverts commit 73be0ba.

Signed-off-by: Wei Liu <wei.liu@zilliz.com>
chyezh pushed a commit to chyezh/milvus that referenced this pull request Sep 11, 2024
…d the new node/proxy (milvus-io#35720)" (milvus-io#36113)

issue: milvus-io#36100
This reverts commit 73be0ba.

Signed-off-by: Wei Liu <wei.liu@zilliz.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved ci-passed dco-passed DCO check passed. kind/enhancement Issues or changes related to enhancement lgtm size/S Denotes a PR that changes 10-29 lines.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants