Re: Does Java driver v3.1.x degrade cluster connect/close performance?

Hi Matija, Andrew Thank you for your reply. Matija: > Do you plan to misuse it and create a new cluster object and open a new connection for each request? No, My app never create a new cluster for each request. Meanwhile its each unit tests creates a new cluster and close it every time. Of

Changed node ID?

I have a 9 node cluster I had shut down (cassandra stopped on all nodes, all nodes shutdown) that I just tried to start back up. I have done this several times successfully. However, on this attempt, one of the nodes failed to join the cluster. Upon inspection of /var/log/cassandra/system.log,

Is it possible to recover a deleted-in-future record?

Hi, all, We recently encountered an issue in production that some records were mysteriously deleted with a timestamp 100+ years from now. Everything is normal as of now, and how the deletion happened and accuracy of system timestamp at that moment are unknown. We were wondering if there is a

Re: Attached profiled data but need help understanding it

Hi Kant, You'll find more information about ixgbevf here  http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/sriov-networking.htmlI repeat myself but don't underestimate VMs placement: same AZ? same placement group? etc.Note that LWT are not discouraged but as the doc says: "[...] reserve

Re: Does Java driver v3.1.x degrade cluster connect/close performance?

One correction on my previous email, at 2.1.8 of the driver, Netty 4.0 was in use, so please disregard my comments about the netty dependency changing from 3.9 to 4.0, there is a different in version, but it's only at the patch level (4.0.27 to 4.0.37) Just to double check, I reran that

Re: Any way to control/limit off-heap memory?

Thanks Hannu - also considered that option. However, that's a trial and error and will have to play with the collision/false-positive fraction. And each iteration will most likely result in a compaction storm - so I was hoping for a way to throttle/limit the max off-heap size. The reason I was

Re: Does Java driver v3.1.x degrade cluster connect/close performance?

Hi Satoshi, This question would be better for the 'DataStax Java Driver for Apache Cassandra mailing list ', but I do have a few thoughts about what you are observing: Between java-driver 2.1 and 3.0 the driver

Re: OOM on Apache Cassandra on 30 Plus node at the same time

On Fri, Mar 3, 2017 at 11:18 AM, Shravan Ch wrote: > More than 30 plus Cassandra servers in the primary DC went down OOM > exception below. What puzzles me is the scale at which it happened (at the > same minute). I will share some more details below. You'd be surprised;

Re: Archive node

Hi, On Mon, Mar 6, 2017 at 12:46 PM Carlos Rolo wrote: > I would not suggest to do that, because the new "Archive" node would be a > new DC that you would need to build (Operational wise). > Yes, but it is a simple copy of an exists Puppet script in our case and it works...

Re: Does Java driver v3.1.x degrade cluster connect/close performance?

Interesting question since I never measured connect and close times. Usually this is something you do once the application starts and thats it. Do you plan to misuse it and create a new cluster object and open a new connection for each request? On Mon, Mar 6, 2017 at 7:19 AM, Satoshi Hikida

Re: Archive node

I would not suggest to do that, because the new "Archive" node would be a new DC that you would need to build (Operational wise). You could also snapshot the old one once it finishes and use SSTableloader to push it into your Development DC. This way you have isolation from Production. Plus no

Archive node

Hi, The background story: we are developing an MMO strategy game and every two week the game world ends and we are starting a new one with a slightly different new database scheme. So that, we have over ~100 keyspaces in our cluster and we want to archive the old schemes into a separated

Re: Attached profiled data but need help understanding it

Hi Romain, We may be able to achieve what we need without LWT but that would require bunch of changes from the application side and possibly introducing caching layers and designing solution around that. But for now, we are constrained to use LWT's for another month or so. All said, I still would