Hello,
Not so long ago, without any doing of our own we started observing an increased
amount of dropped read messages and we can't find an explanation for it,
perhaps you'll have some ideas where to look to try and decipher this.
C* cluster: 7 DCs (5 of them with 18 nodes and 2 with 60)
C* ver
bGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Ba%2FIbybyy2p%2FsreGLBCxBedwl7mkgyBpy6%2BOPJWPcL8%3D&reserved=0>
Making it easier for everyone to experience the world since 1996
43 languages, 214+ offices worldwide, 141,000+ global destinations, 29
guages, 214+ offices worldwide, 141,000+ global destinations, 29 million
reported listings
Subsidiary of Booking Holdings Inc. (NASDAQ: BKNG)
On Wed, Oct 28, 2020 at 8:58 AM Gediminas Blazys
mailto:gediminas.bla...@microsoft.com.invalid>>
wrote:
Hello,
I wanted to seek out your opinion and
Hello,
I wanted to seek out your opinion and experience.
Has anyone of you had a chance to run a Cassandra cluster of more than 350
nodes?
What are the major configuration considerations that you had to focus on? What
number of vnodes did you use?
Once the cluster was up and running what would
hen that error occurs. To
determine the node you can look for this driver log message: "Connection
established to [NODE_ADDRESS] using protocol version [VERSION]."
It should be easier to reproduce the issue with the results of those queries.
Thanks,
João Reis
Ged
72f988bf86f141af91ab2d7cd011db47%7C0%7C0%7C637244653454584013&sdata=%2B9ojISBaiyNt%2Fvlyat2wOCgDbFJIyXjmjuYMhPCB4YU%3D&reserved=0>
Gediminas Blazys
mailto:gediminas.bla...@microsoft.com.invalid>>
escreveu no dia segunda, 4/05/2020 à(s) 11:13:
Hello again,
Looking into system.pee
preferred_ip
rack
release_version
rpc_address
schema_version
tokens
null
null
192.168.104.111
null
null
null
null
null
Have a wonderful day 😊
Gediminas
From: Gediminas Blazys
Sent: Monday, May 4, 2020 10:09
To: user
tact point to
see if all the node list / token info is expected. You can compare it to
nodetool ring info.
Not directly related: 256 vnodes is probably more than you want.
Thanks,
Jorge
On Thu, Apr 30, 2020 at 9:48 AM Gediminas Blazys
mailto:gediminas.bla...@microsoft.com.invalid>>
wro
Hello,
We have run into a very interesting issue and maybe some of you have
encountered it or just have an idea where to look.
We are working towards adding new dcs into our cluster, here's the current
topology:
DC1 - 18 nodes
DC2 - 18 nodes
DC3 - 18 nodes
DC4 - 18 nodes
DC5 - 18 nodes
Recentl