Tools / Apache HertzBeat Interview Questions
Explain the lifecycle of a collection job in a collector cluster?
A job's lifecycle spans creation, ongoing execution, and possible reassignment, all coordinated by the manager rather than the collector deciding anything on its own.
flowchart TD
A[Job created when monitor is saved] --> B[Manager assigns job via consistent hashing]
B --> C[Collector executes job on its interval]
C --> D{Collector still healthy?}
D -- Yes --> C
D -- No --> E[Manager reassigns job to another collector]
E --> C
Each cycle, the assigned collector re-executes the same protocol call and reports results; nothing about the job itself changes between cycles unless the monitor's configuration is edited. If the owning collector fails, the manager's heartbeat tracking detects it and reassigns the job, so the job's identity persists across collector changes — only its execution location moves.
A collection job is first created when:
If the owning collector fails, the job's identity:
More Related questions...
