You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Mradul Maheshwari <mr...@apporbit.com> on 2016/06/10 04:17:23 UTC
Empty snapshot created
Hi,
I am facing an issue when taking snapshots.
The details of the setup are as follows
1. Cassandra Version 3.5
2. I have a keyspace named *other_map* with '*NetworkTopologyStrategy*'
and replication factor 1 for 'dc1'
3. Added another datacenter 'dc2' in the existing cluster
4. Modified other_map keyspace using the *ALTER* command.
5. After this Logged on on the node on dc2 datacenter and issued
the *nodetool
snapshot* command for the other_map keyspace.
6. As a result a directory is created in the other_keyspace/<table
name>/snapshot/<time-stamp>. This contains only a manifest,json file which
has no information about any files.
<cat content of manifest.json>
*cat
data/data/other_map/country-f34a28d02b1511e689afc7a4a4b2ee40/snapshots/1465457086678/manifest.json*
*{"files":[]}*
</cat content of manifest.json>
Am I missing any thing here? Are the above mentioned steps complete?
After altering the keyspace I have tried a *nodetool repair* command which
had also not changed anything.
Regards,
Mradul
Information about schema follows
CREATE KEYSPACE other_map WITH replication = {'class':
'NetworkTopologyStrategy', 'dc': '1', 'dc2': '2'} AND durable_writes =
true;
CREATE TABLE other_map.country (
id int PRIMARY KEY,
name text,
states int
) WITH bloom_filter_fp_chance = 0.01
AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
AND comment = ''
AND compaction = {'class':
'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
'max_threshold': '32', 'min_threshold': '4'}
AND compression = {'chunk_length_in_kb': '64', 'class':
'org.apache.cassandra.io.compress.LZ4Compressor'}
AND crc_check_chance = 1.0
AND dclocal_read_repair_chance = 0.1
AND default_time_to_live = 0
AND gc_grace_seconds = 864000
AND max_index_interval = 2048
AND memtable_flush_period_in_ms = 0
AND min_index_interval = 128
AND read_repair_chance = 0.0
AND speculative_retry = '99PERCENTILE';
Re: Empty snapshot created
Posted by Mradul Maheshwari <mr...@apporbit.com>.
Hi Ben,
Many thanks.
I had tried this command earlier too but I guess my syntax was wrong. This
time I just issued
nodetool rebuild dc1
and took the snapshot after this. I could see the *.db files created.
Earlier I was trying
nodetool rebuild -- dc1
which I guess was wrong.
Thanks for the lightning response.
Regards,
Mradul
On Fri, Jun 10, 2016 at 9:52 AM, Ben Slater <be...@instaclustr.com>
wrote:
> After adding a DC you need to run nodetool rebuild. See the procedure
> here:
> https://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_add_dc_to_cluster_t.html
>
> Cheers
> Ben
>
> On Fri, 10 Jun 2016 at 14:17 Mradul Maheshwari <mr...@apporbit.com>
> wrote:
>
>> Hi,
>> I am facing an issue when taking snapshots.
>>
>> The details of the setup are as follows
>>
>> 1. Cassandra Version 3.5
>> 2. I have a keyspace named *other_map* with '*NetworkTopologyStrategy*'
>> and replication factor 1 for 'dc1'
>> 3. Added another datacenter 'dc2' in the existing cluster
>> 4. Modified other_map keyspace using the *ALTER* command.
>> 5. After this Logged on on the node on dc2 datacenter and issued the *nodetool
>> snapshot* command for the other_map keyspace.
>> 6. As a result a directory is created in the other_keyspace/<table
>> name>/snapshot/<time-stamp>. This contains only a manifest,json file which
>> has no information about any files.
>>
>> <cat content of manifest.json>
>> *cat
>> data/data/other_map/country-f34a28d02b1511e689afc7a4a4b2ee40/snapshots/1465457086678/manifest.json*
>>
>> *{"files":[]}*
>>
>> </cat content of manifest.json>
>>
>> Am I missing any thing here? Are the above mentioned steps complete?
>>
>> After altering the keyspace I have tried a *nodetool repair* command
>> which had also not changed anything.
>>
>> Regards,
>> Mradul
>>
>>
>> Information about schema follows
>>
>> CREATE KEYSPACE other_map WITH replication = {'class':
>> 'NetworkTopologyStrategy', 'dc': '1', 'dc2': '2'} AND durable_writes =
>> true;
>>
>> CREATE TABLE other_map.country (
>> id int PRIMARY KEY,
>> name text,
>> states int
>> ) WITH bloom_filter_fp_chance = 0.01
>> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
>> AND comment = ''
>> AND compaction = {'class':
>> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
>> 'max_threshold': '32', 'min_threshold': '4'}
>> AND compression = {'chunk_length_in_kb': '64', 'class':
>> 'org.apache.cassandra.io.compress.LZ4Compressor'}
>> AND crc_check_chance = 1.0
>> AND dclocal_read_repair_chance = 0.1
>> AND default_time_to_live = 0
>> AND gc_grace_seconds = 864000
>> AND max_index_interval = 2048
>> AND memtable_flush_period_in_ms = 0
>> AND min_index_interval = 128
>> AND read_repair_chance = 0.0
>> AND speculative_retry = '99PERCENTILE';
>>
>> --
> ————————
> Ben Slater
> Chief Product Officer, Instaclustr
> +61 437 929 798
>
Re: Empty snapshot created
Posted by Ben Slater <be...@instaclustr.com>.
After adding a DC you need to run nodetool rebuild. See the procedure here:
https://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_add_dc_to_cluster_t.html
Cheers
Ben
On Fri, 10 Jun 2016 at 14:17 Mradul Maheshwari <mr...@apporbit.com> wrote:
> Hi,
> I am facing an issue when taking snapshots.
>
> The details of the setup are as follows
>
> 1. Cassandra Version 3.5
> 2. I have a keyspace named *other_map* with '*NetworkTopologyStrategy*'
> and replication factor 1 for 'dc1'
> 3. Added another datacenter 'dc2' in the existing cluster
> 4. Modified other_map keyspace using the *ALTER* command.
> 5. After this Logged on on the node on dc2 datacenter and issued the *nodetool
> snapshot* command for the other_map keyspace.
> 6. As a result a directory is created in the other_keyspace/<table
> name>/snapshot/<time-stamp>. This contains only a manifest,json file which
> has no information about any files.
>
> <cat content of manifest.json>
> *cat
> data/data/other_map/country-f34a28d02b1511e689afc7a4a4b2ee40/snapshots/1465457086678/manifest.json*
>
> *{"files":[]}*
>
> </cat content of manifest.json>
>
> Am I missing any thing here? Are the above mentioned steps complete?
>
> After altering the keyspace I have tried a *nodetool repair* command
> which had also not changed anything.
>
> Regards,
> Mradul
>
>
> Information about schema follows
>
> CREATE KEYSPACE other_map WITH replication = {'class':
> 'NetworkTopologyStrategy', 'dc': '1', 'dc2': '2'} AND durable_writes =
> true;
>
> CREATE TABLE other_map.country (
> id int PRIMARY KEY,
> name text,
> states int
> ) WITH bloom_filter_fp_chance = 0.01
> AND caching = {'keys': 'ALL', 'rows_per_partition': 'NONE'}
> AND comment = ''
> AND compaction = {'class':
> 'org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy',
> 'max_threshold': '32', 'min_threshold': '4'}
> AND compression = {'chunk_length_in_kb': '64', 'class':
> 'org.apache.cassandra.io.compress.LZ4Compressor'}
> AND crc_check_chance = 1.0
> AND dclocal_read_repair_chance = 0.1
> AND default_time_to_live = 0
> AND gc_grace_seconds = 864000
> AND max_index_interval = 2048
> AND memtable_flush_period_in_ms = 0
> AND min_index_interval = 128
> AND read_repair_chance = 0.0
> AND speculative_retry = '99PERCENTILE';
>
> --
————————
Ben Slater
Chief Product Officer, Instaclustr
+61 437 929 798