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.

Sign up for GitHub

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

Jump to bottom

orchestration timeout for osds is too aggressive #125

Closed
travisn opened this issue Oct 28, 2016 · 1 comment
Closed

orchestration timeout for osds is too aggressive #125

travisn opened this issue Oct 28, 2016 · 1 comment
Assignees
@travisn
Milestone
initial public pr...

Comments

@travisn
Copy link
Member

travisn commented Oct 28, 2016

The timeout for the orchestration leader is two minutes when waiting for a node to respond. If a node has many disks on which to configure osds, it will take longer than this timeout and fail the orchestration even though the osds will still succeed.

A simple way to extend the timeout is a type of heartbeat after each osd is configured. This will signal to the leader that the node is still working and the timeout can be reset.
@travisn travisn self-assigned this Oct 28, 2016
@travisn travisn added this to the initial public release milestone Oct 28, 2016
@travisn
Copy link
Member Author

travisn commented Nov 3, 2016

This is a non-issue with the fix for #132

@travisn travisn closed this as completed Nov 3, 2016
thotz pushed a commit to thotz/rook that referenced this issue Jun 5, 2020
@jeffvance
Merge pull request rook#125 from yard-turkey/status
2e8a139 
pr 122: lost a commit
agarwal-mudit pushed a commit to agarwal-mudit/rook that referenced this issue Sep 29, 2020
@travisn
Merge pull request rook#125 from travisn/backport-mon-pv-cleanup
41d4236 
Bug 1873118: Backport mon pv cleanup
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@travisn travisn

Labels
None yet
Projects
None yet
Milestone
initial public preview
Development

No branches or pull requests
1 participant
@travisn