![]() ![]() sending user-provided data from coordinators to replicas.That’s all very cool, but ScyllaDB is much more than its client-server protocol! Nodes also need to communicate with each other to fulfill various tasks. ![]() Only CQL requests and their results are shown – other types (auth, events, etc.) are not visible With the “cql” filter, only CQL packets are shownįilters can also limit the output to specific packets we’re interested in, e.g. In order to examine CQL packets, simply use a “cql” filter in Wireshark: With Wireshark, it’s possible to dissect the communication between ScyllaDB nodes and their clients – both via the legacy Thrift protocol and the current standard, CQL ( for which we contributed as well!). However, instead of examining raw bytes that happened to go through our network interfaces, it’s useful to get them parsed to a human-readable form first – assuming we know which protocols were used. It’s extremely valuable to be able to see which nodes communicated with each other, which requests arrived from the clients at which time, and more. Using a packet dissector to investigate issues in distributed systems is a great asset. This includes reading and writing rows, exchanging schema information, gossiping and repairs. From now on, it’s also possible to dissect ScyllaDB’s internal protocol, used to communicate between nodes. One of such tools is Wireshark, a well known utility that offers snooping on all kinds of network protocols – ranging from Ethernet to HTTP and beyond. Investigating problems in a distributed system may be a tedious task, but it becomes much easier with the right tools for the job. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |