Thank you folks! It was very helpful
Regards,
Nitan
Cell: 510 449 9629
> On Sep 20, 2019, at 8:04 PM, Jonathan Koppenhofer
> wrote:
>
> We do this without containers quite successfully. As precaution, we...
> - have dedicated disk per instance.
> - have lots of network bandwidth, but also
We do this without containers quite successfully. As precaution, we...
- have dedicated disk per instance.
- have lots of network bandwidth, but also throttle throughout defaults.
Also monitor network closely
- share CPU completely. Limit Cassandra settings to limit CPU use
(concurrent threads,
Hi Nitan,
You shouldn’t have any issues if you setup things properly.
Few possible issues could be (can become a bottleneck)
* CPU allocation (Instances can compete)
* Disk throughput & IOPS &
* Port allocations
* Network throughout
* Consistency issues.
And we have work around for all above,
I am looking for possible issues doing this setup without containers.
Regards,
Nitan
Cell: 510 449 9629
> On Sep 20, 2019, at 5:22 PM, Elliott Sims wrote:
>
> A container of some sort gives you better isolation and less risk of a
> mistake that could cause the instances to conflict in some
A container of some sort gives you better isolation and less risk of a
mistake that could cause the instances to conflict in some way. Might be
better for balancing resources between them as well, though using cgroups
directly can also accomplish that.
On Fri, Sep 20, 2019, 8:27 AM Nitan Kainth
Hi There,
Any feedback pros/cons for having multiple instances of C* on the same
machine without Docker/container solution?
The plan is to change the ports and run multiple C* processes, so we can
isolate two applications as two different clusters.
