Recover real-time consumption when consuming segment stuck
See original GitHub issueOne possible solution is to manually delete the consuming segment and let the controller create a new one during real-time segment validation. But this scenario is not covered in the PinotLLCRealtimeSegmentManager.ensureAllPartitionsConsuming()
yet.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Recover real-time consumption when consuming segment stuck
One possible solution is to manually delete the consuming segment and let the controller create a new one during real-time segment ...
Read more >Ingestion FAQ - Apache Pinot Docs
How to reset a CONSUMING segment stuck on an offset which has expired from the stream? This typically happens if. 1. The consumer...
Read more >Data Loss: Causes, Effects & Prevention Methods
Data loss is a serious problem for businesses of all sizes— losing files means losing time and money to restore or recover information...
Read more >Recovering From Stuck Failovers - Documentation – Commvault
Caution: Use extreme caution while forcing a failover to a standby CommServe host. Data loss can be experienced with this process as the...
Read more >Advocates Say Providing Addicts with 'Safe Consumption ...
Advocates Say Providing Addicts with 'Safe Consumption Spaces' Could Reduce Overdose Deaths in the City. By Natalie Duddridge The Bronx.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Another way is to manually set the consuning segment to be in OFFLINE state (if it s not already so).
@sajjad-moradi Yes, I think the pause/resume can be used to address all 3 cases mentioned above. Thanks for adding the great feature!