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

Sync state #47

Open
jogomu opened this issue Sep 20, 2022 · 2 comments
Open

Sync state #47

jogomu opened this issue Sep 20, 2022 · 2 comments

Comments

@jogomu
Copy link

jogomu commented Sep 20, 2022

Is there an easy way to know (e.g. from log entry) whether mobius3 is in an idle state where there is no pending or ongoing work? I.e. to check whether mobius3 thinks everything is sync'd ?

@michalc
Copy link
Member

michalc commented Nov 12, 2022

Hi @jogomu,

Not really in any particularly clear way I think. What would be the ideal thing for mobius3 to do from your point of view? (I've thought about this before but not really come to any good conclusion...)

Thanks,

Michal

@jgm-ktg
Copy link

jgm-ktg commented Dec 8, 2022

Just a message to stdout/stderr periodically would be fine (it can be redirected to a log that a user can tail or whatever they want). A message indicating that sync is both healthy and up-to-date, perhaps with a timestamp about when this state was noticed. If such a message is logged periodically the the user would have confidence that things are working. The health check should be based on having actually re-fetched the local and s3 metadata for a fresh comparison. As I said in the other open ticket, mobius3 has "silently failed" for me before where it stops syncing and logging but there is no way to know that this happened other for not seeing the changes propagate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants