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 cause. Same thing regarding which release to try, without knowing the root cause, it's really not possible to advise a specific release. The easiest thing to do is to skip the mutations with problems. You still loose some data but at least not all data. If you see this in your logs: Replay stopped. If you wish to override this error and continue starting the node ignoring commit log replay problems, specify -Dcassandra.commitlog.ignorereplayerrors=true on the command line. Then it means that you can start Cassandra with -Dcassandra.commitlog.ignorereplayerrors=true and it will carry on even if it cannot parse some mutations, which will be saved in the /tmp folder. If it was a schema change problem, then you shouldn't need to start with this property more than once. If the problem persists with new commit log segments, then it's definitely another problem and you should really open a ticket. On Tue, Oct 25, 2016 at 10:36 AM, kurt Greaves <k...@instaclustr.com> wrote: > > On 25 October 2016 at 01:34, Ali Akhtar <ali.rac...@gmail.com> 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 > features it's probably your best bet (until 4.0), however note that it's > still 3.7 and likely less stable than the latest 3.0.x releases. > > https://github.com/instaclustr/cassandra > > Read the README at the repo for more info. > > Kurt Greaves > k...@instaclustr.com > www.instaclustr.com > -- Stefania Alborghetti |+852 6114 9265| stefania.alborghe...@datastax.com
