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

[BUG] JindoMaster mount point did not recovered from pod migration. #3368

Open
SimonCqk opened this issue Jul 28, 2023 · 2 comments · May be fixed by #3383
Open

[BUG] JindoMaster mount point did not recovered from pod migration. #3368

SimonCqk opened this issue Jul 28, 2023 · 2 comments · May be fixed by #3383
Labels
bug Something isn't working

Comments

@SimonCqk
Copy link
Contributor

What is your environment(Kubernetes version, Fluid version, etc.)

kubernetes 1.22

Describe the bug

dataset controller executes jindo mount /xx oss://xxx command into jindomatser when DataSet object becomes ready for the first time, after that, jindo mount will never be triggered again, event jindo master pod was migrated/preempted from one node to another.

What you expect to happen:

Re-execute jindo mount command after jindo master recovered from migration or recreate.

How to reproduce it

  1. create DataSet and JindoRuntime, wait for them to be ready.
  2. simulate preemption or node healing by directly delete pod(jindo master).
  3. wait until jindo master becomes Running again and exec into the container to check mountpoint.

Additional Information

@SimonCqk SimonCqk added the bug Something isn't working label Jul 28, 2023
@TrafalgarZZZ
Copy link
Member

Maybe we can refer to #1322 for similar solution.

@SimonCqk
Copy link
Contributor Author

SimonCqk commented Aug 7, 2023

Maybe we can refer to #1322 for similar solution.

Yes it is, and it seems that master still corrupted when recreated or restarted with JindoRuntime, anyway, I'll open an PR soon to fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants