Hello,
just as a small addition: The numbers also depend on your consistency level
used for reads. It will behave like that if you just read on local nodes.
If you do reads on ALL, QUORUM or EACH_QUORUM etc. you need also include
the read volume in the calculation.
Regards,
Georg
Am Mi., 15. Ja
Thank you. I have an insight now.
Regards,
Osman
On Wed, 15 Jan 2020 at 19:18, Reid Pinchback wrote:
>
> Oh, duh. Revise that. I was forgetting that multi-dc writes are sent to a
> single node in the other dc and tagged to be forwarded to other nodes within
> the dc.
>
> So your quick-and-di
Oh, duh. Revise that. I was forgetting that multi-dc writes are sent to a
single node in the other dc and tagged to be forwarded to other nodes within
the dc.
So your quick-and-dirty estimate would be more like (write volume) x 2 to leave
headroom for random other mechanics.
R
On 1/15/20,
I would think that it would be largely driven by the replication factor. It
isn't that the sstables are forklifted from one dc to another, it's just that
the writes being made to the memtables are also shipped around by the
coordinator nodes as the writes happen. Operations at the sstable leve
Hello,
Is there any way to calculate inter dc bandwidth requirements for
proper operation?
I can't find any info about this subject.
Can we say, how much sstable collected at one dc has to be transferred to other?
I can calculate bandwidth with generated sstable then.
I have twcs with one hour win
