et us know your suggestions on how to debug this issue. Has anyone
experienced an issue like this before.(We had issues where one node starts
acting bad due to bad EBS volume I/O read and write time, but all nodes
experiencing an issue at same time is very peculiar)
Thank You,
Bill Walters.
. The bigger the element (UDT
in your case), the more memory it will requires on the coordinator side for
decoding / deserialization. Each UDT shouldn't exceed 64 KB size.
Thank You,
Bill Walters.
On Mon, Oct 30, 2017 at 3:52 AM, DuyHai Doan wrote:
> Hello Bill
>
> First if you do
would yield good performance. Since UDTs are frozen and
stored as BLOBs will there be any impediment while converting them after
read by coordinator.
If anyone has implemented a similar use-case, please let us know your
suggestions.
Thank You,
Bill Walters.
suggest if my strategies above will help in finding the
Inter DC latency or there are other ways I need to follow.
Thank You,
Bill Walters.
=rja&uact=8&ved=0ahUKEwj5hK2_58_WAhVmzFQKHUSiA4YQtwIIVTAD&url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dw3WbVMavy2I&usg=AOvVaw25xUCY2Jc7fGh7ngQF9ozt>
for
monitoring their cloud Cassandra clusters.
Please let me know if there are any cloud native monitoring systems that
work well with Cassandra, we will review it for our setup.
Thank You,
Bill Walters.
