Re: Lightweight transaction inside a batch : request rejected

As far as I remember, there is an optimization in Cassandra to manage Paxos ballot per table. So asking a Paxos operation to span multiple tables (even if same partition key) would require a lot of changes in the current impl. The question has already been raised, you may want to convince the

Re: CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation

Any workarounds that don't involve me having to figure out how to uninstall and re-install a different version? On Mon, Oct 24, 2016 at 1:24 PM, Ali Akhtar wrote: > 3.9.. > > On Mon, Oct 24, 2016 at 1:22 PM, DuyHai Doan wrote: > >> Which version of

Re: CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation

Thanks, but I did come across those, it doesn't look like they provide a resolution. On Mon, Oct 24, 2016 at 1:36 PM, DuyHai Doan wrote: > You may read those: > > https://issues.apache.org/jira/browse/CASSANDRA-12121 > https://issues.apache.org/jira/browse/CASSANDRA-12397

Re: CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation

You may read those: https://issues.apache.org/jira/browse/CASSANDRA-12121 https://issues.apache.org/jira/browse/CASSANDRA-12397 On Mon, Oct 24, 2016 at 10:24 AM, Ali Akhtar wrote: > Any workarounds that don't involve me having to figure out how to > uninstall and

Lightweight transaction inside a batch : request rejected

Hi, I would like to use lightweight transaction inside a batch but the request is rejected by cassandra, however I think this is a use case than could be handled without problem. Below is what I wanted to do. I am using cassandra 3.7. CREATE KEYSPACE test_ksp WITH replication = {'class':

Re: CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation

3.9.. On Mon, Oct 24, 2016 at 1:22 PM, DuyHai Doan wrote: > Which version of C* ? There was similar issues with commitlogs in tic-toc > versions. > > On Mon, Oct 24, 2016 at 4:18 AM, Ali Akhtar wrote: > >> I have a single node cassandra installation

Re: CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation

Which version of C* ? There was similar issues with commitlogs in tic-toc versions. On Mon, Oct 24, 2016 at 4:18 AM, Ali Akhtar wrote: > I have a single node cassandra installation on my dev laptop, which is > used just for dev / testing. > > Recently, whenever I restart

Re: time series data model

On 20 October 2016 at 09:29, wxn...@zjqunshuo.com wrote: > I do need to align the time windows to day bucket to prevent one row > become too big, and event_time is timestamp since unix epoch. If I use > bigint as type of event_time, can I do queries as you mentioned? Yes.

Re: CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation

If you're not in prod *yet*, I once again recommend not using 3.9 for anything serious. Use the latest 3.0.x. On Mon, Oct 24, 2016 at 6:19 PM Ali Akhtar wrote: > Stefania, > > As this is just on my dev laptop, what I'm really looking for is a quick > 1-2 min fix to this

Re: CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation

3.0.x? Isn't 3.7 stable? On Tue, Oct 25, 2016 at 6:32 AM, Jonathan Haddad wrote: > If you're not in prod *yet*, I once again recommend not using 3.9 for > anything serious. Use the latest 3.0.x. > > On Mon, Oct 24, 2016 at 6:19 PM Ali Akhtar wrote: >

Re: CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation

Nobody that I'm aware of can verify tick tock releases as stable. You can use the latest stuff if you want, just know there's probably bugs (like you're seeing) that nobody is aware of. Tick Tock releases (3.1, 3.2, etc) should really be thought of as development releases. They won't receive

Doing an upsert into a collection?

Say I have this UDT: *CREATE TYPE rating (* * user text,* * rating int* *);* And, I have this table: *CREATE TABLE movie (* * id text,* * name text,* * ratings list,* * PRIMARY KEY ( id )* *);* Say a user 'bob' rated a movie as a 5. Is it possible to do something like this: *UPDATE

Re: CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation

Did the schema change? This would be 12397. If not, and if you don't mind sharing the data, or you have the steps to reproduce it, could you please open a ticket so it can be looked at? You need to attach the schema as well. On Mon, Oct 24, 2016 at 9:33 PM, Ali Akhtar

Re: Question on write failures logs show Uncaught exception on thread Thread[MutationStage-1,5,main]

thank you that is quite helpful On Mon, Oct 24, 2016 at 11:00 PM, Edward Capriolo wrote: > The driver will enforce a max batch size of 65k. > This is an issue in versions of cassandra like 2.1.X. There are control > variables for the logged and unlogged batch size. You

Re: Does anyone store larger values in Cassandra E.g. 500 KB?

If I would do this, I would have have two tables; chunks and data: CREATE TABLE file_chunks { filename string, chunk int, size int, // Optional if you want to query the total size of a file. PRIMARY KEY (filename, chunk) } CREATE TABLE chunks { filename string, chunk int, data

Re: CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation

Stefania, As this is just on my dev laptop, what I'm really looking for is a quick 1-2 min fix to this solution that will act as a workaround. If I drop the keyspace and recreate it, will that fix this problem? Or do I need to uninstall 3.9 and go back to 3.7? I probably have made a couple of

Re: CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation

I want some of the newer UDT features, like not needing to have frozen UDTs On Tue, Oct 25, 2016 at 6:34 AM, Ali Akhtar wrote: > 3.0.x? Isn't 3.7 stable? > > On Tue, Oct 25, 2016 at 6:32 AM, Jonathan Haddad > wrote: > >> If you're not in prod *yet*, I

Re: Cluster Maintenance Mishap

On 21 October 2016 at 15:15, Branton Davis wrote: > For example, I forgot to mention until I read your comment, that the > instances showed as UN (up, normal) instead of UJ (up, joining) while they > were apparently bootstrapping. It's likely these nodes were

Re: Lightweight transaction inside a batch : request rejected

I can't do this, otherwhise i won't be able to query the item_id using a key with a query like : Select * from item_id_by_key where user_id=... and key= Le 25 oct. 2016 07:15, "Ben Slater" a écrit : > Move item_id_by_key into a collection field in item table?

Re: Lightweight transaction inside a batch : request rejected

Move item_id_by_key into a collection field in item table? (Would probably be a “better” C* data model anyway.) On Tue, 25 Oct 2016 at 16:08 Mickael Delanoë wrote: > Ok, I understand, thanks. > So now i would like to know if there is some best practices to do what i >

Re: CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation

On 25 October 2016 at 01:34, Ali Akhtar wrote: > I want some of the newer UDT features, like not needing to have frozen UDTs You can try Instaclustr's 3.7 LTS release which is just 3.7 with some backported fixes from later versions. If you absolutely need those new

Re: Doing an upsert into a collection?

On 24 October 2016 at 22:16, Ali Akhtar wrote: > *UPDATE movie set ratings.rating = 5 WHERE ratings.user = 'bob'* You won't be able to do this because you're trying to update a row without specifying the primary key. Also, even if you did add the PK to the where, you've

Re: Lightweight transaction inside a batch : request rejected

Ok, I understand, thanks. So now i would like to know if there is some best practices to do what i want. I.e inserting entries in several tables (with same partition key) only if there is not already an entry in the main table. Keep in mind i wanted to do that inside a single batch because I can

Re: Lightweight transaction inside a batch : request rejected

Yep, you would have to select the whole map and then pull out the particular value you want in your application. I didn’t actually realise you couldn’t just specify a particular map element in a select like you can in an update but it appears there is a long running Jira for this:

Re: CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation

I'm sure you can share the schema and data privately with the ticket assignee, when the ticket gets assigned and looked at. If it was a schema change problem, you can try going back to the old schema if you can recall what it was, but I cannot guarantee this would work without knowing the root

Re: Transparent Fail-Over for Java Driver to survive Cluster Rolling

Hi, Once the client is connected, it will automatically connect to many nodes in the cluster. Therefore once the app is running the amount of contact points doesn’t matter and if you have consistency level < ALL (or QUORUM where replication factor is <= 2), your app should tolerate rolling

Error creating pool to /IP_ADDRESS33:9042 (Proving Cassandra's NO SINGLE point of failure)

Hi, I have 3 nodes Cassandra cluster. Cassandra version : dsc-cassandra-2.1.5 Python Cassandra Driver : 2.5.1 Running the nodes in Red Hat virtual machines. Node ip info: Node 1: IP_ADDRESS219 Node 2: IP_ADDRESS229 Node 3: IP_ADDRESS230 (IP_ADDRESS219 is masked for this email which

Re: Transparent Fail-Over for Java Driver to survive Cluster Rolling

Thanks a lot Hannu! How about the write path though. What consistency level would I choose if I want to insert e.g. sensor data into my cluster without the app crashing every time I up update the cluster? I would assume that QUORUM (replication of 3) might not always go through? On Mon, Oct

Re: Lightweight transaction inside a batch : request rejected

"So I guess in that case the Paxos operation does not span multiple table but operates only the table that has the condition. Am I wrong?" --> The fact that you're using a BATCH with LWT means that either ALL statements succeed or NONE. And to guarantee this, Paxos ballot must cover all

Re: CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation

Its 'text'. Don't know the answer of the 2nd question. On Mon, Oct 24, 2016 at 6:31 PM, Jonathan Haddad wrote: > What type is board id? Is the value a tombstone? > > On Mon, Oct 24, 2016 at 1:38 AM Ali Akhtar wrote: > >> Thanks, but I did come across

Re: CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation

What type is board id? Is the value a tombstone? On Mon, Oct 24, 2016 at 1:38 AM Ali Akhtar wrote: > Thanks, but I did come across those, it doesn't look like they provide a > resolution. > > On Mon, Oct 24, 2016 at 1:36 PM, DuyHai Doan wrote: > > You

Re: Question about compaction strategy changes

If you drop window size, you may force some window-major compactions (if you go from 1 week windows to 1 day windows, you’ll have 6 days worth of files start compacting into 1-day sstables). If you increase window size, you’ll likely have adjacent windows join (if you go from 1 day windows

Re: Error creating pool to /IP_ADDRESS33:9042 (Proving Cassandra's NO SINGLE point of failure)

Probably used Python driver can't restart failed operation with connection to other node. Do you provide all three IPs to Python driver for connecting? Best regards, Vladimir Yudovin, Winguzone - Hosted Cloud Cassandra Launch your cluster in minutes. On Mon, 24 Oct 2016 07:48:05

incremental repairs with -pr flag?

Hey, In the datastax documentation on repair [1], it says, "The partitioner range option is recommended for routine maintenance. Do not use it to repair a downed node. Do not use with incremental repair (default for Cassandra 3.0 and later)." Why is it not recommended to use -pr with

Re: incremental repairs with -pr flag?

Hi Sean, In order to mitigate its impact, anticompaction is not fully executed when incremental repair is run with -pr. What you'll observe is that running repair on all nodes with -pr will leave sstables marked as unrepaired on all of them. Then, if you think about it you realize it's no big

Transparent Fail-Over for Java Driver to survive Cluster Rolling

Hi, I was wondering if it is enough to set a list of contact points via: Cluster.builder().addContactPoint("host1").addContactPoint("host2")...; to survive a cluster rolling while inserting/reading from the cluster. Regards, Andreas

Re: Transparent Fail-Over for Java Driver to survive Cluster Rolling

Hi, QUORUM would go through if only one node is down any given time. Depending on the consistency requirements of your application, you could also use ONE (or LOCAL_ONE) as well for sensor reading storage. That would go through even if two nodes are down any given time. BR, Hannu > On 24 Oct

Re: Question about compaction strategy changes

Thanks Jeff. We've been trying to find the optimal setting for our TWCS. It's just two tables with only one of the tables being a factor. Initially we set the window to an hour, and then increased it to a day. It still seemed that there were lots of small sstables on disk. dozens of small db files

Re: Lightweight transaction inside a batch : request rejected

Thanks DuyHai for the info. I already see this JIRA, however the use case I describe is slightly different from the JIRA as there is only ONE condition on ONE table. Other statements of the batch does not have any condition. So I guess in that case the Paxos operation does not span multiple table

Re: Hadoop vs Cassandra

If you intend to use files on HDFS, I would recommend using Parquet files. It's a very fast columnar format that allows querying data very efficiently. I believe a Spark data frame will take care of saving all the columns in a Parquet file. So you could extract the data from Cassandra via the

Re: Does anyone store larger values in Cassandra E.g. 500 KB?

Thanks. I will have a look into that. Vikas On Fri, Oct 21, 2016 at 7:18 PM, jason zhao yang < zhaoyangsingap...@gmail.com> wrote: > 1. usually before storing object, serialization is needed, so we can know > the size. > 2. add "chunk id" as last clustering key. > > Vikas Jaiman

Question on write failures logs show Uncaught exception on thread Thread[MutationStage-1,5,main]

Hey cassandra users, When performing writes I have hit an issue where the server is unable to perform writes. The logs show: WARN [MutationStage-1] 2016-10-24 22:05:52,592 AbstractLocalAwareExecutorService.java:169 - Uncaught exception on thread Thread[MutationStage-1,5,main]: {}

Re: Question on write failures logs show Uncaught exception on thread Thread[MutationStage-1,5,main]

The driver will enforce a max batch size of 65k. This is an issue in versions of cassandra like 2.1.X. There are control variables for the logged and unlogged batch size. You may also have to tweak your commitlog size as well. I demonstrate this here:

Re: Question about compaction strategy changes

On 24 October 2016 at 18:11, Seth Edwards wrote: > The other thought is that we currently have data mixed in that does not > have a TTL and we are strongly considering putting this data in it's own > table. You should definitely do that. Having non-TTL'd data mixed in will