Hi,
We are using 2.0.x in production env. Each node has 8G heap. Is there a
practical limit to how many keyspaces I can have? Please note that many
keyspaces remain mostly dormant while others have very high level of
activity.
--
Sourabh Agrawal
Bangalore
+91 9945657973
Yes, what about CQL style columns? Please clarify
On Sat, Jul 5, 2014 at 12:32 PM, tommaso barbugli
wrote:
> Yes my question what about CQL-style columns.
>
>
> 2014-07-04 12:40 GMT+02:00 Jens Rantil :
>
> Just so you guys aren't misunderstanding each other; Tommaso, you were not
>> refering to
Thank you both!
Robert, I read through the bug--it sounds like this behavior has been fixed
(or the impact reduced) in 2.1, but given that our data is pretty uniform
(with no overlap between rows/values), it doesn't look like we'll suffer
from that. At least, that's what I understood from the bug
The Cassandra team is pleased to announce the release of the second release
candidate for the future Apache Cassandra 2.1.0.
Let first stress that this is not yet the final release of 2.1.0 and as
such is
*not* ready for production use. We however encourage as much testing as
possible of this rele
Moving to Leveled compaction resolved same problem for us. As Robert
mentioned, use it carefully.
Size tiered compaction requires having 50% free disk space (also according
to datastax documentation).
Pavel
On Wed, Jul 9, 2014 at 8:39 PM, Robert Coli wrote:
> On Wed, Jul 9, 2014 at 4:27 PM, An
It seems that memtable tries to flush itself to SSTable of not existing
keyspace. I don't know why it is happens, but probably running nodetool
flush before drop should prevent this issue.
Pavel
On Thu, Jul 10, 2014 at 4:09 AM, Fabrice Larcher
wrote:
> Hello,
>
> I am using the 'development'
Hello,
I am using the 'development' version 2.1-rc2.
With one node (=localhost), I get timeouts trying to connect to C* after
running a 'DROP KEYSPACE' command. I have following error messages in
system.log :
INFO [SharedPool-Worker-3] 2014-07-09 16:29:36,578
MigrationManager.java:319 - Drop K
Look at change log on the Github repo for the MBean class
Le 10 juil. 2014 09:14, "bhavishya.p" a écrit :
>
> Hi..
> There seems to be a new feature added in the Metrics MBean which provides
> the overall metrics for a particular cluster. In which version was this
> feature added?
> Also, how can
Hi..
There seems to be a new feature added in the Metrics MBean which provides the
overall metrics for a particular cluster. In which version was this feature
added?
Also, how can we determine in which version the changes are made in general?
Thanks in advance.
Regards,
Bhavishya Palukur