Skip to content

add note on consistency of results for sys.segments queries #7034

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.

Sign up for GitHub

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

Merged
jihoonson merged 7 commits into from
Feb 19, 2019
Merged

add note on consistency of results for sys.segments queries #7034

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
b1e3455
add doc
Feb 7, 2019
9672aea
change docs
Feb 8, 2019
0a71937
Merge branch 'master' of github.com:druid-io/druid into sys-segments-…
Feb 8, 2019
2cdbb1d
PR comments
Feb 14, 2019
9b42012
Merge branch 'master' of github.com:druid-io/druid into sys-segments-…
Feb 14, 2019
bb55eb9
few more changes
Feb 14, 2019
0154bd2
Merge branch 'master' of github.com:druid-io/druid into sys-segments-…
Feb 14, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/content/querying/sql.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -571,6 +571,8 @@ The "sys" schema provides visibility into Druid segments, servers and tasks.
### SEGMENTS table
Segments table provides details on all Druid segments, whether they are published yet or not.

#### CAVEAT
Note that a segment can be served by more than one stream ingestion tasks or Historical processes, in that case it would have multiple replicas. These replicas are weakly consistent with each other when served by multiple ingestion tasks, until a segment is eventually served by a Historical, at that point the segment is immutable. Broker prefers to query a segment from Historical over an ingestion task. But if a segment has multiple realtime replicas, for eg. kafka index tasks, and one task is slower than other, then the sys.segments query results can vary for the duration of the tasks because only one of the ingestion tasks is queried by the Broker and it is not gauranteed that the same task gets picked everytime. The `num_rows` column of segments table can have inconsistent values during this period. There is an open [issue](https://github.com/apache/incubator-druid/issues/5915) about this inconsistency with stream ingestion tasks.

|Column|Notes|
|------|-----|
Expand Down