Re: Cassandra 2.x Stability

2016-12-01 Thread Shalom Sagges
Thanks a lot Kai! Shalom Sagges DBA T: +972-74-700-4035 We Create Meaningful Connections

Re: Why does `now()` produce different times within the same query?

2016-12-01 Thread Edward Capriolo
On Thu, Dec 1, 2016 at 4:06 AM, Sylvain Lebresne wrote: > One can of course always open a JIRA, but I'm going to strongly disagree > with a > change here (outside of a documentation one that is). > > The now() function is a timeuuid generator, and it thus generates a unique

Re: Cassandra 2.x Stability

2016-12-01 Thread Shalom Sagges
Hey Kai, Thanks for the info. Can you please elaborate on the reasons you'd pick 2.2.6 over 3.0? Shalom Sagges DBA T: +972-74-700-4035 We Create Meaningful Connections

Re: Why does `now()` produce different times within the same query?

2016-12-01 Thread Bruce Heath
Get Outlook for Android From: Edward Capriolo Sent: Thursday, December 1, 2016 10:44:10 AM To: user@cassandra.apache.org Subject: Re: Why does `now()` produce different times within the same query? On Thu, Dec 1,

Re: Cassandra 2.x Stability

2016-12-01 Thread Benjamin Roth
A little experience report on MVs: We use them in production (3.10-trunk) and they work really well on normal read/write operations but streaming operations (bootstrap, repair, rebuild, decommision) can kill your cluster and/or your nerves. We will stay with MVs as we need them and want them. I

Re: Cassandra 2.x Stability

2016-12-01 Thread Kai Wang
Just based on a few observations on this list. Not one week goes by without people asking which release is the most stable on 3.x line. Folks at instaclustr also provide their own 3.x fork for stability issues. etc We developers already have enough to think about. I really don't feel like

Re: Cassandra 2.x Stability

2016-12-01 Thread Jonathan Haddad
I agree with everything you just said, Kai. I'd start a new project with 3.0.10. I'd stay away from MVs though. On Thu, Dec 1, 2016 at 10:19 AM Kai Wang wrote: > Just based on a few observations on this list. Not one week goes by > without people asking which release is the

Re: Cassandra: maximum size of collection list type

2016-12-01 Thread Selvam Raman
I am getting the below error when i am having huge list( greater than 3lakh). "Cassandra timeout during write query at consistency LOCAL_ONE (1 replica were required but only 0 acknowledged the write)" 2016-12-01 16:20 GMT+00:00 Selvam Raman : > Hi, > > What is the maximum

Re: Cassandra 2.x Stability

2016-12-01 Thread Kai Wang
Ben, I just read through those two tickets. It's scarier than I thought. Thank you for all the investigations and comments. On Thu, Dec 1, 2016 at 10:31 AM, Benjamin Roth wrote: > A little experience report on MVs: > > We use them in production (3.10-trunk) and they

Re: Why does `now()` produce different times within the same query?

2016-12-01 Thread Sylvain Lebresne
On Thu, Dec 1, 2016 at 4:44 PM, Edward Capriolo wrote: > > I am not sure you saw my reply on thread but I believe everyone's needs > can be met I will copy that here: > I saw it, but the real problem that was raised initially was not that of UDF and of allowing both

Re: Why does `now()` produce different times within the same query?

2016-12-01 Thread Jonathan Haddad
+1 to everything Sylvan said. On Thu, Dec 1, 2016 at 11:09 AM Sylvain Lebresne wrote: > On Thu, Dec 1, 2016 at 4:44 PM, Edward Capriolo > wrote: > > > I am not sure you saw my reply on thread but I believe everyone's needs > can be met I will copy

Re: Why does `now()` produce different times within the same query?

2016-12-01 Thread Cody Yancey
On Thu, Dec 1, 2016 at 11:09 AM Sylvain Lebresne wrote: > there is much much more trivial solution: generate it client side. The > `now()` function is a small convenience but there is nothing you cannot do > without it client side > Please see my post above as to why this

Cassandra: maximum size of collection list type

2016-12-01 Thread Selvam Raman
Hi, What is the maximum size which can be stored into collection list(in a row ) in cassandra. -- Selvam Raman "லஞ்சம் தவிர்த்து நெஞ்சம் நிமிர்த்து"

Re: Why does `now()` produce different times within the same query?

2016-12-01 Thread Edward Capriolo
On Thu, Dec 1, 2016 at 11:09 AM, Sylvain Lebresne wrote: > On Thu, Dec 1, 2016 at 4:44 PM, Edward Capriolo > wrote: > >> >> I am not sure you saw my reply on thread but I believe everyone's needs >> can be met I will copy that here: >> > > I saw it,

Re: Cassandra: maximum size of collection list type

2016-12-01 Thread Benjamin Roth
You can read it in the docs but i think it was 2^16 aka 64k Am 01.12.2016 18:00 schrieb "Selvam Raman" : > Hi, > > What is the maximum size which can be stored into collection list(in a row > ) in cassandra. > > -- > Selvam Raman > "லஞ்சம் தவிர்த்து நெஞ்சம் நிமிர்த்து" >

Re: Cassandra: maximum size of collection list type

2016-12-01 Thread Jeff Jirsa
A 64k element list will not be performant. Even 10% of that will be painful for many users. From: Vladimir Yudovin Reply-To: "user@cassandra.apache.org" Date: Thursday, December 1, 2016 at 10:34 AM To: user

Re: Cassandra: maximum size of collection list type

2016-12-01 Thread DuyHai Doan
My usual rule-of-thumb recommendation for most use-cases is not to exceed 1000 elements. The reasoning behind this is if you have more than 1000 elements, maybe using extra clustering columns to handle them is cleaner and put less pressure on the heap since all the collection data are fetched at

Re: Cassandra: maximum size of collection list type

2016-12-01 Thread Vladimir Yudovin
As doc says: The maximum size of an item in a collection is 64K. Keep collections small to prevent delays during querying because Cassandra reads a collection in its entirety. The collection is not paged internally. As discussed earlier, collections are designed to store only a small amount

Re: Why does `now()` produce different times within the same query?

2016-12-01 Thread Ben Bromhead
> > > > I will note that Ben seems to suggest keeping the return of now() unique > across > call while keeping the time component equals, thus varying the rest of the > uuid > bytes. However: > - I'm starting to wonder what this would buy us. Why would someone be > super >confused by the time

Re: Why does `now()` produce different times within the same query?

2016-12-01 Thread Marko Švaljek
One millisecond is not an issue in most of Internet of Things projects out there. There are lots of connection related things that add far more latency to the requests than that. Especially if you take into account the time it takes for the data to actually come to a cassandra node in the

empty buckets with STCS

2016-12-01 Thread John Sanda
I have 2.2.1 Cassandra node that does not appear to be compacting SSTables. The table is currently configured with STCS. I turned on some debug logging and when the compaction checks run, they log: Compaction buckets are [] I have been going over SizeTieredCompactionStrategy.java and looking in

Re: Cassandra 2.x Stability

2016-12-01 Thread Kai Wang
I have been running 2.2.6 in production. As of today I would still pick it over 3.x for production. On Nov 30, 2016 5:42 AM, "Shalom Sagges" wrote: > Hi Everyone, > > I'm about to upgrade our 2.0.14 version to a newer 2.x version. > At first I thought of upgrading to

Re: Why does `now()` produce different times within the same query?

2016-12-01 Thread Sylvain Lebresne
One can of course always open a JIRA, but I'm going to strongly disagree with a change here (outside of a documentation one that is). The now() function is a timeuuid generator, and it thus generates a unique timeuuid on every call, as specified by the timeuuid spec. I'll note that document lists

Re: Sanity checks to run post restore data?

2016-12-01 Thread Benjamin Roth
Restoring SSTables is not trivial in terms of restoring a consistent state. It depends on your failure scenario. - Do you want to recover from unintentionally deleted data? Then it is possible that you restore the data on one node, run a repair and the data is deleted again because the tombstones