Priority for evaluation rules
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
I am wondering what is the priority for the evaluation rules as defined in the [wiki](https://github.com/linkedin/Burrow/wiki/Consumer-Lag-Evaluation-Rules#evaluation-rules). They are in a numbered order so does that mean they are in descending priority?
The main reason I ask is because of evaluation rules 1 and 4. We've had a few instances recently in which at least one consumer stopped committing for nearly 20 mins, but burrow had marked it as `OK`. I believe during the stored window in burrow, there was at least one recorded offset in which the lag was 0. My hunch was that because of rule 1, it didn't apply rule 4, but I wanted to confirm that here. For reference, in burrow we had `intervals=30` and `min-distance=10`, and the consumer which had stopped was processing quite frequently before, so the window should have been exactly 5 minutes.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked Consumer Lag Evaluation Rules wiki section, focusing on rules 1 and 4 and the intervals=30 and min-distance=10 settings. Confirm whether numbered rules have descending priority and whether the described zero-lag window explains the OK result; done means the priority and behavior are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- stream-processing
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100