Re: Inconsistent data after adding a new DC and rebuilding

[Víctor Pérez Pereira]

zx

El abr. 10, 2017 12:12 PM, "George Sigletos" 
escribió:

> In 3 out of 5 nodes of our new DC the rebuild process finished
> successfully. In the other two nodes not (the process was hanging doing
> nothing) so we killed it, removed all data and started again. This time
> finished successfully.
>
> Here is the netstats output of one of the new newly added nodes:
>
> Mode: NORMAL
> Not sending any streams.
> Read Repair Statistics:
> Attempted: 269142
> Mismatch (Blocking): 169866
> Mismatch (Background): 4
> Pool NameActive   Pending  Completed   Dropped
> Commandsn/a 2   10031126  1935
> Responses   n/a97   22565129   n/a
>
>
> On Mon, Apr 10, 2017 at 5:28 PM, Roland Otta 
> wrote:
>
>> Hi,
>>
>> we have seen similar issues here.
>>
>> have you verified that your rebuilds have been finished successfully? we
>> have seen rebuilds that stopped streaming and working but have not finished.
>> what does nodetool netstats output for your newly built up nodes?
>>
>> br,
>> roland
>>
>>
>> On Mon, 2017-04-10 at 17:15 +0200, George Sigletos wrote:
>>
>> Hello,
>>
>> We recently added a new datacenter to our cluster and run "nodetool
>> rebuild -- " in all 5 new nodes, one by one.
>>
>> After this process finished we noticed there is data missing from the new
>> datacenter, although it exists on the current one.
>>
>> How would that be possible? Should I maybe have run repair in all nodes
>> of the current DC before adding the new one?
>>
>> Running Cassandra 2.1.15
>>
>> Kind regards,
>> George
>>
>>
>>
>>
>

RE: Node always dieing

[Hartmut Inerle]

Hi,

There is an invalid IP in the String.
.SimpleSeedProvider{seeds=10.100.100.19, 10.100.100.85, 10.100.100.185, 
10.100.100.161, 10.100.100.52, 10.100.1000.213};

Regards
  Hartmut


From: Chris Mawata [mailto:chris.maw...@gmail.com]
Sent: Montag, 10. April 2017 13:37
To: user@cassandra.apache.org
Subject: Re: Node always dieing

Notice
.SimpleSeedProvider{seeds=10.100.100.19, 10.100.100.85, 10.100.100.185, 
10.100.100.161, 10.100.100.52, 10.100.1000.213};
Why do you have all six of your nodes as seeds? is it possible that the last 
one you added used itself as the seed and is isolated?

On Thu, Apr 6, 2017 at 6:48 AM, Cogumelos Maravilha 
> wrote:

Yes C* is running as cassandra:

cassand+  2267 1 99 10:18 ?00:02:56 java 
-Xloggc:/var/log/cassandra/gc.log -ea -XX:+UseThreadPriorities -XX:Threa...

