In my cluster, I have it at 4096. I think you can start with 1024 and check
if you have no native requested blocked.
I believe this parameter depends on the cluster traffic
Cheers
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Tue, Apr 9, 2019 at 7:59 PM Abdul Pat
Your delete query
>> "DELETE FROM myTable WHERE course_id = 'C' AND assignment_id = 'A1';”.
will generate multi row range tombstones. Since you are reading entire
partition which effectively will be read in pages (slice query equivalent) you
may get tombstones in certain pages depending upon how
Hi Abdul,
When I have seen dropped messages, I normally double check to ensure the node
not CPU bound.
If you have a high CPU idle value, then it is likely that tuning the thread
counts will help.
I normally start with concurrent_reads and concurrent_writes, so in your case
as reads are bein
Thanks for the information.
George.
On Wed, Apr 10, 2019 at 3:14 AM Alok Dwivedi
wrote:
> Your delete query
>
> "DELETE FROM myTable WHERE course_id = 'C' AND assignment_id = 'A1';”.
>
> will generate multi row range tombstones. Since you are reading entire
> partition which effectively will be
Hi there,
I am running a cassandra cluster (v3.0.9) with 2 DCs (4/3 nodes respectively)
using endpoint_snitch: PropertyFileSnitch and I would like to decommission one
node in DC1 but I wonder about what kind of actions I need to take related with
the the topology settings.
My cassandra-topology
Hi All,
We are seeing some timeouts for Web calls which are going to remote DC, so
enabled debug tracing for DataStax java driver and getting below messages in
the application log file.However not able to get the exact reason for the
timeout. Need assistance in finding the same.
DataStax Java
Yes the queries are all select queries as they are more of read intensive
app.
Last night i rebooted cluster and today they are fine .(i know its
temporary) as i still is all time blocked values.
I am thinking of incresiing concurrent reads and writes to 256 and native
transport threads to 256 and
Yes the queries are all select queries as they are more of read intensive
app.
Last night i rebooted cluster and today they are fine .(i know its
temporary) as i still is all time blocked values.
I am thinking of incresiing concurrent
On Wednesday, April 10, 2019, Paul Chandler wrote:
> Hi Abdul
We have a multitenant cluster that we can't upgrade to 3.x easily, and we'd
like to migrate some apps off of the shared cluster to dedicated clusters.
This is a 2.2 cluster.
So I'm trying a trigger to track updates while we transition and will send
via kafka. Right now I'm just trying to extract
You'll have to setup a local repo like artifactory.
On Wed, Apr 3, 2019 at 4:33 AM Kyrylo Lebediev
wrote:
> Hi Oleksandr,
>
> Yes, that was always the case. All older versions are removed from Debian
> repo index :(
>
>
>
> *From: *Oleksandr Shulgin
> *Reply-To: *"user@cassandra.apache.org"
>
Hi Abdul,
Usually we get no noticeable improvement at tuning concurrent_reads and
concurrent_writes above 128. I generally try to keep current_reads to no
higher than 64 and concurrent_writes to no higher than 128. In creasing the
values beyond that you might start running into issues where the ke
Do we have any recommendations on concurrents reads ans writes settings?
Mine is 18 node 3 dc cluster with 20 core cpu
On Wednesday, April 10, 2019, Anthony Grasso
wrote:
> Hi Abdul,
>
> Usually we get no noticeable improvement at tuning concurrent_reads and
> concurrent_writes above 128. I gene
Hi Robert,
Your action plan looks good.
You can think of the *cassandra-topology.properties* file as a map for the
cluster. The map between the nodes must be consistent because each node
uses it to determine where it is meant to be located logically.
It is good hygiene to maintain the *cassandra
13 matches
Mail list logo
