> Can you outline the detailed steps to reproduce the issue Yuji ?
>
Our application requests UPDATE a row.
The row has "id"(PRIMARY KEY), "revision" and "value" columns.
The updating condition is EQ of current "revision".
When the problem happens, the following sequence is executed in one
>
>
> I am using internode encryption in cassandra, with self signed CA it
works fine. but with other product CA m getting this error "Filtering out
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA as it
isnt supported by the socket”
>
You've specified ECDHE_RSA as the
Thanks Jonathan and Julien for the advice. I will go with 3.0.
Cheers
Farzad
On Thu, Jul 21, 2016 at 1:34 AM, Julien Anguenot
wrote:
> Yes, we have been running 3.0.x for a while and we consider it mostly
> stable now. Though, we did not have to bootstrap new nodes / new
Hi Siddharth,
Thank you for answer.
Yes this is exactly the same goal that I wish to accomplish, though I was
wondering whether it would be possible to access the data of the row that
is being inserted so that I would be able to take a snapshot of the entire
row. Does anybody knows if that is
Hi Garo,
I haven't had this issue on SSDs, but I have definitely seen it with
spinning drives. I would think that SSDs would have more than enough
bandwidth to keep up with requests, but you may be running into issues
with Cassandra calling fsync on the commitlog.
What are your settings for the
Hi Jakub,
I worked with trigger, I was auditing it by time
.
I considered the following partition keys for the audit table.
1. (timeuuid,uuid) OR,
2. formatted date in groups of 5 minutes
21 March 2015, 13:44:15 -> 201503211340
*Used it to batch operations by a group of minutes.*
*Caution : If
Those ciphers are not available on Java 6, on the off chance that you're
trying to run Cassandra on that (you'll run into other troubles).
The more likely problem is that I think those ciphers are only available if
you install the Unlimited Strength JCE policy files in your JVM on each
node.
Hi Jean,
I think this is a good resource: https://www.youtube.com/watch?v=FuP1Fvrv6ZQ
Best,
On Mon, Jul 25, 2016 at 2:45 PM, jean paul wrote:
> As i find in cassandra Documentation, the gossip process runs every second.
> Please, why you have chosen 'running it *every
Hi guys,
I had been exploring recently the Cassandra Triggers and I think that there
are going to be very useful for my use case, though I think that I would
need a bit of help with setting it up.
I fallow this example and it was been very helpful, my use case is
basically similar I want to have
As i find in cassandra Documentation, the gossip process runs every second.
Please, why you have chosen 'running it *every second'* ?
Thanks a lot.
2016-07-25 13:12 GMT+01:00 jean paul :
> Hi all;
>
> I have used Apache Cassandra version 2.1.6 for my experiments.
>
>
Hi all;
I have used Apache Cassandra version 2.1.6 for my experiments.
Please, what is the gossip delay or threshold ? The gossip process is
running every . seconds ?
Thank you so much for help.
Kind regards.
Hi ,
I am using internode encryption in cassandra, with self signed CA it works
fine. but with other product CA m getting this error "Filtering out
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA as it
isnt supported by the socket”
Thank you.
Regards,
Ashwini Mhatre
Can you outline the detailed steps to reproduce the issue Yuji ?
On Mon, Jul 25, 2016 at 3:16 AM, Yuji Ito wrote:
> thanks, Ryan
>
>
>> are you using one of the SERIAL Consistency Levels?
>
> yes, I use read with ConsistencyLevel.SERIAL.
>
> On Mon, Jul 25, 2016 at 10:10
13 matches
Mail list logo