You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by ad...@apache.org on 2022/01/26 11:52:07 UTC
[cassandra] branch cassandra-4.0 updated (95257c0 -> 67f913a)
This is an automated email from the ASF dual-hosted git repository.
adelapena pushed a change to branch cassandra-4.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git.
from 95257c0 Sstableverify unit test operate on SSTables
new 40bf533 Fix conversion from megabits to bytes in streaming rate limiter
new bfab1fd Merge branch 'cassandra-3.0' into cassandra-3.11
new 67f913a Merge branch 'cassandra-3.11' into cassandra-4.0
The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
CHANGES.txt | 1 +
NEWS.txt | 6 ++++++
src/java/org/apache/cassandra/streaming/StreamManager.java | 2 +-
3 files changed, 8 insertions(+), 1 deletion(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-3.11' into cassandra-4.0
Posted by ad...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
adelapena pushed a commit to branch cassandra-4.0
in repository https://gitbox.apache.org/repos/asf/cassandra.git
commit 67f913a7064e7db83ae92f2c55eaeae7db51055c
Merge: 95257c0 bfab1fd
Author: Andrés de la Peña <a....@gmail.com>
AuthorDate: Wed Jan 26 11:43:14 2022 +0000
Merge branch 'cassandra-3.11' into cassandra-4.0
CHANGES.txt | 1 +
NEWS.txt | 6 ++++++
src/java/org/apache/cassandra/streaming/StreamManager.java | 2 +-
3 files changed, 8 insertions(+), 1 deletion(-)
diff --cc CHANGES.txt
index cf4c206,579cea2..ca9b6b3
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@@ -1,39 -1,17 +1,40 @@@
-3.11.12
- * Upgrade snakeyaml to 1.26 in 3.11 (CASSANDRA=17028)
+4.0.2
+ * Full Java 11 support (CASSANDRA-16894)
+ * Remove unused 'geomet' package from cqlsh path (CASSANDRA-17271)
+ * Removed unused 'cql' dependency (CASSANDRA-17247)
+ * Don't block gossip when clearing repair snapshots (CASSANDRA-17168)
+ * Deduplicate warnings for deprecated parameters (changed names) (CASSANDRA-17160)
+ * Update ant-junit to version 1.10.12 (CASSANDRA-17218)
+ * Add droppable tombstone metrics to nodetool tablestats (CASSANDRA-16308)
+ * Fix disk failure triggered when enabling FQL on an unclean directory (CASSANDRA-17136)
+ * Fixed broken classpath when multiple jars in build directory (CASSANDRA-17129)
+ * DebuggableThreadPoolExecutor does not propagate client warnings (CASSANDRA-17072)
+ * internode_send_buff_size_in_bytes and internode_recv_buff_size_in_bytes have new names. Backward compatibility with the old names added (CASSANDRA-17141)
+ * Remove unused configuration parameters from cassandra.yaml (CASSANDRA-17132)
+ * Queries performed with NODE_LOCAL consistency level do not update request metrics (CASSANDRA-17052)
+ * Fix multiple full sources can be select unexpectedly for bootstrap streaming (CASSANDRA-16945)
+ * Fix cassandra.yaml formatting of parameters (CASSANDRA-17131)
+ * Add backward compatibility for CQLSSTableWriter Date fields (CASSANDRA-17117)
+ * Push initial client connection messages to trace (CASSANDRA-17038)
+ * Correct the internode message timestamp if sending node has wrapped (CASSANDRA-16997)
+ * Avoid race causing us to return null in RangesAtEndpoint (CASSANDRA-16965)
+ * Avoid rewriting all sstables during cleanup when transient replication is enabled (CASSANDRA-16966)
+ * Prevent CQLSH from failure on Python 3.10 (CASSANDRA-16987)
+ * Avoid trying to acquire 0 permits from the rate limiter when taking snapshot (CASSANDRA-16872)
+ * Upgrade Caffeine to 2.5.6 (CASSANDRA-15153)
+ * Include SASI components to snapshots (CASSANDRA-15134)
+ * Fix missed wait latencies in the output of `nodetool tpstats -F` (CASSANDRA-16938)
+ * Remove all the state pollution between tests in SSTableReaderTest (CASSANDRA-16888)
+ * Delay auth setup until after gossip has settled to avoid unavailables on startup (CASSANDRA-16783)
+ * Fix clustering order logic in CREATE MATERIALIZED VIEW (CASSANDRA-16898)
+ * org.apache.cassandra.db.rows.ArrayCell#unsharedHeapSizeExcludingData includes data twice (CASSANDRA-16900)
+ * Exclude Jackson 1.x transitive dependency of hadoop* provided dependencies (CASSANDRA-16854)
+Merged from 3.11:
* Add key validation to ssstablescrub (CASSANDRA-16969)
* Update Jackson from 2.9.10 to 2.12.5 (CASSANDRA-16851)
- * Include SASI components to snapshots (CASSANDRA-15134)
* Make assassinate more resilient to missing tokens (CASSANDRA-16847)
- * Exclude Jackson 1.x transitive dependency of hadoop* provided dependencies (CASSANDRA-16854)
- * Validate SASI tokenizer options before adding index to schema (CASSANDRA-15135)
- * Fixup scrub output when no data post-scrub and clear up old use of row, which really means partition (CASSANDRA-16835)
- * Fix ant-junit dependency issue (CASSANDRA-16827)
- * Reduce thread contention in CommitLogSegment and HintsBuffer (CASSANDRA-16072)
- * Avoid sending CDC column if not enabled (CASSANDRA-16770)
Merged from 3.0:
+ * Fix conversion from megabits to bytes in streaming rate limiter (CASSANDRA-17243)
* Upgrade logback to 1.2.9 (CASSANDRA-17204)
* Avoid race in AbstractReplicationStrategy endpoint caching (CASSANDRA-16673)
* Fix abort when window resizing during cqlsh COPY (CASSANDRA-15230)
diff --cc NEWS.txt
index 749b531,b04f4b4..1649ccd
--- a/NEWS.txt
+++ b/NEWS.txt
@@@ -44,280 -47,26 +44,286 @@@ New feature
Upgrading
---------
- - Before you upgrade, if you are using `cassandra.auth_bcrypt_gensalt_log2_rounds` property,
- confirm it is set to value lower than 31 otherwise Cassandra will fail to start. See CASSANDRA-9384
- for further details. You also need to regenerate passwords for users for who the password
- was created while the above property was set to be more than 30 otherwise they will not be able to log in.
+ - The config properties for setting the streaming throughput `stream_throughput_outbound_megabits_per_sec` and
+ `inter_dc_stream_throughput_outbound_megabits_per_sec` were incorrectly interpreted as mebibits. This has
+ been fixed by CASSANDRA-17243, so the values for these properties will now indicate a throughput ~4.6% lower than
+ what was actually applied in previous versions. This also affects the setters and getters for these properties in
+ the JMX MBean `org.apache.cassandra.db:type=StorageService` and the nodetool commands `set/getstreamthroughput`
+ and `set/getinterdcstreamthroughput`.
+ - Before you upgrade, if you are using `cassandra.auth_bcrypt_gensalt_log2_rounds` property,
+ confirm it is set to value lower than 31 otherwise Cassandra will fail to start. See CASSANDRA-9384
+ for further details. You also need to regenerate passwords for users for who the password
+ was created while the above property was set to be more than 30 otherwise they will not be able to log in.
+ - As part of the Internode Messaging improvement work in CASSANDRA-15066, internode_send_buff_size_in_bytes and
+ internode_recv_buff_size_in_bytes were renamed to internode_socket_send_buffer_size_in_bytes and
+ internode_socket_receive_buffer_size_in_bytes. To support upgrades pre-4.0, we add backward compatibility and
+ currently both old and new names should work. Cassandra 4.0.0 and Cassandra 4.0.1 work ONLY with the new names
+ (They weren't updated in cassandra.yaml though).
+
+4.0
+===
+
+New features
+------------
+ - The data of the system keyspaces using a local strategy (at the exception of the system.batches,
+ system.paxos, system.compaction_history, system.prepared_statements and system.repair tables)
+ is now stored by default in the first data directory, instead of being distributed among all
+ the data directories. This approach will allow the server to tolerate the failure of the other disks.
+ To ensure that a disk failure will not bring a node down, it is possible to use the system_data_file_directory
+ yaml property to store the local system keyspaces data on a directory that provides redundancy.
+ On node startup the local system keyspaces data will be automatically migrated if needed to the
+ correct location.
+ - Nodes will now bootstrap all intra-cluster connections at startup by default and wait
+ 10 seconds for the all but one node in the local data center to be connected and marked
+ UP in gossip. This prevents nodes from coordinating requests and failing because they
+ aren't able to connect to the cluster fast enough. block_for_peers_timeout_in_secs in
+ cassandra.yaml can be used to configure how long to wait (or whether to wait at all)
+ and block_for_peers_in_remote_dcs can be used to also block on all but one node in
+ each remote DC as well. See CASSANDRA-14297 and CASSANDRA-13993 for more information.
+ - *Experimental* support for Transient Replication and Cheap Quorums introduced by CASSANDRA-14404
+ The intended audience for this functionality is expert users of Cassandra who are prepared
+ to validate every aspect of the database for their application and deployment practices. Future
+ releases of Cassandra will make this feature suitable for a wider audience.
+ - *Experimental* support for Java 11 has been added. JVM options that differ between or are
+ specific for Java 8 and 11 have been moved from jvm.options into jvm8.options and jvm11.options.
+ IMPORTANT: Running C* on Java 11 is *experimental* and do it at your own risk.
+ - LCS now respects the max_threshold parameter when compacting - this was hard coded to 32
+ before, but now it is possible to do bigger compactions when compacting from L0 to L1.
+ This also applies to STCS-compactions in L0 - if there are more than 32 sstables in L0
+ we will compact at most max_threshold sstables in an L0 STCS compaction. See CASSANDRA-14388
+ for more information.
+ - There is now an option to automatically upgrade sstables after Cassandra upgrade, enable
+ either in `cassandra.yaml:automatic_sstable_upgrade` or via JMX during runtime. See
+ CASSANDRA-14197.
+ - `nodetool refresh` has been deprecated in favour of `nodetool import` - see CASSANDRA-6719
+ for details
+ - An experimental option to compare all merkle trees together has been added - for example, in
+ a 3 node cluster with 2 replicas identical and 1 out-of-date, with this option enabled, the
+ out-of-date replica will only stream a single copy from up-to-date replica. Enable it by adding
+ "-os" to nodetool repair. See CASSANDRA-3200.
+ - The currentTimestamp, currentDate, currentTime and currentTimeUUID functions have been added.
+ See CASSANDRA-13132
+ - Support for arithmetic operations between `timestamp`/`date` and `duration` has been added.
+ See CASSANDRA-11936
+ - Support for arithmetic operations on number has been added. See CASSANDRA-11935
+ - Preview expected streaming required for a repair (nodetool repair --preview), and validate the
+ consistency of repaired data between nodes (nodetool repair --validate). See CASSANDRA-13257
+ - Support for selecting Map values and Set elements has been added for SELECT queries. See CASSANDRA-7396
+ - Change-Data-Capture has been modified to make CommitLogSegments available
+ immediately upon creation via hard-linking the files. This means that incomplete
+ segments will be available in cdc_raw rather than fully flushed. See documentation
+ and CASSANDRA-12148 for more detail.
+ - The initial build of materialized views can be parallelized. The number of concurrent builder
+ threads is specified by the property `cassandra.yaml:concurrent_materialized_view_builders`.
+ This property can be modified at runtime through both JMX and the new `setconcurrentviewbuilders`
+ and `getconcurrentviewbuilders` nodetool commands. See CASSANDRA-12245 for more details.
+ - There is now a binary full query log based on Chronicle Queue that can be controlled using
+ nodetool enablefullquerylog, disablefullquerylog, and resetfullquerylog. The log
+ contains all queries invoked, approximate time they were invoked, any parameters necessary
+ to bind wildcard values, and all query options. A human readable version of the log can be
+ dumped or tailed using the new bin/fqltool utility. The full query log is designed to be safe
+ to use in production and limits utilization of heap memory and disk space with limits
+ you can specify when enabling the log.
+ See nodetool and fqltool help text for more information.
+ - SSTableDump now supports the -l option to output each partition as it's own json object
+ See CASSANDRA-13848 for more detail
+ - Metric for coordinator writes per table has been added. See CASSANDRA-14232
+ - Nodetool cfstats now has options to sort by various metrics as well as limit results.
+ - Operators can restrict login user activity to one or more datacenters. See `network_authorizer`
+ in cassandra.yaml, and the docs for create and alter role statements. CASSANDRA-13985
+ - Roles altered from login=true to login=false will prevent existing connections from executing any
+ statements after the cache has been refreshed. CASSANDRA-13985
+ - Support for audit logging of database activity. If enabled, logs every incoming
+ CQL command request, Authentication (successful as well as unsuccessful login) to a node.
+ - Faster streaming of entire SSTables using ZeroCopy APIs. If enabled, Cassandra will use stream
+ entire SSTables, significantly speeding up transfers. Any streaming related operations will see
+ corresponding improvement. See CASSANDRA-14556.
+ - NetworkTopologyStrategy now supports auto-expanding the replication_factor
+ option into all available datacenters at CREATE or ALTER time. For example,
+ specifying replication_factor: 3 translates to three replicas in every
+ datacenter. This auto-expansion will _only add_ datacenters for safety.
+ See CASSANDRA-14303 for more details.
+ - Added Python 3 support so cqlsh and cqlshlib is now compatible with Python 2.7 and Python 3.6.
+ Added --python option to cqlsh so users can specify the path to their chosen Python interpreter.
+ See CASSANDRA-10190 for details.
+ - Support for server side DESCRIBE statements has been added. See CASSANDRA-14825
+ - It is now possible to rate limit snapshot creation/clearing. See CASSANDRA-13019
+
+Upgrading
+---------
+ - DESCRIBE|DESC was moved to server side in Cassandra 4.0. As a consequence DESRIBE|DESC will not work in cqlsh 6.0.0
+ being connected to earlier major Cassandra versions where DESCRIBE does not exist server side.
+ - cqlsh shell startup script now prefers 'python3' before 'python' when identifying a runtime.
+ - As part of the Internode Messaging improvement work in CASSANDRA-15066, matching response verbs for every request
+ verb were introduced and verbs were renamed. DroppedMessageMetrics pre-4.0 are now available with _REQ suffix. As
+ part of CASSANDRA-16083, we added DroppedMessageMetrics backward compatibility layer which exposes the metrics with
+ their old names too. Only the value for verbs READ and RANGE_SLICE will differ from the same metrics in 3.11 as it
+ does not include anymore the responses dropped, only the requests. After being deprecated in 3.11 PAGED_RANGE was
+ fully removed in 4.0. ConditionNotMet metric has been moved under scope CASClientWriteRequestMetrtic but as part of
+ CASSANDRA-16083, backward compatibility layer was added so it can be still exposed under the old 3.11 scope.
+ - Native protocol v5 is promoted from beta in this release. The wire format has changed
+ significantly and users should take care to ensure client drivers are upgraded to a version
+ with support for the final v5 format, if currently connecting over v5-beta. (CASSANDRA-15299, CASSANDRA-14973)
+ - Cassandra removed support for the OldNetworkTopologyStrategy. Before upgrading you will need to change the
+ replication strategy for the keyspaces using this strategy to the NetworkTopologyStrategy. (CASSANDRA-13990)
+ - Sstables for tables using with a frozen UDT written by C* 3.0 appear as corrupted.
+
+ Background: The serialization-header in the -Statistics.db sstable component contains the type information
+ of the table columns. C* 3.0 write incorrect type information for frozen UDTs by omitting the
+ "frozen" information. Non-frozen UDTs were introduced by CASSANDRA-7423 in C* 3.6. Since then, the missing
+ "frozen" information leads to deserialization issues that result in CorruptSSTableExceptions, potentially other
+ exceptions as well.
+
+ As a mitigation, the sstable serialization-headers are rewritten to contain the missing "frozen" information for
+ UDTs once, when an upgrade from C* 3.0 is detected. This migration does not touch snapshots or backups.
+
+ The sstablescrub tool now performs a check of the sstable serialization-header against the schema. A mismatch of
+ the types in the serialization-header and the schema will cause sstablescrub to error out and stop by default.
+ See the new `-e` option. `-e off` disables the new validation code. `-e fix` or `-e fix-only`, e.g.
+ `sstablescrub -e fix keyspace table`, will validate the serialization-header, rewrite the non-frozen UDTs
+ in the serialzation-header to frozen UDTs, if that matches the schema, and continue with scrub.
+ See `sstablescrub -h`.
+ (CASSANDRA-15035)
+ - CASSANDRA-13241 lowered the default chunk_lengh_in_kb for compresesd tables from
+ 64kb to 16kb. For highly compressible data this can have a noticeable impact
+ on space utilization. You may want to consider manually specifying this value.
+ - Additional columns have been added to system_distributed.repair_history,
+ system_traces.sessions and system_traces.events. As a result select queries
+ against these tables - including queries against tracing tables performed
+ automatically by the drivers and cqlsh - will fail and generate an error in the log
+ during upgrade when the cluster is mixed version. On 3.x side this will also lead
+ to broken internode connections and lost messages.
+ Cassandra versions 3.0.20 and 3.11.6 pre-add these columns (see CASSANDRA-15385),
+ so please make sure to upgrade to those versions or higher before upgrading to
+ 4.0 for query tracing to not cause any issues during the upgrade to 4.0.
+ - Timestamp ties between values resolve differently: if either value has a TTL,
+ this value always wins. This is to provide consistent reconciliation before
+ and after the value expires into a tombstone.
+ - Support for legacy auth tables in the system_auth keyspace (users,
+ permissions, credentials) and the migration code has been removed. Migration
+ of these legacy auth tables must have been completed before the upgrade to
+ 4.0 and the legacy tables must have been removed. See the 'Upgrading' section
+ for version 2.2 for migration instructions.
+ - Cassandra 4.0 removed support for the deprecated Thrift interface. Amongst
+ other things, this implies the removal of all yaml options related to thrift
+ ('start_rpc', rpc_port, ...).
+ - Cassandra 4.0 removed support for any pre-3.0 format. This means you
+ cannot upgrade from a 2.x version to 4.0 directly, you have to upgrade to
+ a 3.0.x/3.x version first (and run upgradesstable). In particular, this
+ mean Cassandra 4.0 cannot load or read pre-3.0 sstables in any way: you
+ will need to upgrade those sstable in 3.0.x/3.x first.
+ - Upgrades from 3.0.x or 3.x are supported since 3.0.13 or 3.11.0, previous
+ versions will causes issues during rolling upgrades (CASSANDRA-13274).
+ - Cassandra will no longer allow invalid keyspace replication options, such
+ as invalid datacenter names for NetworkTopologyStrategy. Operators MUST
+ add new nodes to a datacenter before they can set set ALTER or CREATE
+ keyspace replication policies using that datacenter. Existing keyspaces
+ will continue to operate, but CREATE and ALTER will validate that all
+ datacenters specified exist in the cluster.
+ - Cassandra 4.0 fixes a problem with incremental repair which caused repaired
+ data to be inconsistent between nodes. The fix changes the behavior of both
+ full and incremental repairs. For full repairs, data is no longer marked
+ repaired. For incremental repairs, anticompaction is run at the beginning
+ of the repair, instead of at the end. If incremental repair was being used
+ prior to upgrading, a full repair should be run after upgrading to resolve
+ any inconsistencies.
+ - Config option index_interval has been removed (it was deprecated since 2.0)
+ - Deprecated repair JMX APIs are removed.
+ - The version of snappy-java has been upgraded to 1.1.2.6
+ - the miniumum value for internode message timeouts is 10ms. Previously, any
+ positive value was allowed. See cassandra.yaml entries like
+ read_request_timeout_in_ms for more details.
+ - Cassandra 4.0 allows a single port to be used for both secure and insecure
+ connections between cassandra nodes (CASSANDRA-10404). See the yaml for
+ specific property changes, and see the security doc for full details.
+ - Due to the parallelization of the initial build of materialized views,
+ the per token range view building status is stored in the new table
+ `system.view_builds_in_progress`. The old table `system.views_builds_in_progress`
+ is no longer used and can be removed. See CASSANDRA-12245 for more details.
+ - Config option commitlog_sync_batch_window_in_ms has been deprecated as it's
+ documentation has been incorrect and the setting itself near useless.
+ Batch mode remains a valid commit log mode, however.
+ - There is a new commit log mode, group, which is similar to batch mode
+ but blocks for up to a configurable number of milliseconds between disk flushes.
+ - nodetool clearsnapshot now required the --all flag to remove all snapshots.
+ Previous behavior would delete all snapshots by default.
+ - Nodes are now identified by a combination of IP, and storage port.
+ Existing JMX APIs, nodetool, and system tables continue to work
+ and accept/return just an IP, but there is a new
+ version of each that works with the full unambiguous identifier.
+ You should prefer these over the deprecated ambiguous versions that only
+ work with an IP. This was done to support multiple instances per IP.
+ Additionally we are moving to only using a single port for encrypted and
+ unencrypted traffic and if you want multiple instances per IP you must
+ first switch encrypted traffic to the storage port and not a separate
+ encrypted port. If you want to use multiple instances per IP
+ with SSL you will need to use StartTLS on storage_port and set
+ outgoing_encrypted_port_source to gossip outbound connections
+ know what port to connect to for each instance. Before changing
+ storage port or native port at nodes you must first upgrade the entire cluster
+ and clients to 4.0 so they can handle the port not being consistent across
+ the cluster.
+ - Names of AWS regions/availability zones have been cleaned up to more correctly
+ match the Amazon names. There is now a new option in conf/cassandra-rackdc.properties
+ that lets users enable the correct names for new clusters, or use the legacy
+ names for existing clusters. See conf/cassandra-rackdc.properties for details.
+ - Background repair has been removed. dclocal_read_repair_chance and
+ read_repair_chance table options have been removed and are now rejected.
+ See CASSANDRA-13910 for details.
+ - Internode TCP connections that do not ack segments for 30s will now
+ be automatically detected and closed via the Linux TCP_USER_TIMEOUT
+ socket option. This should be exceedingly rare, but AWS networks (and
+ other stateful firewalls) apparently suffer from this issue. You can
+ tune the timeouts on TCP connection and segment ack via the
+ `cassandra.yaml:internode_tcp_connect_timeout_in_ms` and
+ `cassandra.yaml:internode_tcp_user_timeout_in_ms` options respectively.
+ See CASSANDRA-14358 for details.
+ - repair_session_space_in_mb setting has been added to cassandra.yaml to allow operators to reduce
+ merkle tree size if repair is creating too much heap pressure. The repair_session_max_tree_depth
+ setting added in 3.0.19 and 3.11.5 is deprecated in favor of this setting. See CASSANDRA-14096
+ - The flags 'enable_materialized_views' and 'enable_sasi_indexes' in cassandra.yaml
+ have been set as false by default. Operators should modify them to allow the
+ creation of new views and SASI indexes, the existing ones will continue working.
+ See CASSANDRA-14866 for details.
+ - CASSANDRA-15216 - The flag 'cross_node_timeout' has been set as true by default.
+ This change is done under the assumption that users have setup NTP on
+ their clusters or otherwise synchronize their clocks, and that clocks are
+ mostly in sync, since this is a requirement for general correctness of
+ last write wins.
+ - CASSANDRA-15257 removed the joda time dependency. Any time formats
+ passed will now need to conform to java.time.format.DateTimeFormatter.
+ Most notably, days and months must be two digits, and years exceeding
+ four digits need to be prefixed with a plus or minus sign.
+ - cqlsh now returns a non-zero code in case of errors. This is a backward incompatible change so it may
+ break existing scripts that rely on the current behavior. See CASSANDRA-15623 for more details.
+ - Updated the default compaction_throughput_mb_per_sec to to 64. The original
+ default (16) was meant for spinning disk volumes. See CASSANDRA-14902 for details.
+ - Custom compaction strategies must now handle getting sstables added/removed notifications for
+ sstables already added/removed - see CASSANDRA-14103 for details.
+ - Support for JNA with glibc 2.6 and earlier has been removed. Centos 5, Debian 4, and Ubuntu 7.10 operating systems
+ must be first upgraded. See CASSANDRA-16212 for more.
+ - In cassandra.yaml, when using vnodes num_tokens must be defined if initial_token is defined.
+ If it is not defined, or not equal to the numbers of tokens defined in initial_tokens,
+ the node will not start. See CASSANDRA-14477 for details.
+ - CASSANDRA-13701 To give a better out of the box experience, the default 'num_tokens'
+ value has been changed from 256 to 16 for reasons described in
+ https://cassandra.apache.org/doc/latest/getting_started/production.html#tokens
+ 'allocate_tokens_for_local_replication_factor' is also uncommented and set to 3.
+ Please note when upgrading that if the 'num_tokens' value is different than what you have
+ configured, the upgraded node will refuse to start. Also note that if a new node joining
+ the cluster has a different value for 'num_tokens' than the rest of the datacenter,
+ the new node will be responsible for a different amount of data than the rest of the datacenter.
-Statement re-prepare storms
----------------------------
- - CASSANDRA-15252 has changed how prepared statement ids are computed in order to avoid infinite re-prepare
- loops caused by the driver. This new behaviour will be picked up only when the entire cluster has been updated
- to 3.0.26 or higher. In case of a mixed version cluster, different major versions will be taken as a minimum
- required version.
+Deprecation
+-----------
-3.11.11
-=======
+ - The JMX MBean org.apache.cassandra.metrics:type=Streaming,name=ActiveOutboundStreams has been
+ deprecated and will be removed in a subsequent major version. This metric was not updated since several version
+ already.
+ - The JMX MBean org.apache.cassandra.db:type=BlacklistedDirectories has been
+ deprecated in favor of org.apache.cassandra.db:type=DisallowedDirectories
+ and will be removed in a subsequent major version.
+ - cqlsh support of 2.7 is deprecated and will warn when running with Python 2.7.
ALTER ... DROP COMPACT STORAGE
------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org