diness check imo.
> For the query why not select 1; ?
>
> --
>
> Raphael Mazelier
>
>
> On 25/08/2023 19:38, Shaurya Gupta wrote:
>
> Hi community
>
> We want to validate cassandra connectivity from the application container
> when it starts up and before it
her suggestions ?
--
Shaurya Gupta
back out? etc). All can play into
>> this.
>>
>> On Fri, Aug 11, 2023, at 3:40 PM, Jeff Jirsa wrote:
>>
>> You’re going to have to help us help you
>>
>> 4.0 is pretty widely deployed. I’m not aware of a perf regression
>>
>> Can you give us a s
ld not be a problem if rightly designed. Levelled compaction
> strategy further reduces this, however it consume some resources. For read,
> caching is also helpful.
> Can you check your cpu iowait as it could be the reason for delay
>
> Regards,
> Ashish
>
> On Fri, 11
observe those to be 40 ms P95 Reads and same for Writes. This looks very
high as compared to what we expected. We are using Cassandra 4.0.
Any documentation / numbers will be helpful.
Thanks
--
Shaurya Gupta
is it possible that the configs got applied even before a single
cassandra node was restarted ?
Thanks
Shaurya
--
Shaurya Gupta
milliseconds.
The CPU consumed by the container is just 35% of available.
Can someone help with this ?
Thanks
--
Shaurya Gupta
t; https://issues.apache.org/jira/browse/CASSANDRA-10404
>
> By Any chance, did you try to enable internode encryption in 3.x
> without downtime and were successful? Can you please confirm.
> Best Regards,
> Kiran.M.K.
>
>
> On Wed, Nov 10, 2021 at 12:04 PM Tolbert, Andy
Thanks Andy! It was very helpful.
On Wed, Nov 10, 2021 at 12:04 PM Tolbert, Andy wrote:
> Hi Shaurya,
>
> On Tue, Nov 9, 2021 at 11:57 PM Shaurya Gupta
> wrote:
>
>> Hi,
>>
>> We want to enable node-to-node SSL on a live cluster. Could it be done
>> with
Hi,
We want to enable node-to-node SSL on a live cluster. Could it be done
without any down time ?
Would the nodes which have been restarted be able to communicate with the
nodes which have not yet come up and vice versa ?
Regards
--
Shaurya Gupta
sAddDCToCluster.html.
> Cheers!
>
--
Shaurya Gupta
seed
list from DC2 (node booted in previous step) & DC1.
3. Change of RFs of required keyspaces in DC1 to mention DC2.
If someone could point to some already available documentation then that
would be great too.
--
Shaurya Gupta
f data, which is going to overwhelm it when it
> streams and compacts. CASSANDRA-3200 helps this in 4.0, and incremental
> repair helps this if you're running incremental repair (again, probably
> after CASSANDRA-9143 in 4.0), but the naive approach can lead to really bad
> surprises.
&g
center, you have 3 copies of data.
> If you have 3 DCs, means 9 copies of data.
> Think about space wasted, Network bandwidth wasted for number of copies.
> BTW, Ours just 2 DCs for regional DR.
>
> Thanks,
> Jim
>
> On Wed, Jul 14, 2021 at 2:27 AM Shaurya Gupta
&
on all the data
> centers.
>
>
> On Wed, Jul 14, 2021 at 12:03 PM Shaurya Gupta
> wrote:
>
>> Hi
>>
>> Does someone have any suggestions on the maximum number of Data Centers
>> which NetworkTopology strategy can have for a keyspace. Not only
>> techn
Hi
Does someone have any suggestions on the maximum number of Data Centers
which NetworkTopology strategy can have for a keyspace. Not only
technically but considering performance as well.
In each Data Center RF is 3.
Thanks!
--
Shaurya Gupta
-+---
*123* | *Ashish* | *[{**house_no**: **123**, **name**: **'ashish'**,
**city**: **'patna'**, **pin: 246746**}, {**house_no**: **544**, **name**: *
*'ashish'**, **city**: **'california'**, **pin**: **2019**}, {**house_no**:
**124**, **name**: **'rana'**, **city**: **'delhi'**, **pin**: **2020**}]*
| *2500*
*and this should happen atomically.*
Thanks!
--
Shaurya Gupta
hanks
--
Shaurya Gupta
case however for isolation (updates to different column families are not
isolated)
"
*Though it is for Cassandra 1.1 but, is this still true and is this also
true for unlogged batch operations?*
--
Shaurya Gupta
elect * from demo.tweets;
*id* | *body* | *latitude* | *longitude* | *time* | *user*
+--+--+---+--+--
(0 rows)
Thanks
Shaurya
On Fri, May 3, 2019 at 1:02 AM Shaurya Gupta wrote:
> One suggestion - I think Cassandra community is already having a drive
One suggestion - I think Cassandra community is already having a drive to
update the documentation. This could be added to CQLSH documentation or
some other relevant documentation.
On Fri, May 3, 2019 at 12:56 AM Shaurya Gupta
wrote:
> Thanks Jeff.
>
> On Fri, May 3, 2019 at 12:38 AM J
Thanks Jeff.
On Fri, May 3, 2019 at 12:38 AM Jeff Jirsa wrote:
> No. Don’t mix LWT and normal writes.
>
> --
> Jeff Jirsa
>
>
> > On May 2, 2019, at 11:43 AM, Shaurya Gupta
> wrote:
> >
> > Hi,
> >
> > We are seeing really odd behaviour while
Hi,
We are seeing really odd behaviour while try to delete a row which is
simultaneously being updated in a light weight transaction.
The delete command succeeds and the LWT update fails with timeout exception
but still the next select statement shows that the row still exists. This
occurs ones in
gt; Lastname: pitt| dicaprio | Mcconahey | Beckinsale | Green
>
> ... would have been completely acceptable provided the fact I will
> retrieve them by using the indedx [0] would mean brad pitt and [1] would
> mean leonardo dicaprio in my applications
> But the same indexed based retrieval would fail in case 2 where [0] would
> mean leonardo pitt and [1] would mean brad dicaprio.
>
> Please help with any insights, I would be really grateful.
>
--
Shaurya Gupta
As already mentioned in this thread, ALLOW FILTERING should be avoided in
any scenario.
It seems to work in test scenarios, but as soon as the data increases to
certain size(a few MBs), it starts failing miserably and fails almost
always.
Thanks
Shaurya
On Wed, Apr 17, 2019, 6:44 PM Durity, Sea
eresting talks on Cassandra Traffic management,
> Cassandra on Kubernetes. See details in the attached link -
>
>
> https://www.eventbrite.com/e/cassandra-traffic-management-at-instagram-cassandra-and-k8s-with-instaclustr-tickets-54986803008
>
> Thanks,
>
> Dinesh
>
--
Shaurya Gupta
you
> propose has been discussed in the past and it is something that is
> currently unsupported.
>
> Dinesh
>
>
> On Tuesday, November 27, 2018, 11:05:32 PM PST, Shaurya Gupta <
> shaurya.n...@gmail.com> wrote:
>
>
> Hi,
>
> We want to throttle maxim
.
If not is there any plan to do so in future.
It is a must have feature if we want to support multiple teams on a single
cassandra cluster or to prevent one keyspace from interfering with the
performance of the other keyspaces.
Regards
Shaurya Gupta
28 matches
Mail list logo