where a restart considers the old tables to be live.
>
> On Jul 6, 2015, at 1:51 PM, Robert Coli wrote:
>
> On Mon, Jul 6, 2015 at 1:46 PM, Jeff Williams
> wrote:
>
>> 1) Cassandra version is 2.0.12.
>>
>
>
>> 2) Interesting. Looking at JMX org
Anton,
I have also seen this issue with decommissioned nodes remaining in the
system.peers table.
On the bright side, they can be safely removed from the system.peers table
without issue. You will have to check every node in the cluster since this
is a local setting per node.
Jeff
On 6 July 201
the same JMX attributes are:
LiveDiskSpaceUsed: 55681040579, i.e. ~55GB
LiveSSTableCount: 8
TotalDiskSpaceUsed: 55681040579, i.e. ~55GB
So some of my non-live tables are back live again, and obviously some of
the big ones!!
Jef
On 6 July 2015 at 20:26, Robert Coli wrote:
> On Mon, Jul 6, 2015 at 7:25 AM, J
Hi,
I have a keyspace which is using about 19GB on most nodes in the cluster.
However on one node the data directory for the only table in that keyspace
now uses 52GB. It seems that old sstables are not removed after compaction.
Here is a view of the data directory Data files before compaction (I
Restarting this node removed the decommissioned node from gossip.
Jeff
On 3 July 2015 at 13:09, Jeff Williams wrote:
> I'm thinking I'll have to find something similar for 2.0. I just don't
> understand where the node is coming from!
>
> Jeff
>
> On 1 July 201
ast in version 1.2
>
> http://docs.datastax.com/en/cassandra/1.2/cassandra/architecture/architectureGossipPurge_t.html
>
> the trick was to add -Dcassandra.load_ring_state=false somehow to the jvm
> parameters
>
> I'm not sure if it works for 2.0 (since it's not in the doc for 2.x)
only read when cassandra starts but updating the seed list to live nodes
> and then doing a roiling restart fixed this issue for me.
> I hope this helps you.
>
> Thanks
>
> Sent from my iPhone
>
> On Jun 30, 2015, at 4:42 AM, Jeff Williams
> wrote:
>
> Hi,
>
>
Hi,
I have a cluster which had 4 datacenters running 2.0.12. Last week one of
the datacenters was decommissioned using nodetool decommission on each of
the servers in turn. This seemed to work fine until one of the nodes
started appearing in the logs of all of the remaining servers with messages
l
Hi,
It doesn't look like this is possible, but can I select all rows missing a
certain column? The equivalent of "select * where col is null" in SQL.
Regards,
Jeff
You should be able to get most of this information from the datastax
documentation, e.g. http://www.datastax.com/docs/1.0/references/cql/index for
version 1.0.
Jeff
On Jun 20, 2012, at 1:47 PM, Thierry Templier wrote:
> Hello,
>
> I'm using cqlsh tool to create column families and it works fi
On May 30, 2012, at 10:32 PM, Edward Capriolo wrote:
>
> The snitch does use the datacenter and the rack but almost all
> deployments use a single rack per DC, because when you have more then
> one rack in a data center the NTS snitch has some logic to spread the
> data between racks. (most peop
First, note that replication is done at the row level, not at the node level.
That line should look more like:
placement_strategy = 'NetworkTopologyStrategy' and strategy_options = {DC1:
1,DC2: 1,DC3: 1 }
This means that each row will have one copy in each DC and within each DC it's
placement
I've used java-package under Debian (http://wiki.debian.org/JavaPackage) which
turns your download from Oracle into a .deb. This may work on Ubuntu as well.
On May 14, 2012, at 11:19 PM, aaron morton wrote:
> To get the latest sun java 6 JRE on a ubuntu machine using apt-get I've used
> the ins
Conan,
Good to see I'm not alone in this! I just set up a fresh test cluster. I first
did a fresh install of 1.1.0 and was able to replicate the issue. I then did a
fresh install using 1.0.10 and didn't see the issue. So it looks like rolling
back to 1.0.10 could be the answer for now.
Jeff
O
his is
> definitively a bug and it's be easier to follow up there.
>
> Did you try restarting the node on which you try the create keyspace?
>
> --
> Sylvain
>
> On Thu, May 3, 2012 at 8:43 PM, Jeff Williams
> wrote:
>> As a follow up, I am running version 1.1
As a follow up, I am running version 1.1 and have tried nodetool repair,
cleanup, compact. I can create other keyspaces, but still can't create a
keyspace called PlayLog even though it is not listed anywhere.
On May 3, 2012, at 6:35 PM, Jeff Williams wrote:
> Hi,
>
> I'
.
On Apr 4, 2012, at 9:11 AM, Jeff Williams wrote:
> On three machines on the same subnet as the two cassandra nodes.
>
> On Apr 3, 2012, at 6:40 PM, Collard, David L (Dave) wrote:
>
>> Where is your client running?
>>
>> -Original Message-
>
Hi,
I'm doing testing and wanted to drop a keyspace (with a column family) to
re-add it with a different strategy. So I ran in cqlsh:
DROP KEYSPACE PlayLog;
CREATE KEYSPACE PlayLog WITH strategy_class = 'SimpleStrategy'
AND strategy_options:replication_factor = 2;
And everything seemed to be
On three machines on the same subnet as the two cassandra nodes.
On Apr 3, 2012, at 6:40 PM, Collard, David L (Dave) wrote:
> Where is your client running?
>
> -Original Message-
> From: Jeff Williams [mailto:je...@wherethebitsroam.com]
> Sent: Tuesday, April 03, 201
Apr 3, 2012, at 4:08 PM, Vitalii Tymchyshyn wrote:
> Note that having tons of TCP connections is not good. We are using async
> client to issue multiple calls over single connection at same time. You can
> do the same.
>
> Best regards, Vitalii Tymchyshyn.
>
> 03.04.12 16:18
eff,
>
> Writing serially over one connection will be slower. If you run many threads
> hitting the server at once you will see throughput improve.
>
> Jake
>
>
>
> On Apr 3, 2012, at 7:08 AM, Jeff Williams wrote:
>
>> Hi,
>>
>> I am
Hi,
I am looking at cassandra for a logging application. We currently log to a
Postgresql database.
I set up 2 cassandra servers for testing. I did a benchmark where I had 100
hashes representing logs entries, read from a json file. I then looped over
these to do 10,000 log inserts. I repeated
22 matches
Mail list logo
