-
Notifications
You must be signed in to change notification settings - Fork 38
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
control port must be opened and handled on start #2585
Labels
Milestone
Comments
roman-khimov
added
enhancement
Improving existing functionality
good first issue
Good for newcomers
and removed
triage
labels
Sep 18, 2023
moreover, program must not start in case of control port opening failure |
Do we want to provide a separate control status for every operation (e.g. "starting service X") instead of generic "starting", "ready"? |
Yes. We have very distinct states especially wrt integrated CN. |
AliceInHunterland
added a commit
that referenced
this issue
Nov 14, 2023
Control ports should be initialised and start served first of all. Closes: #2585. Signed-off-by: Ekaterina Pavlova <[email protected]>
AliceInHunterland
added a commit
that referenced
this issue
Nov 14, 2023
Control ports should be initialised and start served first of all. Closes: #2585. Signed-off-by: Ekaterina Pavlova <[email protected]>
AliceInHunterland
added a commit
that referenced
this issue
Nov 16, 2023
Control ports should be initialised and start served first of all. As initControlService already listening endpoint, no need of preRun of control service. Closes: #2585. Signed-off-by: Ekaterina Pavlova <[email protected]>
AliceInHunterland
added a commit
that referenced
this issue
Nov 16, 2023
Control ports should be initialised and start served first of all. As initControlService already listening endpoint, no need of preRun of control service in storage nodes. Closes: #2585. Signed-off-by: Ekaterina Pavlova <[email protected]>
AliceInHunterland
added a commit
that referenced
this issue
Nov 17, 2023
Control ports should be initialised and start served first of all. As initControlService already listening endpoint, no need of preRun of control service in storage nodes. Closes: #2585. Signed-off-by: Ekaterina Pavlova <[email protected]>
AliceInHunterland
added a commit
that referenced
this issue
Nov 20, 2023
Control ports should be initialised and start served first of all. The priority of running control service is maximized for both SN and IR. Closes: #2585. Signed-off-by: Ekaterina Pavlova <[email protected]>
roman-khimov
added a commit
that referenced
this issue
Nov 20, 2023
not fixed
log:
|
Should be fixed with #2679. |
roman-khimov
added a commit
that referenced
this issue
Dec 18, 2023
Sync may take some time while nothing stops IR from showing some useful info. Closes #2585.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
The same as #2428 but for control port.
The text was updated successfully, but these errors were encountered: