+1 to what Eric said, a queue is a classic C* anti-pattern. Something like
Kafka or RabbitMQ might fit your use case better.
Mark
On 24 May 2016 at 18:03, Eric Stevens wrote:
> It sounds like you're trying to build a queue in Cassandra, which is one
> of the classic
No, this is what TTL is for.
If you want to schedule a cron to delete data this will need to be an
external task.
On 19 June 2015 at 07:41, anil_ah anil...@yahoo.co.in wrote:
Hi
Is their any way to schedule a job in cassandra to delete the recrods
which are older than a specific time
Have you configured the rpc_address to listen on that ip? You can check
your nodes casandra.yaml for the rpc_address setting.
On a side node why are you testing on such an old version of Cassandra? The
latest versions of 1.2.x is 1.2.19. There are also two branches of 2.x
which are 2.0.15 and
Can you check your logs for any other other error message around the time
of the repair? Something to look for would be Error occurred during
snapshot phase.
Regards,
Mark
On 25 May 2015 at 14:56, Sachin PK sachinpray...@gmail.com wrote:
Hey I'm new to Cassandra ,I have 4 node cluster with
To disable auto snapshots, set the property auto_snapshot: false in your
cassandra.yaml file.
Mark
On 21 May 2015 at 08:30, Ali Akhtar ali.rac...@gmail.com wrote:
Is there a config setting where automatic snapshots can be disabled? I
have a use case where a table is truncated quite often, and
Yes, it's a known issue. For more information on the topic see this support
post from DataStax:
https://support.datastax.com/hc/en-us/articles/204226339-How-to-drop-and-recreate-a-table-in-Cassandra-versions-older-than-2-1
Mark
On 21 May 2015 at 15:31, Ken Hancock ken.hanc...@schange.com wrote:
It's always good to run nodetool describecluster after a schema change,
this will show you all the nodes in your cluster and what schema version
they have. If they have different versions you have a schema disagreement
and should follow this guide to resolution:
Raman,
To unsubscribe send a mail to user-unsubscr...@cassandra.apache.org
On 22 February 2015 at 03:59, Raman ra...@assetcorporation.net wrote:
unsubscribe
Hey Clint,
Someone for DataStax can correct me here, but I'm assuming that they have
disabled vnodes because the AMI is built to make it easy to set up a
pre-configured
mixed workload cluster. A mixture of Real-Time/Transactional (Cassandra),
Analytics (Hadoop), or Search (Solr). If you take a
Please use user-unsubscr...@cassandra.apache.org to unsubscribe from this
mailing list.
Thanks
Regards,
Mark
On 19 February 2015 at 09:14, Hilary Albutt - CEO
hil...@incrediblesoftwaresolutions.com wrote:
Cancel subscription
What is a long time in your scenario? What is the data size in your cluster?
I'm sure Rob will be along shortly to say that 2.1.2 is, in his opinion,
broken for production use...an opinion I'd agree with. So bare that in mind
if you are running a production cluster.
Regards,
Mark
On 19
Yes you can use Oracle JDK if your prefer, I've been using the JDK with
Cassandra in production for years without issue.
Regards,
Mark
On 18 February 2015 at 19:49, cass savy casss...@gmail.com wrote:
Can we install Oracle JDK instead of JRE in Cassandra servers? We have
few clusters running
Hey Jiri,
While I don't have any experience running 4TB nodes (yet), I would
recommend taking a look at a presentation by Arron Morton on large nodes:
http://planetcassandra.org/blog/cassandra-community-webinar-videoslides-large-nodes-with-cassandra-by-aaron-morton/
to see if you can glean
Hi Santo,
If you are seeing the compacted_at value as timestamp and want to convert
it to a human readable date, this is not possible via nodetool. You will
always write a script to make the compactionhistory call and then convert
the output (the fourth column - compacted_at) to a readable date.
, commitlog_directory and saved_caches
directory and after that it worked.
Thanks a lot for the help ...
On Wed, Feb 4, 2015 at 2:32 PM, Mark Reddy mark.l.re...@gmail.com wrote:
INFO 22:17:19 Loading settings from file:/home/csduser/cassandra/
conf/cassandra.yaml
ERROR 22:17:20 Fatal configuration
Hey Krish,
Here is a list of use cases from the industry:
http://planetcassandra.org/apache-cassandra-use-cases/ You may find some
examples on how people/companies are using and running their C* clusters.
Also DataStax provide online training that will get you up to speed on
several aspects of
Hey Saurabh,
I can't say that I have experienced this before, however if you can
reliably reproduce the issue it would be worth commenting on the JIRA issue
you linked to or alternatively creating a new JIRA with as much info
(setup, test case, debug logs, etc) as possible.
Regards,
Mark
On 5
INFO 22:17:19 Loading settings from file:/home/csduser/cassandra/
conf/cassandra.yaml
ERROR 22:17:20 Fatal configuration error
org.apache.cassandra.exceptions.ConfigurationException: Invalid yaml
You have an malformed cassandra.yaml config file that is resulting in
Cassandra not being able
If you have a list of usernames stored in your cassandra database,
how could you find all usernames starting with 'Jo'?
Cassandra does not support full text search on its own, if you are looking
into DataStax enterprise Cassandra there is an integration with Slor that
gives you this
Hi Boying,
I'm not sure I fully understand your question here, so some clarification
may be needed. However, if you are asking what steps need to be performed
on the current datacenter or on the new datacenter:
Step 1 - Current DC
Step 2 - New DC
Step 3 - Depending on the snitch you may need to
I believe you were attempting to share:
https://issues.apache.org/jira/browse/CASSANDRA-8352
Your cassandra logs outputs the following:
DEBUG [Thrift:4] 2014-11-20 15:36:50,653 CustomTThreadPoolServer.java
(line 204) Thrift transport error occurred during processing of message.
Hi Rajanish,
Cassandra imposes a max TTL of 20 years.
public static final int MAX_TTL = 20 * 365 * 24 * 60 * 60; // 20 years in
seconds
See:
https://github.com/apache/cassandra/blob/8d8fed52242c34b477d0384ba1d1ce3978efbbe8/src/java/org/apache/cassandra/db/ExpiringCell.java#L37
Mark
On 21
Hi Adil,
What Cassandra version are you using? Are you using the default user or a
non-default user?
Mark
On 20 November 2014 08:20, Adil adil.cha...@gmail.com wrote:
Hi,
We have two data-center, we configured PasswordAuthenticator on each node,
we increment the RF of system_auth to the
, Adil adil.cha...@gmail.com wrote:
cassandra version 2.1.2
with the default user
we create another user and with this one we could login even if only one
node is up
2014-11-20 15:16 GMT+01:00 Mark Reddy mark.l.re...@gmail.com:
Hi Adil,
What Cassandra version are you using? Are you using
To be clear, I don't believe DSE is required to use OpsCenter. My
understanding is that it can be used with vanilla Apache Cassandra, but I
have never actually tried to do so.
Correct Rob, you can use Opscenter with vanilla Apache Cassandra.
Mark
On 20 November 2014 16:10, Robert Coli
Hi Clint,
The values of SSTables, Write Latency and Read Latency will be reset on
node start/restart and after running the cfhistograms command itself.
The values of Row Size and Column Count are calculated at startup and
then re-evaluated during compaction.
Mark
On 16 November 2014 17:12,
HI Eric,
It looks like you are running into CASSANDRA-7878
https://issues.apache.org/jira/browse/CASSANDRA-7878 which is fixed
in 2.0.11 / 2.1.1
Mark
On 1 November 2014 14:08, Eric Stevens migh...@gmail.com wrote:
We've been commissioning some new nodes on a 2.0.10 community edition
Oleg,
If you are running nodetool status, be sure to specify the keyspace also.
If you don't specify the keyspace the results will be nonsense.
https://issues.apache.org/jira/browse/CASSANDRA-7173
Regards,
Mark
On 28 October 2014 10:35, Oleg Dulin oleg.du...@gmail.com wrote:
I have a setup
Hi stephen,
I have never added a node via OpsCenter, so this may be a short coming of
that process. However in non OpsCenter installs you would have to create
the data directories first:
sudo mkdir -p /mnt/cassandra/commitlog
sudo mkdir -p /mnt/cassandra/data
sudo mkdir -p
It is telling you that your yaml is invalid, from looking at the snippet
you have provided it looks like the seed_provider.parameters is not
correctly indented, it should look something like:
seed_provider:
- class_name: org.apache.cassandra.locator.SimpleSeedProvider
parameters:
-
)
at
org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:585)
Missing required directive CommitLogSync
Fatal configuration error; unable to start. See log for stacktrace.
Do you have any idea about this.
Thanks!
On Tue, Aug 26, 2014 at 3:07 PM, Mark Reddy mark.l.re...@gmail.com
Hi,
As a general rule of thumb I would steer clear of secondary indexes, this is
also the official stand that DataStax take (see p5 of their best practices doc:
http://www.datastax.com/wp-content/uploads/2014/04/WP-DataStax-Enterprise-Best-Practices.pdf).
“It is best to avoid using Cassandra's
Hi,
It looks like you are running into a known issue:
https://issues.apache.org/jira/browse/CASSANDRA-7780 and its being worked
on here: https://issues.apache.org/jira/browse/CASSANDRA-7145
Mark
On 20 August 2014 09:06, 鄢来琼 laiqiong@gtafe.com wrote:
Is it related to MAX_HEAP_SIZE and
Hi,
As you are writing as CL.ONE and cqlsh by default reads at CL.ONE, there is
a probability that you are reading stale data i.e. the node you have
contacted for the read may not have the most recent data. If you have a
higher consistency requirement, you should look at increasing your
Hi Clint,
You need to configure the datastax-agents so they know what machine
OpsCenter is running on. To do this you will need to edit the address.yaml
of the datastax-agent, located in /var/lib/datastax-agent/conf/. In this
file you need to add the following line:
stomp_interface:
Hi Peter,
At the time of the IllegalStateException, do you see the node that it
should be streaming from marked as down by the failure detector?
Mark
On Fri, Aug 15, 2014 at 5:45 AM, Peter Haggerty peter.hagge...@librato.com
wrote:
When adding nodes via bootstrap to a 27 node 2.0.9 cluster
How can we prevent a disconnected DC from coming back automatically?
You could use firewall rules to prevent the disconnected DC from contacting
your live DCs when it becomes live again
Mark
On Thu, Aug 14, 2014 at 6:48 AM, Lu, Boying boying...@emc.com wrote:
Hi, All,
We are using
Hi,
Gossip will propagate to all nodes in a cluster. So if you have a cluster
spanning DC1, DC2 and DC3 and you then remove all nodes in DC3 via nodetool
removenode from a node in DC1, all nodes in both DC1 and DC2 will be
informed of the nodes removal so no need to run it from a node in DC2.
Hi,
Without more information (Cassandra version, setup, topology, schema,
queries performed) this list won't be able to assist you. If you can
provide a more detailed explanation of the steps you took to reach your
current state that would be great.
Mark
On Tue, Aug 12, 2014 at 12:21 PM,
Hi Vish,
1. This tool repairs inconsistencies across replicas of the row. Since
latest update always wins, I dont see inconsistencies other than ones
resulting from the combination of deletes, tombstones, and crashed nodes.
Technically, if data is never deleted from cassandra, then nodetool
Hi,
When you configured the new node, did you correctly configure your seeds
and listen address?
Mark
On Mon, Aug 11, 2014 at 6:12 PM, Rahul Gupta rgu...@dekaresearch.com
wrote:
I have a 3 node Cassandra cluster and I am adding a new node when I get
below error during bootstrap.
Running
Hi,
While I have no direct experience with the Python driver itself I took a
quick and it uses Cassandra's native transport protocol, so setting the
port to 9160 (Thrift protocol) won't work. You will need to set it to the
native transport port, which is 9042.
Also make sure that you have the
Hi Ian,
The issues here, which relates to normal and index column families, is
scanning over a large number of tombstones can cause Cassandra to fall over
due to increased GC pressure. This pressure is caused because tombstones
will create DeletedColumn objects which consume heap. Also
these
or updated since there
is no sense of how frequent is too frequent.
Cheers,
Ian
On Sun, Aug 10, 2014 at 3:02 PM, Mark Reddy mark.re...@boxever.com
wrote:
Hi Ian,
The issues here, which relates to normal and index column families, is
scanning over a large number of tombstones can
Hi Phil,
In theory, the max number of column families would be in the low number of
hundreds. In practice the limit is related the amount of heap you have, as
each column family will consume 1 MB of heap due to arena allocation.
To segregate customer data, you could:
- Use customer specific
Yes, you must run a full repair for the reasons stated in the yaml file.
Mark
On Tue, Aug 5, 2014 at 11:52 AM, Rene Kochen rene.koc...@schange.com
wrote:
Hi all,
I want to add a data-center to an existing single data-center cluster.
First I have to make the existing cluster multi
are blocked.
On Tue, Aug 5, 2014 at 10:14 AM, Ruchir Jha ruchir@gmail.com
wrote:
Yes num_tokens is set to 256. initial_token is blank on all nodes
including the new one.
On Tue, Aug 5, 2014 at 10:03 AM, Mark Reddy mark.re...@boxever.com
wrote:
My understanding was that if initial_token
So the ‘strategy’ change may not be seen by all nodes when the ‘upgrade
keyspace …’ command returns and I can use ’describe cluster’ to check if
the change has taken effect on all nodes right?
Correct, the change may take time to propagate to all nodes. As Rahul said
you can check describe
35.22%
Compaction iprodgatecustomerorder_hist
2959560205312350192622 bytes 0.95%
On Tue, Aug 5, 2014 at 11:37 AM, Mark Reddy mark.re...@boxever.com
wrote:
Yes num_tokens is set to 256. initial_token is blank on all nodes
including the new one
Hi Vasilis,
To further on what Rob said
I believe you might be able to tune the phi detector threshold to help this
operation complete, hopefully someone with direct experience of same will
chime in.
I have been through this operation where streams break due to a node
falsely being marked
Hi Jens,
The system keyspace is configured with LocalStrategy, this strategy only
stores data on the the local node. This strategy is reserved for internal
use only and is used for other things such as SecondaryIndexes.
You cannot change the replication factor of the 'system' keyspace. If you
Hi Parag,
1) Would anyone be able to help me interrupt this information from
OpsCenter?
At a high level bootstrapping a new node has two phases, streaming and
secondary index builds. I believe OpsCenter will only report active
streams, the pending stream will be listed as such in
.
*From:* Mark Reddy [mailto:mark.re...@boxever.com]
*Sent:* Wednesday, July 30, 2014 4:42 AM
*To:* user@cassandra.apache.org
*Subject:* Re: bootstrapping new nodes on 1.2.12
Hi Parag,
1) Would anyone be able to help me interrupt this information from
OpsCenter?
At a high level
on non-production hours.
How do we make it such that full GC’s don’t impact bootstrapping? Should
we increase phi_convict_threshold ?
Parag
*From:* Mark Reddy [mailto:mark.re...@boxever.com]
*Sent:* Wednesday, July 30, 2014 7:58 AM
*To:* user@cassandra.apache.org
*Subject:* Re
we increase phi_convict_threshold ?
Parag
*From:* Mark Reddy [mailto:mark.re...@boxever.com]
*Sent:* Wednesday, July 30, 2014 7:58 AM
*To:* user@cassandra.apache.org
*Subject:* Re: bootstrapping new nodes on 1.2.12
Thanks for the detailed response. I checked ‘nodetool netstats
Looks like you are running into this issue:
https://issues.apache.org/jira/browse/CASSANDRA-7239
Mark
On Tue, Jul 29, 2014 at 5:32 PM, Jeronimo de A. Barros
jeronimo.bar...@gmail.com wrote:
Hi everyone,
After upgrade and clean install on a 5 nodes cluster:
Datacenter: datacenter1
What is your data size and number of columns in Cassandra. Do you do many
deletions?
On Mon, Jul 28, 2014 at 2:53 PM, Ruchir Jha ruchir@gmail.com wrote:
Really curious to know what's causing the spike in Columns and
DeletedColums below :
2014-07-28T09:30:27.471-0400: 127335.928: [Full
Check https://github.com/apache/cassandra/blob/trunk/NEWS.txt to see the
steps required, if any, when upgrading.
As a general practice you should also reviw the changes at
https://github.com/apache/cassandra/blob/trunk/CHANGES.txt If upgrading
major versions it is often recommended to be on the
After removing a node, it's information can persist in the Gossiper for up
to 3 days, after which time it should be removed.
Are you having issues with a removed node state persisting for longer?
Mark
On Fri, Jul 25, 2014 at 11:33 AM, Rahul Neelakantan ra...@rahul.be wrote:
Is there a way
it still request a full
data read to the node having the most recent time ?
On Fri, Jul 25, 2014 at 11:25 PM, Mark Reddy mark.re...@boxever.com
wrote:
Hi Brian,
A read request will be handled in the following manner:
Once the coordinator receives a read request it will firstly determine
Yes you are correct, Cassandra is often abbreviated as C*. With most
languages and applications being referenced by their acronym /
abbreviation, I guess you just have to pick one that is available. I assume
if someone creates a new language and wants to name it C*, they will see
that it is taken
PlanetCassandra has a collection of migration use cases:
http://planetcassandra.org/mysql-to-cassandra-migration/
http://planetcassandra.org/oracle-to-cassandra-migration/
If they don't contain the information you need I'm sure you could reach out
to the companies involved or DataStax itself to
Hi Kevin,
The difference here is that the Apache Cassandra site is maintained by the
community whereas the DataStax site is maintained by paid employees with a
vested interest in producing documentation.
With DataStax having some comprehensive docs, I guess the desire for people
to maintain the
It won't. Cassandra stores a node's host ID in an end-point to host ID
mapping, each ID must be unique and cannot be changed after the fact.
Mark
On Mon, Jul 21, 2014 at 4:44 PM, John Sanda john.sa...@gmail.com wrote:
Under what circumstances, if any, will a node's host ID change?
- John
Have you setup your security group correctly so that all nodes can
communicate. Is there anything in the logs to suggest nodes could not
communicate to each other?
When you log into the other instances, is Cassandra running correctly?
On Tue, Jul 15, 2014 at 6:28 PM, Lars Schouw
/documentation/cassandra/2.0/cassandra/install/installAMISecurityGroup.html
On Tuesday, July 15, 2014 6:43 PM, Mark Reddy mark.re...@boxever.com
wrote:
Have you setup your security group correctly so that all nodes can
communicate. Is there anything in the logs to suggest nodes could
Hi Carlos,
I have just downloaded 2.1.0-rc3 to validate this and the cassandra.in.sh
contains the correct reference to the jamm-0.2.6.jar
This can also been seen on the trunk:
https://github.com/apache/cassandra/blob/trunk/bin/cassandra.in.sh
I am unsure why you are seeing jamm-0.2.5.jar in
Can you post the output of nodetool status and your Astyanax connection
settings?
On Fri, Jul 11, 2014 at 9:06 PM, Ruchir Jha ruchir@gmail.com wrote:
This is how we create our keyspace. We just ran this command once through
a cqlsh session on one of the nodes, so don't quite understand
= 1.6.0 -a $JVM_PATCH_VERSION -ge 23 ]
then
JAVA_AGENT=$JAVA_AGENT -javaagent:$CASSANDRA_HOME/lib/jamm-0.2.6.jar
fi
On Fri, Jul 11, 2014 at 3:02 PM, Mark Reddy mark.re...@boxever.com
wrote:
Hi Carlos,
I have just downloaded 2.1.0-rc3 to validate this and the cassandra.in.sh
contains
Hi Bhaskar,
Can you check your limits using 'ulimit -a'? The default is 1024, which
needs to be increased if you have not done so already.
Here you will find a list of recommended production settings:
Hi Rameez,
I have never done a migration from vnodes to non-vnodes however I would
imagine that the procedure would be the same as its counterpart. As always
testing in dev should be done first.
To move from vnodes to non-vodes I would add a new datacenter to the
cluster with vnodes disabled and
You should run nodetool ring and specify a keyspace, otherwise the
ownership information will be nonsense.
https://issues.apache.org/jira/browse/CASSANDRA-7173
Mark
On Mon, Jun 30, 2014 at 6:13 PM, S C as...@outlook.com wrote:
When I run nodetoool ring I see the ownership with different
Can you share your schema and the commands you are running?
On Thu, May 15, 2014 at 7:54 PM, mahesh rajamani
rajamani.mah...@gmail.comwrote:
Hi,
I am using Cassandra 2.0.5 version. I trying to setup 2 keyspace with same
tables for different testing. While creating index on the tables, I
Yes, please see http://wiki.apache.org/cassandra/FAQ#dropped_messages for
further details.
Mark
On Fri, May 9, 2014 at 12:52 PM, Raveendran, Varsha IN BLR STS
varsha.raveend...@siemens.com wrote:
Hello,
I am writing around 10Million records continuously into a single node
Cassandra
Hi Boying,
From Datastax documentation:
http://www.datastax.com/documentation/cassandra/1.2/cassandra/architecture/architectureGossipAbout_c.html
The seed node designation has no purpose other than bootstrapping the
gossip process for new nodes joining the cluster. Seed nodes are not a
single
Datastax recommended during a long time (still now ?) to use Java 6
Java 6 is recommended for version 1.2
Java 7 is required for version 2.0
Mark
On Tue, Apr 29, 2014 at 10:19 AM, Alain RODRIGUEZ arodr...@gmail.comwrote:
Looks like it will be like with the version 7... Cassandra has been
If all streams have completed, the node could be still rebuilding secondary
indexes? Try looking at 'nodetool compactionstats' for this.
On Fri, Apr 18, 2014 at 1:05 PM, Phil Burress philburress...@gmail.comwrote:
nodetool netstats shows 84 files. They are all at 100%. Nothing showing in
To get a list of all keyspaces via CQL you can run:
*describe keyspaces *or *select keyspace_name from system.schema_keyspaces;*
On Wed, Apr 16, 2014 at 9:23 AM, Sebastian Schmidt isib...@gmail.comwrote:
Hey
I want to do unit tests for software that uses Cassandra as storage
backend. Using
create keyspace twitter with replication = {'class':'SimpleStrategy',
'replication_factor' : 3}
Your replication factor is your issue here, you have a single node and a
RF=3. For a single node setup your RF should be 1. You can find more info
about replication here:
Mark. does this mean with RF=3, all 3 nodes must be up and running
for CAS updates?
-Vivek
On Wed, Apr 16, 2014 at 6:22 PM, Mark Reddy mark.re...@boxever.comwrote:
create keyspace twitter with replication = {'class':'SimpleStrategy',
'replication_factor' : 3}
Your replication factor
Do you delete and/or set TTLs on your data?
On Wed, Apr 16, 2014 at 2:14 PM, Ruchir Jha ruchir@gmail.com wrote:
Hi,
I am trying to investigate ParNew promotion failures happening routinely
in production. As part of this exercise, I enabled
-XX:PrintHistogramBeforeFullGC and saw the
Datastax have a comprehensive installation and configuration guide here:
http://www.datastax.com/documentation/opscenter/4.1/opsc/install/opscInstallation_g.html
On Tue, Apr 15, 2014 at 9:13 AM, Aravindan T aravinda...@tcs.com wrote:
Hi,
Could anyone please guide me on installation procedure
Hi Will,
You can run 'nodetool upgradesstables', this will rewrite the SSTables and
regenerate the bloom filters for those tables, This will reduce their
usage.
Mark
On Mon, Apr 14, 2014 at 3:16 PM, William Oberman
ober...@civicscience.comwrote:
Ah, so I could change the chance value to
What are you storing these 15 chars as; string, int, double, etc.? 15 chars
does not translate to 15 bytes.
You may be mixing up replication factor and quorum when you say Cassandra
cluster has 3 servers, and data is stored in quorum ( 2 servers ). You
read and write at quorum (N/2)+1 where
numbers?
2) Still it has 1.5X of overall data how can this be resolved and what is
reason for that?
3) Also i see that data is in different size on all nodes , does that
means that servers are out of sync???
Thanks and best regards
Yulian Oifa
On Sun, Apr 13, 2014 at 7:03 PM, Mark Reddy mark.re
Correct, a tombstone will only be removed after gc_grace period has
elapsed. The default value is set to 10 days which allows a great deal of
time for consistency to be achieved prior to deletion. If you are
operationally confident that you can achieve consistency via anti-entropy
repairs within a
, making it likely
I'll have to self manage compactions.
On Fri, Apr 11, 2014 at 10:31 AM, Mark Reddy mark.re...@boxever.comwrote:
Correct, a tombstone will only be removed after gc_grace period has
elapsed. The default value is set to 10 days which allows a great deal of
time
:-)
will
On Fri, Apr 11, 2014 at 11:12 AM, Mark Reddy mark.re...@boxever.comwrote:
Yes, running nodetool compact (major compaction) creates one large
SSTable. This will mess up the heuristics of the SizeTiered strategy (is
this the compaction strategy you are using?) leading to multiple 'small
day for gc_grace_seconds. Would nodetool scrub help? Does nodetool
scrub forces a minor compaction?
Cheers,
Paulo
On Fri, Apr 11, 2014 at 12:12 PM, Mark Reddy mark.re...@boxever.comwrote:
Yes, running nodetool compact (major compaction) creates one large
SSTable. This will mess up
What version are you running? As of 1.2.x you can do the following:
1. Start the cqlsh connected locally to the node.
2. Run:
update system.local set cluster_name='$CLUSTER_NAME' where key='local';
3. Run nodetool flush on the node.
4. Update the cassandra.yaml file on the node, changing the
I would go with option 1.
I think it is the safer of the two options, involves less work and if
something were to go wrong mid migration you can remove the second DC from
your keyspace replication and have a clean break. SimpleStrategy will work
across DCs. It is generally advised to not use it
Hi,
If you want to just secure OpsCenter itself take a look here:
http://www.datastax.com/documentation/opscenter/4.1/opsc/configure/opscAssigningAccessRoles_t.html
If you want to enable internal authentication and still allow OpsCenter
access, you can create an OpsCenter user and once you have
at 11:24 PM, Mark Reddy mark.re...@boxever.comwrote:
Hi,
If you want to just secure OpsCenter itself take a look here:
http://www.datastax.com/documentation/opscenter/4.1/opsc/configure/opscAssigningAccessRoles_t.html
If you want to enable internal authentication and still allow OpsCenter
93 matches
Mail list logo