Skip to content

Allow parallel operations on different volumes #136

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

Closed
msau42 opened this issue Oct 23, 2018 · 4 comments
Closed

Allow parallel operations on different volumes #136

msau42 opened this issue Oct 23, 2018 · 4 comments
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.
Milestone

Comments

@msau42
Copy link
Contributor

msau42 commented Oct 23, 2018

We put global locks on mount operations (I didn't check about attach/detach). This limits the driver from only executing one mount at a time. We should allow mounts to happen in parallel if they're on different volumes.

@davidz627 davidz627 added this to the GA milestone Oct 23, 2018
@msau42
Copy link
Contributor Author

msau42 commented Apr 11, 2019

/help
/kind bug

@k8s-ci-robot
Copy link
Contributor

@msau42:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help
/kind bug

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 kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Apr 11, 2019
@hantaowang
Copy link

See PR #302 and #303.

After scale testing on a single node, there is reason to believe that much of the delay comes from not actually NodePublishVolume/NodeStageVolume but actually from the Attaching side. Pod events show constant RPC context DeadlineExceeded errors, Attachment timeout errors, and Internal errors (stemming from an error from googleapi regarding too many pending operations on the same resource). All of this causes a backoff loop for retrying.

I've also observed some timeouts on the kubelet side due to WaitForAttach taking too long, which also cause backoffs.

@davidz627
Copy link
Contributor

resolved by #303

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

4 participants