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

Unmount corrupted folder is case nodeserver restarted #15191

Merged
merged 1 commit into from
Mar 29, 2022

Conversation

Binyang2014
Copy link
Contributor

@Binyang2014 Binyang2014 commented Mar 23, 2022

What changes are proposed in this pull request?

Unmount corrupted folder is case csi-nodeserver restarted

Related to issue #14917

This change just mitigate the issue. If node-server restated, it will try to remount the folder. But user job still can not access data during restarting period.

Just notice these is another solution for this issue #15165. Believe this solution is more robustness and better for critical job. But this solution need more efforts to be mutual for production workload. Maybe at this stage, we can keep the both.

Notice: this change requires k8s version above 1.18
This change not tested yet, we need to kill the nodeserver. After it restarted, check if the mount path is remounted

@alluxio-bot
Copy link
Contributor

Automated checks report:

  • Commits associated with Github account: PASS
  • PR title follows the conventions: FAIL
    • The title of the PR does not pass all the checks. Please fix the following issues:
      • First word of title ("Umount") is not an imperative verb. Please use one of the valid words

Some checks failed. Please fix the reported issues and reply 'alluxio-bot, check this please' to re-run checks.

@Binyang2014 Binyang2014 changed the title Umount corrupted folder is case nodeserver restarted Unmount corrupted folder is case nodeserver restarted Mar 23, 2022
@alluxio-bot
Copy link
Contributor

Automated checks report:

  • Commits associated with Github account: PASS
  • PR title follows the conventions: PASS

All checks passed!

@HelloHorizon HelloHorizon requested a review from ssz1997 March 23, 2022 17:56
@HelloHorizon HelloHorizon added the area-k8s Alluxio Kubernetes Integration label Mar 23, 2022
Copy link
Contributor

@ssz1997 ssz1997 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks for adding this.

@HelloHorizon
Copy link
Contributor

Thanks @Binyang2014 !

@HelloHorizon
Copy link
Contributor

alluxio-bot, merge this please

@alluxio-bot alluxio-bot merged commit d1d0628 into Alluxio:master Mar 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-k8s Alluxio Kubernetes Integration
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants