Priam

This is a re-release of 3.11.60 since that release was blocked by an upload failure to bintray.

Fixing PriamConfig endpoints that were broken because of an underlying dependency change from the last release.

Fixing PriamConfig endpoints that were broken because of an underlying dependency change from the last release.

This is a re-release of 3.1.89 since that release was blocked by a failing test that was run concurrently along with another release train.

This release contains a bugfix in the backup verification strategy to only page when there is no valid backup in the specified date range (SLO window) And also disable lifecyle rule for backup if backup v1 is disabled.

This release contains a bug fix in the backup verification strategy to only page when there is no valid backup in the specified date range (SLO window) And also disable lifecyle rule for backup if backup v1 is disabled.

This release contains the changes for a new BackUpVerification strategy - with these changes ALL unverified backups in the specified date range will be verified and notifications will be sent for each verified backup.

This release contains the changes for a new BackUpVerification strategy - with these changes ALL unverified backups in the specified date range will be verified and notifications will be sent for each verified backup.

(Bugfix) Switch to using upstream cassandra-all from our internal jar
(Bugfix) Allow Priam to run on clusters that don't have public-hostnames and ips

(#844, #839) Implementation of a filter for Backup Notification. The filter can be controlled using the configuration "priam.backupNotifyComponentIncludeList"

(#842, #839) Implementation of a filter for Backup Notification. The filter can be controlled using the configuration "priam.backupNotifyComponentIncludeList"

Adding google to the list of repositories to resolve google related transitive dependencies.

(#836) Move flush and compactions to Service Layer. This allows us to "hot" reload the jobs when configurations change.
(#836) Send SNAPSHOT_VERIFIED message when a snapshot is verified and ready to be consumed by downward dependencies.

• (#835) Move flush and compactions to Service Layer. This allows us to "hot" reload the jobs when configurations change.
• (#835) Send SNAPSHOT_VERIFIED message when a snapshot is verified and ready to be consumed by downward dependencies.

(#834 ) Removing functionality of creating incremental manifest file in backup V1 as it is not used.
(#834 ) Bug fix: When meta file do not exist for TTL in backup v2 we should not be throwing NPE.
(#834 ) Bug fix: Fix X-Y-Z issue using gossip status information instead of gossip state. Note that gossip status is (JOINING/LEAVING/NORMAL) while gossip state is (UP/DOWN). Gossip state is calculated individually by all the Cassandra instances using gossip status.Priam only checked the database to give to Cassandra when "replacing" a token. That ip could be old or outdate. Now the replacing Priam asks other Priam for the view as from C* (source of truth) to find the IP address to replace.
(#834 ) Bug fix: Change return type of cassadmin/paritioner from JSON to text type.
(#834 ) Bug fix: Handle files of 0 bytes iff created from C* during snapshot operation.
(#834 ) Bug fix: Reduce the no. of max chunks as files could inflate after compression.

(#832) Travis build fails for oraclejdk8. Migration to openjdk8

(#827) Removing functionality of creating incremental manifest file in backup V1 as it is not used.
(#827) Bug fix: When meta file do not exist for TTL in backup v2 we should not be throwing NPE.
(#827) Bug fix: Fix X-Y-Z issue using gossip status information instead of gossip state. Note that gossip status is (JOINING/LEAVING/NORMAL) while gossip state is (UP/DOWN). Gossip state is calculated individually by all the Cassandra instances using gossip status.

(#826): Rollback the fixes to use Gossip info while grabbing dead and pre-assigned tokens. Gossip info doesn't not reflect the correct cluster state always. A node marked with status as NORMAL in the Gossip info could actually be down. This can be checked using nt ring. This change will unblock the nodes from joining the ring.

(#825): Rollback the fixes to use Gossip info while grabbing dead and pre-assigned tokens. Gossip info doesn't not reflect the correct cluster state always. A node marked with status as NORMAL in the Gossip info could actually be down. This can be checked using nt ring. This change will unblock the nodes from joining the ring.

(#824): Use replace_address instead of replace_address_first_boot. replace_address always try to bootstrap Cassandra in replace mode even when the previous bootstrap is successful. replace_address_first_boot tries to bootstrap normally if the node already bootstrapped successfully.