I have been using the cassandra-stress tool to evaluate my cassandra
cluster for quite some time now. My problem is that I am not able to
comprehend the results generated for my specific use case.
My schema looks something like this:
CREATE TABLE Table_test(
ID uuid,
Time timestamp,
Your insert settings look unrealistic since I doubt you would be
writing 50k rows at a time. Try to set this to 1 per partition and
you should get much more consistent numbers across runs I would think.
select: fixed(1)/10
On Wed, Mar 4, 2015 at 7:53 AM, Nisha Menon nisha.meno...@gmail.com
HI Folks;
We are planning to deploy a Multi region C* Cluster with nodes on both US
coasts. Need some advice :
a) As I do not have Public IP address access, is there an alternative way to
deploy EC2MultiRegion snitch using Private IP addresses ? b) Has anyone used
EC2_Snitch with nodes
You could set up an Alert for Node down within OpsCenter. OpsCenter also
offers you the option to send an email to a paging system with reminders.
Jan/
On Sunday, March 8, 2015 6:10 AM, Vasileios Vlachos
vasileiosvlac...@gmail.com wrote:
We use Nagios for monitoring, and we call
I notice some of the discussion about rolling back and avoiding upgrading. I
wonder if people can elaborate on their pain points?
We are in a situation where there are some use cases we wish to implement that
appear to be much simpler to implement using indexed sets. So it has me
wondering
On Mon, Mar 9, 2015 at 2:17 PM, Jan cne...@yahoo.com wrote:
c) Has anyone used Gossiping_File_Property snitch got it working
successfully in a Multi region deployment.
Were I attempting the task you're doing, I'd use GPFS.
=Rob
2.1.3 has a few memory leaks/issues, resource management race conditions.
That is horribly vague, however looking at some of the fixes in 2.1.4 I’d be
tempted to wait on that.
2.1.3 is fine for testing though.
On Mar 9, 2015, at 6:42 PM, Jacob Rhoden jacob.rho...@me.com wrote:
I notice
On Mon, Mar 9, 2015 at 4:42 PM, Jacob Rhoden jacob.rho...@me.com wrote:
I notice some of the discussion about rolling back and avoiding upgrading.
I wonder if people can elaborate on their pain points?
We are in a situation where there are some use cases we wish to implement
that appear to
Hi All,
I used sstableloader to export data from first cassandra cluster (RF 3) to
another cluster with RF 1. Afther all the tables were copied and second
cluster was working fine I decided to run node repair on the second cluster
as regular operation. *This repair cause the data size on the
nodetool clearsnapshot
--
Ranger Tsao
2015-03-10 10:47 GMT+08:00 鄢来琼 laiqiong@gtafe.com:
Hi ALL,
After drop table, I found the data is not removed from disk, I should
reduce the gc_grace_seconds before the drop operation.
I have to wait for 10
Hi ALL,
After drop table, I found the data is not removed from disk, I should reduce
the gc_grace_seconds before the drop operation.
I have to wait for 10 days, but there is not enough disk.
Could you tell me there is method to clear the data from disk quickly?
Thank you very much!
Peter
Hi,every one:
I have a 12 nodes C* 2.0.9 cluster for titan.I found some error when doing
compaction,the exception stack:
java.lang.AssertionError: Added column does not sort as the last column
at
org.apache.cassandra.db.ArrayBackedSortedColumns.addColumn(ArrayBackedSortedColumns.java:115)
at
12 matches
Mail list logo
