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: ingestions fail to take place after sync failure #999

Open
de-sh opened this issue Nov 21, 2024 · 1 comment
Open

bug: ingestions fail to take place after sync failure #999

de-sh opened this issue Nov 21, 2024 · 1 comment
Assignees

Comments

@de-sh
Copy link
Contributor

de-sh commented Nov 21, 2024

/about output:
v1.6, distributed mode

Description:

Ingestion API returns 200, but events aren't in s3. Logs show retries reaching limit(5):

2024-11-18T18:13:43Z WARN  parseable::sync] failed to sync local data with object store. ConnectionError(UnhandledError(Reqwest { retries: 5, max_retries: 5, elapsed: 6.842013835s, retry_timeout: 30s, source: reqwest::Error { kind: Status(500), url: ".../date%3D2024-11-15/ingestor.8677e4a099f5a08.manifest.json" } }))
@nitisht
Copy link
Member

nitisht commented Jan 12, 2025

As we discussed, we'll add detailed warning about how to notify users if sync is getting delayed and there is a arrow to parquet conversion lag due to high CPU usage.

@nitisht nitisht closed this as completed Jan 12, 2025
@nitisht nitisht reopened this Jan 12, 2025
@nitisht nitisht removed the bug label Jan 26, 2025
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