Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Production fixes #669

Closed
wants to merge 85 commits into from
Closed

Production fixes #669

wants to merge 85 commits into from

Conversation

Glamdring
Copy link

Addressing issues that I found while trying to deploy Priam, including #666 #667 and #668

vinaykumarchella and others added 30 commits June 28, 2017 13:36
Seed changes for Cassandra 3.x [aagrwal]
1. Make backup/snapshot status manager store additional details like meta file location.
2. Ensure it can save last 60 snapshot days.
3. Allow bindable values on how to save snapshot status in file/datastore. Default implementation stores in a file on the local instance.
4. Non-backward compatible. The previous backup file gets overwritten with new values(null) during the upgrade process.
Default behavior to look for HOUR i.e. the flush interval. If the flush interval is not set, it is considered OFF (default backward compatible behavior). Similar behavior for CRON.
…tflix#574)

* Bug fix: resource leak (Too many open files) while executing Cassandra monitor.
Remove guava dependency in NewTokenRetriever.
…y Cassandra during compaction. (Netflix#579)

* Allow configuration of the size of large partitions that get logged by Cassandra during compaction.
* Make DSE Audit log tuning bindable with default way as YAML (since DSE 4.x).
Make sudo usage to start C* configurable.
Adding C* logs directory location to configuration
Fixing LogsDir and sudo stop C* issues
* JVM Options Tuning for Cassandra 3.x: 
Cassandra 3.x added a new way to configure heap sizes and pass other JVM parameters (via jvm.options). Priam now supports configuring common options like heap setting and choosing Garbage Collection type (G1GC/CMS) natively. Default being CMS. It logs jvm.options after tuning them.
jolynch and others added 28 commits December 6, 2017 18:43
That thread runs every 10s, so it can race with the stop API. Just
always go through start.
Fix bug in autostart shouldCassandraBeAlive logic
Letting backup status location be variable
excluding module with duplicate slf4j binding
Running both sdb clients in the same region
This is a bit easier to understand and gives us the desired behaviour of
not autostarting until a rate interval _after_ the first start.
Eliminate assumption that existence of an element in a data structure means successful backup
@Glamdring Glamdring closed this Mar 19, 2018
@Glamdring Glamdring changed the base branch from 3.x to 3.11 March 19, 2018 11:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants