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: 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: 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

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: 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

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

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

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: 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: 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

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

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

CommitLogReadHandler$CommitLogReadException: Unexpected error deserializing mutation

I have a single node cassandra installation on my dev laptop, which is used just for dev / testing. Recently, whenever I restart my laptop, Cassandra fails to start when I run it via 'sudo service cassandra start'. Doing a tail on /var/log/cassandra/system.log gives this log: *INFO [main]