This message was deleted.
# general
s
This message was deleted.
v
what is it that you are trying to do? Only one of the task replicas will commit to deep storage. so adding more replicas will double the reads but won’t double the ingestion throughput.
v
adding task replicas would increase Kinesis reads proportionally to the number of replicas you add
it only doubles if you double the replicas
j
Got it. Thanks 👍
@Vijay Narayanan I have 17 tasks for native kinesis ingestion, but am thinking of adding a replica for each task.
v
what is the reason for adding the replica?
if you are looking to boost ingestion throughput then the approach would be to increase number of tasks (and reshard kinesis if you already have 17 shards). Adding replicas will add fault tolerance but will not increase ingestion throughput
👍 1
r
fault tolerance + query throughput for the live segments
t
For query throughput increasing the processing.numThread also helps . Default is 2 , you could try increasing to 4 .
May I know what is the query pattern and concurrency.
j
Thank you all for your help. Follow question here if anyone knows.. would tranquility replication also double the reads of the kinesis stream? I know it would double the number of druid tasks, but not sure if that means tranquility would read the kinesis stream twice or the druid tasks are getting data from tranquility that has only read the kinesis stream once.
r
AFAIK, it will double the reads, at last on kafka that's the way it's
but that 'should' not be a problem, unless kinesis is priced based on that (that could be the case, given aws way of doing biz)
j
thanks Renato
however, here Rohit is saying that the read is only done once for tranquility:
Copy code
User decide the replication factor while using tranquility via a configuration.Tranquility will read the data once and will send the same data to multiple indexing tasks(equal to number of replication) hence ensuring that each replica gets exactly the same set of <http://data.In|data.In> case of realtime nodes ensuring all replicas get same set of data was not possible.
https://www.druidforum.org/t/doubts-regarding-replicaiton-policies-in-realtime-ndoes-and-tranquility/1767/2
r
hm, I don't know for sure if this feature was merged back into apache druid
for what I understand, tranquility acts as man(manager)-in-the-middle of the ingestion, so it manager it's own tasks and how they should publish, but I don't think this feature exists in the apache druid or imply