INFO  [main] 2017-04-06 10:35:42,956 Config.java:474 - Node 
configuration:[allocate_tokens_for_keyspace=null; 
authenticator=PasswordAuthenticator; authorizer=CassandraAuthorizer; 
auto_bootstrap=true; auto_snapshot=true; back_pressure_enabled=false; 
back_pressure_strategy=org.apache.cassandra.net.RateBasedBackPressure{high_ratio=0.9,
 factor=5, flow=FAST}; batch_size_fail_threshold_in_kb=50; 
batch_size_warn_threshold_in_kb=5; batchlog_replay_throttle_in_kb=1024; 
broadcast_address=null; broadcast_rpc_address=null; 
buffer_pool_use_heap_if_exhausted=true; cas_contention_timeout_in_ms=600; 
cdc_enabled=false; cdc_free_space_check_interval_ms=250; 
cdc_raw_directory=null; cdc_total_space_in_mb=0; 
client_encryption_options=; cluster_name=company; 
column_index_cache_size_in_kb=2; column_index_size_in_kb=64; 
commit_failure_policy=ignore; commitlog_compression=null; 
commitlog_directory=/mnt/cassandra/commitlog; 
commitlog_max_compression_buffers_in_pool=3; commitlog_periodic_queue_size=-1; 
commitlog_segment_size_in_mb=32; commitlog_sync=periodic; 
commitlog_sync_batch_window_in_ms=NaN; commitlog_sync_period_in_ms=1; 
commitlog_total_space_in_mb=null; 
compaction_large_partition_warning_threshold_mb=100; 
compaction_throughput_mb_per_sec=16; concurrent_compactors=null; 
concurrent_counter_writes=32; concurrent_materialized_view_writes=32; 
concurrent_reads=32; concurrent_replicates=null; concurrent_writes=32; 
counter_cache_keys_to_save=2147483647; counter_cache_save_period=7200; 
counter_cache_size_in_mb=null; counter_write_request_timeout_in_ms=600; 
credentials_cache_max_entries=1000; credentials_update_interval_in_ms=-1; 
credentials_validity_in_ms=2000; cross_node_timeout=false; 
data_file_directories=[Ljava.lang.String;@223f3642; disk_access_mode=auto; 
disk_failure_policy=ignore; disk_optimization_estimate_percentile=0.95; 
disk_optimization_page_cross_chance=0.1; disk_optimization_strategy=ssd; 
dynamic_snitch=true; dynamic_snitch_badness_threshold=0.1; 
dynamic_snitch_reset_interval_in_ms=60; 
dynamic_snitch_update_interval_in_ms=100; 
enable_scripted_user_defined_functions=false; 
enable_user_defined_functions=false; 
enable_user_defined_functions_threads=true; encryption_options=null; 
endpoint_snitch=SimpleSnitch; file_cache_size_in_mb=null; 
gc_log_threshold_in_ms=200; gc_warn_threshold_in_ms=1000; 
hinted_handoff_disabled_datacenters=[]; hinted_handoff_enabled=true; 
hinted_handoff_throttle_in_kb=1024; hints_compression=null; 
hints_directory=/mnt/cassandra/hints; hints_flush_period_in_ms=1; 
incremental_backups=false; index_interval=null; 
index_summary_capacity_in_mb=null; index_summary_resize_interval_in_minutes=60; 
initial_token=null; inter_dc_stream_throughput_outbound_megabits_per_sec=200; 
inter_dc_tcp_nodelay=false; internode_authenticator=null; 
internode_compression=dc; internode_recv_buff_size_in_bytes=0; 
internode_send_buff_size_in_bytes=0; key_cache_keys_to_save=2147483647; 
key_cache_save_period=14400; key_cache_size_in_mb=null; 
listen_address=10.100.100.213; listen_interface=null; 
listen_interface_prefer_ipv6=false; listen_on_broadcast_address=false; 
max_hint_window_in_ms=1080; max_hints_delivery_threads=2; 
max_hints_file_size_in_mb=128; max_mutation_size_in_kb=null; 
max_streaming_retries=3; max_value_size_in_mb=256; 
memtable_allocation_type=heap_buffers; memtable_cleanup_threshold=null; 
memtable_flush_writers=0; memtable_heap_space_in_mb=null; 
memtable_offheap_space_in_mb=null; min_free_space_per_drive_in_mb=50; 
native_transport_max_concurrent_connections=-1; 
native_transport_max_concurrent_connections_per_ip=-1; 
native_transport_max_frame_size_in_mb=256; native_transport_max_threads=128; 
native_transport_port=9042; native_transport_port_ssl=null; num_tokens=256; 
otc_coalescing_strategy=TIMEHORIZON; otc_coalescing_window_us=200; 
partitioner=org.apache.cassandra.dht.Murmur3Partitioner; 
permissions_cache_max_entries=1000; permissions_update_interval_in_ms=-1; 
permissions_validity_in_ms=2000; phi_convict_threshold=8.0; 

Re: Inconsistent data after adding a new DC and rebuilding

[George Sigletos]

In 3 out of 5 nodes of our new DC the rebuild process finished
successfully. In the other two nodes not (the process was hanging doing
nothing) so we killed it, removed all data and started again. This time
finished successfully.

Here is the netstats output of one of the new newly added nodes:

Mode: NORMAL
Not sending any streams.
Read Repair Statistics:
Attempted: 269142
Mismatch (Blocking): 169866
Mismatch (Background): 4
Pool NameActive   Pending  Completed   Dropped
Commandsn/a 2   10031126  1935
Responses   n/a97   22565129   n/a


On Mon, Apr 10, 2017 at 5:28 PM, Roland Otta 
wrote:

> Hi,
>
> we have seen similar issues here.
>
> have you verified that your rebuilds have been finished successfully? we
> have seen rebuilds that stopped streaming and working but have not finished.
> what does nodetool netstats output for your newly built up nodes?
>
> br,
> roland
>
>
> On Mon, 2017-04-10 at 17:15 +0200, George Sigletos wrote:
>
> Hello,
>
> We recently added a new datacenter to our cluster and run "nodetool
> rebuild -- " in all 5 new nodes, one by one.
>
> After this process finished we noticed there is data missing from the new
> datacenter, although it exists on the current one.
>
> How would that be possible? Should I maybe have run repair in all nodes of
> the current DC before adding the new one?
>
> Running Cassandra 2.1.15
>
> Kind regards,
> George
>
>
>
>

Re: Inconsistent data after adding a new DC and rebuilding

[Roland Otta]

Hi,

we have seen similar issues here.

have you verified that your rebuilds have been finished successfully? we have 
seen rebuilds that stopped streaming and working but have not finished.
what does nodetool netstats output for your newly built up nodes?

br,
roland


On Mon, 2017-04-10 at 17:15 +0200, George Sigletos wrote:
Hello,

We recently added a new datacenter to our cluster and run "nodetool rebuild -- 
" in all 5 new nodes, one by one.

After this process finished we noticed there is data missing from the new 
datacenter, although it exists on the current one.

How would that be possible? Should I maybe have run repair in all nodes of the 
current DC before adding the new one?

Running Cassandra 2.1.15

Kind regards,
George

Inconsistent data after adding a new DC and rebuilding

[George Sigletos]

Hello,

We recently added a new datacenter to our cluster and run "nodetool rebuild
-- " in all 5 new nodes, one by one.

After this process finished we noticed there is data missing from the new
datacenter, although it exists on the current one.

How would that be possible? Should I maybe have run repair in all nodes of
the current DC before adding the new one?

Running Cassandra 2.1.15

Kind regards,
George

Re: Migrating from Datastax Distribution to Apache Cassandra

[Michael Shuler]

Changes between 3.7 and 3.10? Yes, massive changes. Read NEWS.txt and
CHANGES.txt with every upgrade. Test upgrades in staging.

-- 
Kind regards,
Michael

On 04/10/2017 02:02 AM, Eren Yilmaz wrote:
> Thanks Michael,
> 
> Are there any data changes that I need to worry about?
> 
> Eren 
> 
> -Original Message-
> From: Michael Shuler [mailto:mshu...@pbandjelly.org] On Behalf Of Michael 
> Shuler
> Sent: Friday, April 7, 2017 9:20 PM
> To: user@cassandra.apache.org
> Subject: Re: Migrating from Datastax Distribution to Apache Cassandra
> 
> Example DDC 3.7.0 to Apache Cassandra 3.10 upgrade with all default configs, 
> no data, and both the DDC and Apache Cassandra lines in sources.list (sorry 
> for any weird wrapping, but I think the list strips
> attachments):
> 
> mshuler@hana:~$ apt-cache policy datastax-ddc cassandra
> datastax-ddc:
>   Installed: (none)
>   Candidate: 3.7.0
>   Version table:
>  3.7.0 0
> 500 https://debian.datastax.com/datastax-ddc/ 3.7/main amd64 Packages
> cassandra:
>   Installed: (none)
>   Candidate: 3.10
>   Version table:
>  3.10 0
> 500 http://www.apache.org/dist/cassandra/debian/ 310x/main amd64 
> Packages mshuler@hana:~$ mshuler@hana:~$ sudo apt-get install datastax-ddc 
> Reading package lists... Done Building dependency tree Reading state 
> information... Done The following extra packages will be installed:
>   datastax-ddc-tools
> The following NEW packages will be installed:
>   datastax-ddc datastax-ddc-tools
> 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
> Need to get 28.4 MB of archives.
> After this operation, 38.0 MB of additional disk space will be used.
> Do you want to continue? [Y/n]
> Get:1 https://debian.datastax.com/datastax-ddc/ 3.7/main datastax-ddc all 
> 3.7.0 [28.4 MB]
> Get:2 https://debian.datastax.com/datastax-ddc/ 3.7/main datastax-ddc-tools 
> all 3.7.0 [4,484 B] Fetched 28.4 MB in 3s (8,210 kB/s) Selecting previously 
> unselected package datastax-ddc.
> (Reading database ... 171852 files and directories currently installed.) 
> Preparing to unpack .../datastax-ddc_3.7.0_all.deb ...
> Unpacking datastax-ddc (3.7.0) ...
> Selecting previously unselected package datastax-ddc-tools.
> Preparing to unpack .../datastax-ddc-tools_3.7.0_all.deb ...
> Unpacking datastax-ddc-tools (3.7.0) ...
> Processing triggers for systemd (215-17+deb8u6) ...
> Setting up datastax-ddc (3.7.0) ...
> vm.max_map_count = 1048575
> net.ipv4.tcp_keepalive_time = 300
> update-rc.d: warning: start and stop actions are no longer supported; falling 
> back to defaults Setting up datastax-ddc-tools (3.7.0) ...
> Processing triggers for systemd (215-17+deb8u6) ...
> mshuler@hana:~$
> mshuler@hana:~$ sudo apt-get install cassandra cassandra-tools Reading 
> package lists... Done Building dependency tree Reading state information... 
> Done The following packages will be REMOVED:
>   datastax-ddc datastax-ddc-tools
> The following NEW packages will be installed:
>   cassandra cassandra-tools
> 0 upgraded, 2 newly installed, 2 to remove and 0 not upgraded.
> Need to get 29.2 MB of archives.
> After this operation, 939 kB of additional disk space will be used.
> Do you want to continue? [Y/n]
> Get:1 http://www.apache.org/dist/cassandra/debian/ 310x/main cassandra all 
> 3.10 [29.2 MB]
> Get:2 http://www.apache.org/dist/cassandra/debian/ 310x/main cassandra-tools 
> all 3.10 [4,558 B] Fetched 29.2 MB in 2s (13.6 MB/s) (Reading database ... 
> 172046 files and directories currently installed.) Removing 
> datastax-ddc-tools (3.7.0) ...
> Removing datastax-ddc (3.7.0) ...
> Selecting previously unselected package cassandra.
> (Reading database ... 171870 files and directories currently installed.) 
> Preparing to unpack .../cassandra_3.10_all.deb ...
> Unpacking cassandra (3.10) ...
> Selecting previously unselected package cassandra-tools.
> Preparing to unpack .../cassandra-tools_3.10_all.deb ...
> Unpacking cassandra-tools (3.10) ...
> Processing triggers for systemd (215-17+deb8u6) ...
> Setting up cassandra (3.10) ...
> Installing new version of config file /etc/cassandra/cassandra-env.sh ...
> Installing new version of config file /etc/cassandra/cassandra.yaml ...
> Installing new version of config file /etc/cassandra/jvm.options ...
> Installing new version of config file /etc/cassandra/logback-tools.xml ...
> Installing new version of config file /etc/cassandra/logback.xml ...
> vm.max_map_count = 1048575
> net.ipv4.tcp_keepalive_time = 300
> update-rc.d: warning: start and stop actions are no longer supported; falling 
> back to defaults Setting up cassandra-tools (3.10) ...
> mshuler@hana:~$
> 
> --
> Warm regards,
> Michael
> 

Re: Node always dieing

[Cogumelos Maravilha]

No.

nodetool status, nodetool describecluster also nodetool ring shows a
correct cluster.

Not all nodes needs to be a seed, but can be.

I had also ALTER KEYSPACE system_auth WITH REPLICATION = { 'class' :
'SimpleStrategy', 'replication_factor' : 6 } AND durable_writes = false;

And the first command on the new node was  |nodetool repair system_auth|


On 04/10/2017 12:37 PM, Chris Mawata wrote:
> Notice
> .SimpleSeedProvider{seeds=10.100.100.19, 10.100.100.85,
> 10.100.100.185, 10.100.100.161, 10.100.100.52, 10.100.1000.213};
>
> Why do you have all six of your nodes as seeds? is it possible that
> the last one you added used itself as the seed and is isolated?
>
> On Thu, Apr 6, 2017 at 6:48 AM, Cogumelos Maravilha
> > wrote:
>
> Yes C* is running as cassandra:
>
> cassand+  2267 1 99 10:18 ?00:02:56 java
> -Xloggc:/var/log/cassandra/gc.log -ea -XX:+UseThreadPriorities
> -XX:Threa...
>
> INFO  [main] 2017-04-06 10:35:42,956 Config.java:474 - Node
> configuration:[allocate_tokens_for_keyspace=null;
> authenticator=PasswordAuthenticator;
> authorizer=CassandraAuthorizer; auto_bootstrap=true;
> auto_snapshot=true; back_pressure_enabled=false;
> back_pressure_strategy=org.apache.cassandra.net
> .RateBasedBackPressure{high_ratio=0.9,
> factor=5, flow=FAST}; batch_size_fail_threshold_in_kb=50;
> batch_size_warn_threshold_in_kb=5;
> batchlog_replay_throttle_in_kb=1024; broadcast_address=null;
> broadcast_rpc_address=null;
> buffer_pool_use_heap_if_exhausted=true;
> cas_contention_timeout_in_ms=600; cdc_enabled=false;
> cdc_free_space_check_interval_ms=250; cdc_raw_directory=null;
> cdc_total_space_in_mb=0; client_encryption_options=;
> cluster_name=company; column_index_cache_size_in_kb=2;
> column_index_size_in_kb=64; commit_failure_policy=ignore;
> commitlog_compression=null;
> commitlog_directory=/mnt/cassandra/commitlog;
> commitlog_max_compression_buffers_in_pool=3;
> commitlog_periodic_queue_size=-1; commitlog_segment_size_in_mb=32;
> commitlog_sync=periodic; commitlog_sync_batch_window_in_ms=NaN;
> commitlog_sync_period_in_ms=1;
> commitlog_total_space_in_mb=null;
> compaction_large_partition_warning_threshold_mb=100;
> compaction_throughput_mb_per_sec=16; concurrent_compactors=null;
> concurrent_counter_writes=32;
> concurrent_materialized_view_writes=32; concurrent_reads=32;
> concurrent_replicates=null; concurrent_writes=32;
> counter_cache_keys_to_save=2147483647;
> counter_cache_save_period=7200; counter_cache_size_in_mb=null;
> counter_write_request_timeout_in_ms=600;
> credentials_cache_max_entries=1000;
> credentials_update_interval_in_ms=-1;
> credentials_validity_in_ms=2000; cross_node_timeout=false;
> data_file_directories=[Ljava.lang.String;@223f3642;
> disk_access_mode=auto; disk_failure_policy=ignore;
> disk_optimization_estimate_percentile=0.95;
> disk_optimization_page_cross_chance=0.1;
> disk_optimization_strategy=ssd; dynamic_snitch=true;
> dynamic_snitch_badness_threshold=0.1;
> dynamic_snitch_reset_interval_in_ms=60;
> dynamic_snitch_update_interval_in_ms=100;
> enable_scripted_user_defined_functions=false;
> enable_user_defined_functions=false;
> enable_user_defined_functions_threads=true;
> encryption_options=null; endpoint_snitch=SimpleSnitch;
> file_cache_size_in_mb=null; gc_log_threshold_in_ms=200;
> gc_warn_threshold_in_ms=1000;
> hinted_handoff_disabled_datacenters=[];
> hinted_handoff_enabled=true; hinted_handoff_throttle_in_kb=1024;
> hints_compression=null; hints_directory=/mnt/cassandra/hints;
> hints_flush_period_in_ms=1; incremental_backups=false;
> index_interval=null; index_summary_capacity_in_mb=null;
> index_summary_resize_interval_in_minutes=60; initial_token=null;
> inter_dc_stream_throughput_outbound_megabits_per_sec=200;
> inter_dc_tcp_nodelay=false; internode_authenticator=null;
> internode_compression=dc; internode_recv_buff_size_in_bytes=0;
> internode_send_buff_size_in_bytes=0;
> key_cache_keys_to_save=2147483647; key_cache_save_period=14400;
> key_cache_size_in_mb=null; listen_address=10.100.100.213;
> listen_interface=null; listen_interface_prefer_ipv6=false;
> listen_on_broadcast_address=false; max_hint_window_in_ms=1080;
> max_hints_delivery_threads=2; max_hints_file_size_in_mb=128;
> max_mutation_size_in_kb=null; max_streaming_retries=3;
> max_value_size_in_mb=256; memtable_allocation_type=heap_buffers;
> memtable_cleanup_threshold=null; memtable_flush_writers=0;
> memtable_heap_space_in_mb=null; memtable_offheap_space_in_mb=null;
> min_free_space_per_drive_in_mb=50;
> native_transport_max_concurrent_connections=-1;
> 

Re: Node always dieing

[Chris Mawata]

Notice
.SimpleSeedProvider{seeds=10.100.100.19, 10.100.100.85, 10.100.100.185,
10.100.100.161, 10.100.100.52, 10.100.1000.213};

Why do you have all six of your nodes as seeds? is it possible that the
last one you added used itself as the seed and is isolated?

On Thu, Apr 6, 2017 at 6:48 AM, Cogumelos Maravilha <
cogumelosmaravi...@sapo.pt> wrote:

> Yes C* is running as cassandra:
>
> cassand+  2267 1 99 10:18 ?00:02:56 java
> -Xloggc:/var/log/cassandra/gc.log -ea -XX:+UseThreadPriorities
> -XX:Threa...
>
> INFO  [main] 2017-04-06 10:35:42,956 Config.java:474 - Node
> configuration:[allocate_tokens_for_keyspace=null; 
> authenticator=PasswordAuthenticator;
> authorizer=CassandraAuthorizer; auto_bootstrap=true; auto_snapshot=true;
> back_pressure_enabled=false; back_pressure_strategy=org.
> apache.cassandra.net.RateBasedBackPressure{high_ratio=0.9, factor=5,
> flow=FAST}; batch_size_fail_threshold_in_kb=50;
> batch_size_warn_threshold_in_kb=5; batchlog_replay_throttle_in_kb=1024;
> broadcast_address=null; broadcast_rpc_address=null; 
> buffer_pool_use_heap_if_exhausted=true;
> cas_contention_timeout_in_ms=600; cdc_enabled=false;
> cdc_free_space_check_interval_ms=250; cdc_raw_directory=null;
> cdc_total_space_in_mb=0; client_encryption_options=;
> cluster_name=company; column_index_cache_size_in_kb=2;
> column_index_size_in_kb=64; commit_failure_policy=ignore;
> commitlog_compression=null; commitlog_directory=/mnt/cassandra/commitlog;
> commitlog_max_compression_buffers_in_pool=3;
> commitlog_periodic_queue_size=-1; commitlog_segment_size_in_mb=32;
> commitlog_sync=periodic; commitlog_sync_batch_window_in_ms=NaN;
> commitlog_sync_period_in_ms=1; commitlog_total_space_in_mb=null;
> compaction_large_partition_warning_threshold_mb=100;
> compaction_throughput_mb_per_sec=16; concurrent_compactors=null;
> concurrent_counter_writes=32; concurrent_materialized_view_writes=32;
> concurrent_reads=32; concurrent_replicates=null; concurrent_writes=32;
> counter_cache_keys_to_save=2147483647; counter_cache_save_period=7200;
> counter_cache_size_in_mb=null; counter_write_request_timeout_in_ms=600;
> credentials_cache_max_entries=1000; credentials_update_interval_in_ms=-1;
> credentials_validity_in_ms=2000; cross_node_timeout=false;
> data_file_directories=[Ljava.lang.String;@223f3642;
> disk_access_mode=auto; disk_failure_policy=ignore;
> disk_optimization_estimate_percentile=0.95; 
> disk_optimization_page_cross_chance=0.1;
> disk_optimization_strategy=ssd; dynamic_snitch=true;
> dynamic_snitch_badness_threshold=0.1; 
> dynamic_snitch_reset_interval_in_ms=60;
> dynamic_snitch_update_interval_in_ms=100; 
> enable_scripted_user_defined_functions=false;
> enable_user_defined_functions=false; 
> enable_user_defined_functions_threads=true;
> encryption_options=null; endpoint_snitch=SimpleSnitch;
> file_cache_size_in_mb=null; gc_log_threshold_in_ms=200;
> gc_warn_threshold_in_ms=1000; hinted_handoff_disabled_datacenters=[];
> hinted_handoff_enabled=true; hinted_handoff_throttle_in_kb=1024;
> hints_compression=null; hints_directory=/mnt/cassandra/hints;
> hints_flush_period_in_ms=1; incremental_backups=false;
> index_interval=null; index_summary_capacity_in_mb=null;
> index_summary_resize_interval_in_minutes=60; initial_token=null;
> inter_dc_stream_throughput_outbound_megabits_per_sec=200;
> inter_dc_tcp_nodelay=false; internode_authenticator=null;
> internode_compression=dc; internode_recv_buff_size_in_bytes=0;
> internode_send_buff_size_in_bytes=0; key_cache_keys_to_save=2147483647;
> key_cache_save_period=14400; key_cache_size_in_mb=null;
> listen_address=10.100.100.213; listen_interface=null;
> listen_interface_prefer_ipv6=false; listen_on_broadcast_address=false;
> max_hint_window_in_ms=1080; max_hints_delivery_threads=2;
> max_hints_file_size_in_mb=128; max_mutation_size_in_kb=null;
> max_streaming_retries=3; max_value_size_in_mb=256;
> memtable_allocation_type=heap_buffers; memtable_cleanup_threshold=null;
> memtable_flush_writers=0; memtable_heap_space_in_mb=null;
> memtable_offheap_space_in_mb=null; min_free_space_per_drive_in_mb=50;
> native_transport_max_concurrent_connections=-1; native_transport_max_
> concurrent_connections_per_ip=-1; native_transport_max_frame_size_in_mb=256;
> native_transport_max_threads=128; native_transport_port=9042;
> native_transport_port_ssl=null; num_tokens=256; 
> otc_coalescing_strategy=TIMEHORIZON;
> otc_coalescing_window_us=200; 
> partitioner=org.apache.cassandra.dht.Murmur3Partitioner;
> permissions_cache_max_entries=1000; permissions_update_interval_in_ms=-1;
> permissions_validity_in_ms=2000; phi_convict_threshold=8.0;
> prepared_statements_cache_size_mb=null; range_request_timeout_in_ms=600;
> read_request_timeout_in_ms=600; request_scheduler=org.apache.
> cassandra.scheduler.NoScheduler; request_scheduler_id=null;
> request_scheduler_options=null; request_timeout_in_ms=600;
> role_manager=CassandraRoleManager; 

RE: Migrating from Datastax Distribution to Apache Cassandra

[Eren Yilmaz]

Thanks Michael,

Are there any data changes that I need to worry about?

Eren 

-Original Message-
From: Michael Shuler [mailto:mshu...@pbandjelly.org] On Behalf Of Michael Shuler
Sent: Friday, April 7, 2017 9:20 PM
To: user@cassandra.apache.org
Subject: Re: Migrating from Datastax Distribution to Apache Cassandra

Example DDC 3.7.0 to Apache Cassandra 3.10 upgrade with all default configs, no 
data, and both the DDC and Apache Cassandra lines in sources.list (sorry for 
any weird wrapping, but I think the list strips
attachments):

mshuler@hana:~$ apt-cache policy datastax-ddc cassandra
datastax-ddc:
  Installed: (none)
  Candidate: 3.7.0
  Version table:
 3.7.0 0
500 https://debian.datastax.com/datastax-ddc/ 3.7/main amd64 Packages
cassandra:
  Installed: (none)
  Candidate: 3.10
  Version table:
 3.10 0
500 http://www.apache.org/dist/cassandra/debian/ 310x/main amd64 
Packages mshuler@hana:~$ mshuler@hana:~$ sudo apt-get install datastax-ddc 
Reading package lists... Done Building dependency tree Reading state 
information... Done The following extra packages will be installed:
  datastax-ddc-tools
The following NEW packages will be installed:
  datastax-ddc datastax-ddc-tools
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 28.4 MB of archives.
After this operation, 38.0 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 https://debian.datastax.com/datastax-ddc/ 3.7/main datastax-ddc all 3.7.0 
[28.4 MB]
Get:2 https://debian.datastax.com/datastax-ddc/ 3.7/main datastax-ddc-tools all 
3.7.0 [4,484 B] Fetched 28.4 MB in 3s (8,210 kB/s) Selecting previously 
unselected package datastax-ddc.
(Reading database ... 171852 files and directories currently installed.) 
Preparing to unpack .../datastax-ddc_3.7.0_all.deb ...
Unpacking datastax-ddc (3.7.0) ...
Selecting previously unselected package datastax-ddc-tools.
Preparing to unpack .../datastax-ddc-tools_3.7.0_all.deb ...
Unpacking datastax-ddc-tools (3.7.0) ...
Processing triggers for systemd (215-17+deb8u6) ...
Setting up datastax-ddc (3.7.0) ...
vm.max_map_count = 1048575
net.ipv4.tcp_keepalive_time = 300
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults Setting up datastax-ddc-tools (3.7.0) ...
Processing triggers for systemd (215-17+deb8u6) ...
mshuler@hana:~$
mshuler@hana:~$ sudo apt-get install cassandra cassandra-tools Reading package 
lists... Done Building dependency tree Reading state information... Done The 
following packages will be REMOVED:
  datastax-ddc datastax-ddc-tools
The following NEW packages will be installed:
  cassandra cassandra-tools
0 upgraded, 2 newly installed, 2 to remove and 0 not upgraded.
Need to get 29.2 MB of archives.
After this operation, 939 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://www.apache.org/dist/cassandra/debian/ 310x/main cassandra all 3.10 
[29.2 MB]
Get:2 http://www.apache.org/dist/cassandra/debian/ 310x/main cassandra-tools 
all 3.10 [4,558 B] Fetched 29.2 MB in 2s (13.6 MB/s) (Reading database ... 
172046 files and directories currently installed.) Removing datastax-ddc-tools 
(3.7.0) ...
Removing datastax-ddc (3.7.0) ...
Selecting previously unselected package cassandra.
(Reading database ... 171870 files and directories currently installed.) 
Preparing to unpack .../cassandra_3.10_all.deb ...
Unpacking cassandra (3.10) ...
Selecting previously unselected package cassandra-tools.
Preparing to unpack .../cassandra-tools_3.10_all.deb ...
Unpacking cassandra-tools (3.10) ...
Processing triggers for systemd (215-17+deb8u6) ...
Setting up cassandra (3.10) ...
Installing new version of config file /etc/cassandra/cassandra-env.sh ...
Installing new version of config file /etc/cassandra/cassandra.yaml ...
Installing new version of config file /etc/cassandra/jvm.options ...
Installing new version of config file /etc/cassandra/logback-tools.xml ...
Installing new version of config file /etc/cassandra/logback.xml ...
vm.max_map_count = 1048575
net.ipv4.tcp_keepalive_time = 300
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults Setting up cassandra-tools (3.10) ...
mshuler@hana:~$

--
Warm regards,
Michael