This message was deleted.
# troubleshooting
s
This message was deleted.
g
what do you mean by "segment merge wait time"?
r
we have data in S3. When we query in druid, segments gets loaded from there to disk and from disk to memory right, if i am not wrong? We want to reduce the time to fetch while querying the data in terms of that. we are using i3.4x nodes(30). wanted to check if there are few druid config properties that can be tweaked to achieve better performance.
k
@Rohit Segments are fetched from s3 when the historicals are coming up not at query time
So are you trying to optimize on query time or starting the historical faster
r
i want to optmize on query time
k
Please share the query. The segment shard spec and the number of segments
What do you think is getting bottlenecked
r
@Karan Kumar sorry for late response, as i was out for few days. single segment for an hour, 3 replicas, total segment for a datasource - ~10k . these are select queries with zeroFilledTopN or groupby
k
Can you please share the metrics underneath the graph ? https://druid.apache.org/docs/latest/operations/metrics.html#historical https://druid.apache.org/docs/latest/operations/metrics.html#historical-1 It would be present from the above list