Hi Alexander,
thanks a lot for the pointers, I checked the mentioned issue.
While the reported issue seems to match our problem it only occurs reads
and not for writes (according to the Datastax Jira). But we experience
downtimes for writes and reads.
Which version of the Datastax Driver
Hi Daniel,
it seems like the driver isn't detecting that the node went down, which is
probably due to the way the node is being killed.
If I remember correctly, in some cases Netty transport is still up in the
client, which will still allows to send queries without them answering back
:
Hi Sean,
thanks for your comments, find below some more details with respect to
the (1) VM sizing and (2) the replication factor:
(1) VM sizing:
We selected the small VMs as intial setup to run our experiments. We
have also executed the same experiments (5 nodes) on larger VMs with 6
cores
