Hi Brooke, Just had a quick look on your code and I will promise that your LTS version will have the same issues with MVs as any other version. For details check CASSANDRA-12905 or CASSANDRA-12888.
2016-11-30 8:35 GMT+01:00 Brooke Jensen <bro...@instaclustr.com>: > 2.1 will be end of life soon. > > We have a number of customers running 3.7 in production and it's quite > stable. However you should always test in a lower environment first with > your data model to be sure. > > If you're interested, we have made available a patched version of 3.7 > <https://www.instaclustr.com/blog/2016/10/19/patched-cassandra-3-7/> > which backports some key patches from 3.9. > https://github.com/instaclustr/cassandra > > > *Brooke Jensen* > VP Technical Operations & Customer Services > www.instaclustr.com | support.instaclustr.com > <https://support.instaclustr.com/hc/en-us> > > This email has been sent on behalf of Instaclustr Limited (Australia) and > Instaclustr Inc (USA). This email and any attachments may contain > confidential and legally privileged information. If you are not the > intended recipient, do not copy or disclose its content, but please reply > to this email immediately and highlight the error to the sender and then > immediately delete the message. > > On 30 November 2016 at 18:20, Benjamin Roth <benjamin.r...@jaumo.com> > wrote: > >> What are the compaction issues / hint corruprions you encountered? Are >> there JIRA tickets for it? >> I am curios cause I use 3.10 (trunk) in production. >> >> For anyone who is planning to use MVs: >> They basically work. We use them in production since some months, BUT >> (it's a quite big one) maintainance is a pain. Bootstrapping and repairs >> may be - depending on the model, config, amount of data - really, really >> painful. I'm currently investigating intensively. >> >> 2016-11-30 3:11 GMT+01:00 Harikrishnan Pillai <hpil...@walmartlabs.com>: >> >>> 3.0 has "off the heap memtable" impl removed and if you have a >>> requirement for this,its not available.If you don't have the requirement >>> 3.0.9 can be tried out. 3.9 version we did some testing and find lot issues >>> in compaction,hint corruption etc. >>> >>> Regards >>> >>> Hari >>> >>> >>> ------------------------------ >>> *From:* Discovery <wl_...@qq.com> >>> *Sent:* Tuesday, November 29, 2016 5:59 PM >>> *To:* user >>> *Subject:* Re: Which version is stable enough for production >>> environment? >>> >>> Why version 3.x is not recommended? Thanks. >>> >>> >>> ------------------ Original ------------------ >>> *From: * "Harikrishnan Pillai";<hpil...@walmartlabs.com>; >>> *Date: * Wed, Nov 30, 2016 09:57 AM >>> *To: * "user"<user@cassandra.apache.org>; >>> *Subject: * Re: Which version is stable enough for production >>> environment? >>> >>> Cassandra 2.1.16 >>> >>> >>> ------------------------------ >>> *From:* Discovery <wl_...@qq.com> >>> *Sent:* Tuesday, November 29, 2016 5:42 PM >>> *To:* user >>> *Subject:* Which version is stable enough for production environment? >>> >>> Hi Cassandra Experts, >>> >>> We prepare to deploy Cassandra in production env, but >>> we can not confirm which version is stable and recommended, could someone >>> in this mail list give the suggestion? Thanks in advance! >>> >>> >>> Best Regards >>> Discovery >>> 11/30/2016 >>> >> >> >> >> -- >> Benjamin Roth >> Prokurist >> >> Jaumo GmbH · www.jaumo.com >> Wehrstraße 46 · 73035 Göppingen · Germany >> Phone +49 7161 304880-6 <+49%207161%203048806> · Fax +49 7161 304880-1 >> <+49%207161%203048801> >> AG Ulm · HRB 731058 · Managing Director: Jens Kammerer >> > > -- Benjamin Roth Prokurist Jaumo GmbH · www.jaumo.com Wehrstraße 46 · 73035 Göppingen · Germany Phone +49 7161 304880-6 · Fax +49 7161 304880-1 AG Ulm · HRB 731058 · Managing Director: Jens Kammerer