Hi, All,
I need to remove a Cassandra data center from a set of connected Cassandra data
centers (I use Cassandra 2.0.7).
I found a related document at
http://www.datastax.com/documentation/cassandra/2.0/cassandra/operations/ops_decomission_dc_t.html
But I need to do these in my Java programs.
Hi,
We need to retrieve the data stored in cassandra on something different
than its "natural" order; we are looking for possible ways to sort results
from a column family data based on columns that are not part of the primary
key; is denormalizing the data on another column family the only option
Hi all,
I have a small cluster (2 nodes RF 2) running with C* 2.0.6 on I2 Extra
Large (AWS) with SSD disk,
the nodetool tpstats shows many MemtablePostFlusher pending and FlushWriter
All time blocked.
The two nodes have the default configuration. All CF use size-tiered
compaction strategy.
Ther
When I start Cassandra AMI cluster with 4 nodes on AWS and open the OpsCenter
there is only one node shown. I followed the doc
http://www.datastax.com/documentation/cassandra/2.0/cassandra/install/installAMILaunch.html
I choose
Region AMI
us-east-1 ami-ada2b6c4
I set the number of Ec2 ins
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 wrote:
> When
FWIW I was able to work around this problem by having my code run the
following loop:
while (the index doesn't exit and we haven't hit our limit of number of tries):
try to create the index
read from system.schema_columns to see if the index exists
if so, then break
if not, pause 5
As far as I know, schema propagation always takes some times in the
cluster. On this mailing list some people in the past faced similar
behavior.
On Tue, Jul 15, 2014 at 8:20 PM, Clint Kelly wrote:
> FWIW I was able to work around this problem by having my code run the
> following loop:
>
> whi
Hi DuyHai,
Thanks for the response. Is the recommended best practice therefore
to do what I describe above?
Is there some way to get the driver to block until the schema code has
propagated everywhere? My currently solution feels rather janky!
Thanks!
Best regards,
Clint
On Tue, Jul 15, 201
Good to hear.
Mark
On Tue, Jul 15, 2014 at 8:16 PM, Lars Schouw wrote:
> Yes, it works when setting the security group so all traffic is allowed
> from anywhere.
>
> I also found the doc that tells me how to add the more restrictive
> security
> http://www.datastax.com/documentation/cassandra
Yes, it works when setting the security group so all traffic is allowed from
anywhere.
I also found the doc that tells me how to add the more restrictive security
http://www.datastax.com/documentation/cassandra/2.0/cassandra/install/installAMISecurityGroup.html
On Tuesday, July 15, 2014 6:4
I have seen this behavour when Commitlog files got deleted (or permissions
were set to read only).
MemtablePostFlusher is the stage that marks the Commitlog as flushed. When
they fail it usually means there is something wrong with the commitlog
files.
Check your logfiles for any commitlog related
Number of compactions can spike for perfectly reasonable scenarios (ie after a
repair or bootstrap) so no matter what you set it to there will likely be
periodic false alarms.
I would however put a number "15" on the limit of any thread pool backlog as
matter of principle until woken up too m
The MemtablePostFlusher is also used for flushing non-cf backed (solr) indexes.
Are you using DSE and solr by chance?
Chris
On Jul 15, 2014, at 5:01 PM, horschi wrote:
> I have seen this behavour when Commitlog files got deleted (or permissions
> were set to read only).
>
> MemtablePostFlus
13 matches
Mail list logo
