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

2.07: restaring one master caused fatal error on FUSE mount #1589

Closed
onlyjob opened this issue Nov 1, 2020 · 3 comments
Closed

2.07: restaring one master caused fatal error on FUSE mount #1589

onlyjob opened this issue Nov 1, 2020 · 3 comments

Comments

@onlyjob
Copy link

onlyjob commented Nov 1, 2020

During restart of one master out of three, application using a FUSE mount failed with the following error: statvfs arror (EIO (Input/output error)). As mentioned earlier (in other tickets), FUSE client should wait and retry instead of immediately fail an operation. This is crucial for resiliency to network errors and normal maintenance operations such as restarting 1/3 masters which should not cause any errors.
@chrislusf
Copy link
Collaborator

Added retries to all grpc operations.

@onlyjob
Copy link
Author

onlyjob commented Nov 1, 2020

Thank you. Will test shortly. Would it work as per -readRetryTime?

@chrislusf
Copy link
Collaborator

Would it work as per -readRetryTime?

Yes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@onlyjob @chrislusf