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

[data ingestion] migrate analytics to data ingestion framework #17731

Merged
merged 1 commit into from
May 22, 2024

Conversation

phoenix-o
Copy link
Contributor

No description provided.

Copy link

vercel bot commented May 14, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
sui-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 20, 2024 2:11pm

Copy link

vercel bot commented May 14, 2024

@phoenix-o is attempting to deploy a commit to the Mysten Labs Team on Vercel.

A member of the Team first needs to authorize it.

self.update_to_next_epoch(epoch);
self.create_epoch_dirs()?;
self.reset()?;
let mut state = self.state.lock().await;
Copy link
Contributor

Choose a reason for hiding this comment

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

just curious: why does the state need to be locked if it can only be processed one at a time

Copy link
Contributor Author

Choose a reason for hiding this comment

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

so although this specific case has a concurrency of 1, the framework doesn't make exceptions and requires workers to be thread-safe. So they could be canceled, cloned, and rescheduled in another thread. We do the same for the archival workflow

@phoenix-o phoenix-o merged commit e6c65fc into MystenLabs:main May 22, 2024
42 of 45 checks passed
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

Successfully merging this pull request may close these issues.

None yet

2 participants