mirror of https://github.com/apache/cassandra
Prepare for release, set version build date, fix whitespace
This commit is contained in:
Michael Shuler
parent
fefb79994c
commit
53bdc64a0e
194
NEWS.txt
194
NEWS.txt
|
|
@ -38,78 +38,78 @@ using the provided 'sstableupgrade' tool.
|
||||||
|
|
||||||
New features
|
New features
|
||||||
------------
|
------------
|
||||||
- Nodes will now bootstrap all intra-cluster connections at startup by default and wait
|
- 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
|
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
|
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
|
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)
|
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
|
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.
|
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
|
- *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
|
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
|
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.
|
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
|
- *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.
|
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.
|
IMPORTANT: Running C* on Java 11 is *experimental* and do it at your own risk.
|
||||||
Compilation recommendations: configure Java 11 SDK via JAVA_HOME and Java 8 SDK via JAVA8_HOME.
|
Compilation recommendations: configure Java 11 SDK via JAVA_HOME and Java 8 SDK via JAVA8_HOME.
|
||||||
Release builds require Java 11 + Java 8. Development builds can use Java 8 without 11.
|
Release builds require Java 11 + Java 8. Development builds can use Java 8 without 11.
|
||||||
- LCS now respects the max_threshold parameter when compacting - this was hard coded to 32
|
- 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.
|
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
|
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
|
we will compact at most max_threshold sstables in an L0 STCS compaction. See CASSANDRA-14388
|
||||||
for more information.
|
for more information.
|
||||||
- There is now an option to automatically upgrade sstables after Cassandra upgrade, enable
|
- 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
|
either in `cassandra.yaml:automatic_sstable_upgrade` or via JMX during runtime. See
|
||||||
CASSANDRA-14197.
|
CASSANDRA-14197.
|
||||||
- `nodetool refresh` has been deprecated in favour of `nodetool import` - see CASSANDRA-6719
|
- `nodetool refresh` has been deprecated in favour of `nodetool import` - see CASSANDRA-6719
|
||||||
for details
|
for details
|
||||||
- An experimental option to compare all merkle trees together has been added - for example, in
|
- 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
|
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
|
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.
|
"-os" to nodetool repair. See CASSANDRA-3200.
|
||||||
- The currentTimestamp, currentDate, currentTime and currentTimeUUID functions have been added.
|
- The currentTimestamp, currentDate, currentTime and currentTimeUUID functions have been added.
|
||||||
See CASSANDRA-13132
|
See CASSANDRA-13132
|
||||||
- Support for arithmetic operations between `timestamp`/`date` and `duration` has been added.
|
- Support for arithmetic operations between `timestamp`/`date` and `duration` has been added.
|
||||||
See CASSANDRA-11936
|
See CASSANDRA-11936
|
||||||
- Support for arithmetic operations on number has been added. See CASSANDRA-11935
|
- 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
|
- 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
|
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
|
- 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
|
- Change-Data-Capture has been modified to make CommitLogSegments available
|
||||||
immediately upon creation via hard-linking the files. This means that incomplete
|
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
|
segments will be available in cdc_raw rather than fully flushed. See documentation
|
||||||
and CASSANDRA-12148 for more detail.
|
and CASSANDRA-12148 for more detail.
|
||||||
- The initial build of materialized views can be parallelized. The number of concurrent builder
|
- 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`.
|
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`
|
This property can be modified at runtime through both JMX and the new `setconcurrentviewbuilders`
|
||||||
and `getconcurrentviewbuilders` nodetool commands. See CASSANDRA-12245 for more details.
|
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
|
- There is now a binary full query log based on Chronicle Queue that can be controlled using
|
||||||
nodetool enablefullquerylog, disablefullquerylog, and resetfullquerylog. The log
|
nodetool enablefullquerylog, disablefullquerylog, and resetfullquerylog. The log
|
||||||
contains all queries invoked, approximate time they were invoked, any parameters necessary
|
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
|
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
|
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
|
to use in production and limits utilization of heap memory and disk space with limits
|
||||||
you can specify when enabling the log.
|
you can specify when enabling the log.
|
||||||
See nodetool and fqltool help text for more information.
|
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
|
- SSTableDump now supports the -l option to output each partition as it's own json object
|
||||||
See CASSANDRA-13848 for more detail
|
See CASSANDRA-13848 for more detail
|
||||||
- Metric for coordinator writes per table has been added. See CASSANDRA-14232
|
- 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.
|
- 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`
|
- 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
|
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
|
- Roles altered from login=true to login=false will prevent existing connections from executing any
|
||||||
statements after the cache has been refreshed. CASSANDRA-13985
|
statements after the cache has been refreshed. CASSANDRA-13985
|
||||||
- Support for audit logging of database activity. If enabled, logs every incoming
|
- 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.
|
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
|
- 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
|
entire SSTables, significantly speeding up transfers. Any streaming related operations will see
|
||||||
corresponding improvement. See CASSANDRA-14556.
|
corresponding improvement. See CASSANDRA-14556.
|
||||||
- NetworkTopologyStrategy now supports auto-expanding the replication_factor
|
- NetworkTopologyStrategy now supports auto-expanding the replication_factor
|
||||||
option into all available datacenters at CREATE or ALTER time. For example,
|
option into all available datacenters at CREATE or ALTER time. For example,
|
||||||
specifying replication_factor: 3 translates to three replicas in every
|
specifying replication_factor: 3 translates to three replicas in every
|
||||||
datacenter. This auto-expansion will _only add_ datacenters for safety.
|
datacenter. This auto-expansion will _only add_ datacenters for safety.
|
||||||
See CASSANDRA-14303 for more details.
|
See CASSANDRA-14303 for more details.
|
||||||
|
|
||||||
Upgrading
|
Upgrading
|
||||||
---------
|
---------
|
||||||
|
|
@ -160,23 +160,23 @@ Upgrading
|
||||||
- Config option index_interval has been removed (it was deprecated since 2.0)
|
- Config option index_interval has been removed (it was deprecated since 2.0)
|
||||||
- Deprecated repair JMX APIs are removed.
|
- Deprecated repair JMX APIs are removed.
|
||||||
- The version of snappy-java has been upgraded to 1.1.2.6
|
- The version of snappy-java has been upgraded to 1.1.2.6
|
||||||
- the miniumum value for internode message timeouts is 10ms. Previously, any
|
- the miniumum value for internode message timeouts is 10ms. Previously, any
|
||||||
positive value was allowed. See cassandra.yaml entries like
|
positive value was allowed. See cassandra.yaml entries like
|
||||||
read_request_timeout_in_ms for more details.
|
read_request_timeout_in_ms for more details.
|
||||||
- Cassandra 4.0 allows a single port to be used for both secure and insecure
|
- 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
|
connections between cassandra nodes (CASSANDRA-10404). See the yaml for
|
||||||
specific property changes, and see the security doc for full details.
|
specific property changes, and see the security doc for full details.
|
||||||
- Due to the parallelization of the initial build of materialized views,
|
- Due to the parallelization of the initial build of materialized views,
|
||||||
the per token range view building status is stored in the new table
|
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`
|
`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.
|
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
|
- Config option commitlog_sync_batch_window_in_ms has been deprecated as it's
|
||||||
documentation has been incorrect and the setting itself near useless.
|
documentation has been incorrect and the setting itself near useless.
|
||||||
Batch mode remains a valid commit log mode, however.
|
Batch mode remains a valid commit log mode, however.
|
||||||
- There is a new commit log mode, group, which is similar to batch mode
|
- 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.
|
but blocks for up to a configurable number of milliseconds between disk flushes.
|
||||||
- nodetool clearsnapshot now required the --all flag to remove all snapshots.
|
- nodetool clearsnapshot now required the --all flag to remove all snapshots.
|
||||||
Previous behavior would delete all snapshots by default.
|
Previous behavior would delete all snapshots by default.
|
||||||
- Nodes are now identified by a combination of IP, and storage port.
|
- Nodes are now identified by a combination of IP, and storage port.
|
||||||
Existing JMX APIs, nodetool, and system tables continue to work
|
Existing JMX APIs, nodetool, and system tables continue to work
|
||||||
and accept/return just an IP, but there is a new
|
and accept/return just an IP, but there is a new
|
||||||
|
|
@ -208,9 +208,9 @@ Upgrading
|
||||||
`cassandra.yaml:internode_tcp_connect_timeout_in_ms` and
|
`cassandra.yaml:internode_tcp_connect_timeout_in_ms` and
|
||||||
`cassandra.yaml:internode_tcp_user_timeout_in_ms` options respectively.
|
`cassandra.yaml:internode_tcp_user_timeout_in_ms` options respectively.
|
||||||
See CASSANDRA-14358 for details.
|
See CASSANDRA-14358 for details.
|
||||||
- repair_session_space_in_mb setting has been added to cassandra.yaml to allow operators to reduce
|
- 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
|
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
|
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
|
- 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
|
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.
|
creation of new views and SASI indexes, the existing ones will continue working.
|
||||||
|
|
@ -218,14 +218,14 @@ Upgrading
|
||||||
|
|
||||||
Materialized Views
|
Materialized Views
|
||||||
-------------------
|
-------------------
|
||||||
- Following a discussion regarding concerns about the design and safety of Materialized Views, the C* development
|
- Following a discussion regarding concerns about the design and safety of Materialized Views, the C* development
|
||||||
community no longer recommends them for production use, and considers them experimental. Warnings messages will
|
community no longer recommends them for production use, and considers them experimental. Warnings messages will
|
||||||
now be logged when they are created. (See https://www.mail-archive.com/dev@cassandra.apache.org/msg11511.html)
|
now be logged when they are created. (See https://www.mail-archive.com/dev@cassandra.apache.org/msg11511.html)
|
||||||
- An 'enable_materialized_views' flag has been added to cassandra.yaml to allow operators to prevent creation of
|
- An 'enable_materialized_views' flag has been added to cassandra.yaml to allow operators to prevent creation of
|
||||||
views
|
views
|
||||||
- CREATE MATERIALIZED VIEW syntax has become stricter. Partition key columns are no longer implicitly considered
|
- CREATE MATERIALIZED VIEW syntax has become stricter. Partition key columns are no longer implicitly considered
|
||||||
to be NOT NULL, and no base primary key columns get automatically included in view definition. You have to
|
to be NOT NULL, and no base primary key columns get automatically included in view definition. You have to
|
||||||
specify them explicitly now.
|
specify them explicitly now.
|
||||||
|
|
||||||
3.11.5
|
3.11.5
|
||||||
======
|
======
|
||||||
|
|
@ -263,7 +263,7 @@ Upgrading
|
||||||
|
|
||||||
Upgrading
|
Upgrading
|
||||||
---------
|
---------
|
||||||
- See MAXIMUM TTL EXPIRATION DATE NOTICE above.
|
- See MAXIMUM TTL EXPIRATION DATE NOTICE above.
|
||||||
- Cassandra is now relying on the JVM options to properly shutdown on OutOfMemoryError. By default it will
|
- Cassandra is now relying on the JVM options to properly shutdown on OutOfMemoryError. By default it will
|
||||||
rely on the OnOutOfMemoryError option as the ExitOnOutOfMemoryError and CrashOnOutOfMemoryError options
|
rely on the OnOutOfMemoryError option as the ExitOnOutOfMemoryError and CrashOnOutOfMemoryError options
|
||||||
are not supported by the older 1.7 and 1.8 JVMs. A warning will be logged at startup if none of those JVM
|
are not supported by the older 1.7 and 1.8 JVMs. A warning will be logged at startup if none of those JVM
|
||||||
|
|
|
||||||
|
|
@ -1,14 +1,14 @@
|
||||||
cassandra (4.0~alpha2) UNRELEASED; urgency=medium
|
cassandra (4.0~alpha2) unstable; urgency=medium
|
||||||
|
|
||||||
* New release
|
* New release
|
||||||
|
|
||||||
--
|
-- Michael Shuler <mshuler@apache.org> Thu, 24 Oct 2019 09:12:05 -0500
|
||||||
|
|
||||||
cassandra (4.0~alpha1) unstable; urgency=medium
|
cassandra (4.0~alpha1) unstable; urgency=medium
|
||||||
|
|
||||||
* New release
|
* New release
|
||||||
|
|
||||||
-- Michael Shuler <michael@pbandjelly.org> Tue, 03 Sep 2019 11:51:18 -0500
|
-- Michael Shuler <mshuler@apache.org> Tue, 03 Sep 2019 11:51:18 -0500
|
||||||
|
|
||||||
cassandra (3.10) unstable; urgency=medium
|
cassandra (3.10) unstable; urgency=medium
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue