[jira] [Updated] (CASSANDRA-15273) cassandra does not start with new systemd version
[ https://issues.apache.org/jira/browse/CASSANDRA-15273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-15273: Authors: Mike Kelly (was: Michael Semb Wever) Test and Documentation Plan: This will involve testing on an RPM + systemd system. Status: Patch Available (was: Open) > cassandra does not start with new systemd version > - > > Key: CASSANDRA-15273 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15273 > Project: Cassandra > Issue Type: Bug > Components: Packaging >Reporter: Aleksandr Yatskin >Assignee: Michael Semb Wever >Priority: Urgent > Attachments: > 0001-Fix-Red-Hat-init-script-on-newer-systemd-versions.patch > > > After update systemd with fixed vulnerability > https://access.redhat.com/security/cve/cve-2018-16888, the cassandra service > does not start correctly. > Environment: RHEL 7, systemd-219-67.el7_7.1, cassandra-3.11.4-1 > (https://www.apache.org/dist/cassandra/redhat/311x/cassandra-3.11.4-1.noarch.rpm) > --- > systemctl status cassandra > ● cassandra.service - LSB: distributed storage system for structured data > Loaded: loaded (/etc/rc.d/init.d/cassandra; bad; vendor preset: disabled) > Active: failed (Result: resources) since Fri 2019-08-09 17:20:26 MSK; 1s ago > Docs: man:systemd-sysv-generator(8) > Process: 2414 ExecStop=/etc/rc.d/init.d/cassandra stop (code=exited, > status=0/SUCCESS) > Process: 2463 ExecStart=/etc/rc.d/init.d/cassandra start (code=exited, > status=0/SUCCESS) > Main PID: 1884 (code=exited, status=143) > Aug 09 17:20:23 desktop43.example.com systemd[1]: Unit cassandra.service > entered failed state. > Aug 09 17:20:23 desktop43.example.com systemd[1]: cassandra.service failed. > Aug 09 17:20:23 desktop43.example.com systemd[1]: Starting LSB: distributed > storage system for structured data... > Aug 09 17:20:23 desktop43.example.com su[2473]: (to cassandra) root on none > Aug 09 17:20:26 desktop43.example.com cassandra[2463]: Starting Cassandra: OK > Aug 09 17:20:26 desktop43.example.com systemd[1]: New main PID 2545 does not > belong to service, and PID file is not owned by root. Refusing. > Aug 09 17:20:26 desktop43.example.com systemd[1]: New main PID 2545 does not > belong to service, and PID file is not owned by root. Refusing. > Aug 09 17:20:26 desktop43.example.com systemd[1]: Failed to start LSB: > distributed storage system for structured data. > Aug 09 17:20:26 desktop43.example.com systemd[1]: Unit cassandra.service > entered failed state. > Aug 09 17:20:26 desktop43.example.com systemd[1]: cassandra.service failed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15273) cassandra does not start with new systemd version
[ https://issues.apache.org/jira/browse/CASSANDRA-15273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-15273: Bug Category: Parent values: Code(13163) Complexity: Low Hanging Fruit Discovered By: User Report Platform: Linux (was: All) Severity: Normal (was: Critical) Status: Open (was: Triage Needed) > cassandra does not start with new systemd version > - > > Key: CASSANDRA-15273 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15273 > Project: Cassandra > Issue Type: Bug > Components: Packaging >Reporter: Aleksandr Yatskin >Assignee: Michael Semb Wever >Priority: Urgent > Attachments: > 0001-Fix-Red-Hat-init-script-on-newer-systemd-versions.patch > > > After update systemd with fixed vulnerability > https://access.redhat.com/security/cve/cve-2018-16888, the cassandra service > does not start correctly. > Environment: RHEL 7, systemd-219-67.el7_7.1, cassandra-3.11.4-1 > (https://www.apache.org/dist/cassandra/redhat/311x/cassandra-3.11.4-1.noarch.rpm) > --- > systemctl status cassandra > ● cassandra.service - LSB: distributed storage system for structured data > Loaded: loaded (/etc/rc.d/init.d/cassandra; bad; vendor preset: disabled) > Active: failed (Result: resources) since Fri 2019-08-09 17:20:26 MSK; 1s ago > Docs: man:systemd-sysv-generator(8) > Process: 2414 ExecStop=/etc/rc.d/init.d/cassandra stop (code=exited, > status=0/SUCCESS) > Process: 2463 ExecStart=/etc/rc.d/init.d/cassandra start (code=exited, > status=0/SUCCESS) > Main PID: 1884 (code=exited, status=143) > Aug 09 17:20:23 desktop43.example.com systemd[1]: Unit cassandra.service > entered failed state. > Aug 09 17:20:23 desktop43.example.com systemd[1]: cassandra.service failed. > Aug 09 17:20:23 desktop43.example.com systemd[1]: Starting LSB: distributed > storage system for structured data... > Aug 09 17:20:23 desktop43.example.com su[2473]: (to cassandra) root on none > Aug 09 17:20:26 desktop43.example.com cassandra[2463]: Starting Cassandra: OK > Aug 09 17:20:26 desktop43.example.com systemd[1]: New main PID 2545 does not > belong to service, and PID file is not owned by root. Refusing. > Aug 09 17:20:26 desktop43.example.com systemd[1]: New main PID 2545 does not > belong to service, and PID file is not owned by root. Refusing. > Aug 09 17:20:26 desktop43.example.com systemd[1]: Failed to start LSB: > distributed storage system for structured data. > Aug 09 17:20:26 desktop43.example.com systemd[1]: Unit cassandra.service > entered failed state. > Aug 09 17:20:26 desktop43.example.com systemd[1]: cassandra.service failed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15273) cassandra does not start with new systemd version
[ https://issues.apache.org/jira/browse/CASSANDRA-15273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-15273: Component/s: Packaging > cassandra does not start with new systemd version > - > > Key: CASSANDRA-15273 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15273 > Project: Cassandra > Issue Type: Bug > Components: Packaging >Reporter: Aleksandr Yatskin >Priority: Urgent > > After update systemd with fixed vulnerability > https://access.redhat.com/security/cve/cve-2018-16888, the cassandra service > does not start correctly. > Environment: RHEL 7, systemd-219-67.el7_7.1, cassandra-3.11.4-1 > (https://www.apache.org/dist/cassandra/redhat/311x/cassandra-3.11.4-1.noarch.rpm) > --- > systemctl status cassandra > ● cassandra.service - LSB: distributed storage system for structured data > Loaded: loaded (/etc/rc.d/init.d/cassandra; bad; vendor preset: disabled) > Active: failed (Result: resources) since Fri 2019-08-09 17:20:26 MSK; 1s ago > Docs: man:systemd-sysv-generator(8) > Process: 2414 ExecStop=/etc/rc.d/init.d/cassandra stop (code=exited, > status=0/SUCCESS) > Process: 2463 ExecStart=/etc/rc.d/init.d/cassandra start (code=exited, > status=0/SUCCESS) > Main PID: 1884 (code=exited, status=143) > Aug 09 17:20:23 desktop43.example.com systemd[1]: Unit cassandra.service > entered failed state. > Aug 09 17:20:23 desktop43.example.com systemd[1]: cassandra.service failed. > Aug 09 17:20:23 desktop43.example.com systemd[1]: Starting LSB: distributed > storage system for structured data... > Aug 09 17:20:23 desktop43.example.com su[2473]: (to cassandra) root on none > Aug 09 17:20:26 desktop43.example.com cassandra[2463]: Starting Cassandra: OK > Aug 09 17:20:26 desktop43.example.com systemd[1]: New main PID 2545 does not > belong to service, and PID file is not owned by root. Refusing. > Aug 09 17:20:26 desktop43.example.com systemd[1]: New main PID 2545 does not > belong to service, and PID file is not owned by root. Refusing. > Aug 09 17:20:26 desktop43.example.com systemd[1]: Failed to start LSB: > distributed storage system for structured data. > Aug 09 17:20:26 desktop43.example.com systemd[1]: Unit cassandra.service > entered failed state. > Aug 09 17:20:26 desktop43.example.com systemd[1]: cassandra.service failed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15273) cassandra does not start with new systemd version
[ https://issues.apache.org/jira/browse/CASSANDRA-15273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17035033#comment-17035033 ] Nate McCall commented on CASSANDRA-15273: - If someone wants to distill this into a patch, we would be interested! cc/ [~mshuler] and [~mck2] sense they are wrestling some build stuff right now. > cassandra does not start with new systemd version > - > > Key: CASSANDRA-15273 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15273 > Project: Cassandra > Issue Type: Bug >Reporter: Aleksandr Yatskin >Priority: Urgent > > After update systemd with fixed vulnerability > https://access.redhat.com/security/cve/cve-2018-16888, the cassandra service > does not start correctly. > Environment: RHEL 7, systemd-219-67.el7_7.1, cassandra-3.11.4-1 > (https://www.apache.org/dist/cassandra/redhat/311x/cassandra-3.11.4-1.noarch.rpm) > --- > systemctl status cassandra > ● cassandra.service - LSB: distributed storage system for structured data > Loaded: loaded (/etc/rc.d/init.d/cassandra; bad; vendor preset: disabled) > Active: failed (Result: resources) since Fri 2019-08-09 17:20:26 MSK; 1s ago > Docs: man:systemd-sysv-generator(8) > Process: 2414 ExecStop=/etc/rc.d/init.d/cassandra stop (code=exited, > status=0/SUCCESS) > Process: 2463 ExecStart=/etc/rc.d/init.d/cassandra start (code=exited, > status=0/SUCCESS) > Main PID: 1884 (code=exited, status=143) > Aug 09 17:20:23 desktop43.example.com systemd[1]: Unit cassandra.service > entered failed state. > Aug 09 17:20:23 desktop43.example.com systemd[1]: cassandra.service failed. > Aug 09 17:20:23 desktop43.example.com systemd[1]: Starting LSB: distributed > storage system for structured data... > Aug 09 17:20:23 desktop43.example.com su[2473]: (to cassandra) root on none > Aug 09 17:20:26 desktop43.example.com cassandra[2463]: Starting Cassandra: OK > Aug 09 17:20:26 desktop43.example.com systemd[1]: New main PID 2545 does not > belong to service, and PID file is not owned by root. Refusing. > Aug 09 17:20:26 desktop43.example.com systemd[1]: New main PID 2545 does not > belong to service, and PID file is not owned by root. Refusing. > Aug 09 17:20:26 desktop43.example.com systemd[1]: Failed to start LSB: > distributed storage system for structured data. > Aug 09 17:20:26 desktop43.example.com systemd[1]: Unit cassandra.service > entered failed state. > Aug 09 17:20:26 desktop43.example.com systemd[1]: cassandra.service failed. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15443) Add data modeling documentation to docs
[ https://issues.apache.org/jira/browse/CASSANDRA-15443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-15443: Description: Jeff Carpenter and O'Reilly have offered to contribute a complete chapter on data modeling from Cassandra, The Definitive Guide as a patch and thus under ASFv2.0 license. We've had this stubbed out for some time on our site so this will be a fantastic addition: http://cassandra.apache.org/doc/latest/data_modeling/index.html This issue will be for converting the text to our site format. For some background, see LEGAL-486. The consensus on a follow up thread on legal-discuss was that Jeff C. signing a ICLA and accepting this as a patch was good enough: https://lists.apache.org/thread.html/86485fd59bdb8d6b7932447c7cd6e1d50d23bb91aaf2680153855597%40%3Clegal-discuss.apache.org%3E was: Jeff Carpenter and O'Reilly have offered to contribute a complete chapter on data modeling from Cassandra, The Definitive Guide as a patch and thus under ASFv2.0 license. We've had this stubbed out for some time on our site so this will be a fantastic addition: http://cassandra.apache.org/doc/latest/data_modeling/index.html This issue will be for converting the text to our site format. For some background, see LEGAL-486. The consensus on a follow up thread on legal-discuss was that Jeff C. signing a CCLA and accepting this as a patch was good enough: https://lists.apache.org/thread.html/86485fd59bdb8d6b7932447c7cd6e1d50d23bb91aaf2680153855597%40%3Clegal-discuss.apache.org%3E > Add data modeling documentation to docs > --- > > Key: CASSANDRA-15443 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15443 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Nate McCall >Priority: Normal > > Jeff Carpenter and O'Reilly have offered to contribute a complete chapter on > data modeling from Cassandra, The Definitive Guide as a patch and thus under > ASFv2.0 license. > We've had this stubbed out for some time on our site so this will be a > fantastic addition: > http://cassandra.apache.org/doc/latest/data_modeling/index.html > This issue will be for converting the text to our site format. > For some background, see LEGAL-486. The consensus on a follow up thread on > legal-discuss was that Jeff C. signing a ICLA and accepting this as a patch > was good enough: > https://lists.apache.org/thread.html/86485fd59bdb8d6b7932447c7cd6e1d50d23bb91aaf2680153855597%40%3Clegal-discuss.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15443) Add data modeling documentation to docs
[ https://issues.apache.org/jira/browse/CASSANDRA-15443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-15443: Description: Jeff Carpenter and O'Reilly have offered to contribute a complete chapter on data modeling from Cassandra, The Definitive Guide as a patch and thus under ASFv2.0 license. We've had this stubbed out for some time on our site so this will be a fantastic addition: http://cassandra.apache.org/doc/latest/data_modeling/index.html This issue will be for converting the text to our site format. For some background, see LEGAL-486. The consensus on a follow up thread on legal-discuss was that Jeff C. signing a CCLA and accepting this as a patch was good enough: https://lists.apache.org/thread.html/86485fd59bdb8d6b7932447c7cd6e1d50d23bb91aaf2680153855597%40%3Clegal-discuss.apache.org%3E was: Jeff Carpenter and O'Reilly have offered to contribute a complete chapter on data modeling from Cassandra, The Definitive Guide as a patch and thus under ASFv2.0 license. We've had this stubbed out for some time on our site so this will be a fantastic addition: http://cassandra.apache.org/doc/latest/data_modeling/index.html This issue will be for converting the text to our site format. For some background, see LEGAL-486. The consensus on a follow up thread on legal-discuss was that Jeff C. signing a CCLA was good enough: https://lists.apache.org/thread.html/86485fd59bdb8d6b7932447c7cd6e1d50d23bb91aaf2680153855597%40%3Clegal-discuss.apache.org%3E > Add data modeling documentation to docs > --- > > Key: CASSANDRA-15443 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15443 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Nate McCall >Priority: Normal > > Jeff Carpenter and O'Reilly have offered to contribute a complete chapter on > data modeling from Cassandra, The Definitive Guide as a patch and thus under > ASFv2.0 license. > We've had this stubbed out for some time on our site so this will be a > fantastic addition: > http://cassandra.apache.org/doc/latest/data_modeling/index.html > This issue will be for converting the text to our site format. > For some background, see LEGAL-486. The consensus on a follow up thread on > legal-discuss was that Jeff C. signing a CCLA and accepting this as a patch > was good enough: > https://lists.apache.org/thread.html/86485fd59bdb8d6b7932447c7cd6e1d50d23bb91aaf2680153855597%40%3Clegal-discuss.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15443) Add data modeling documentation to docs
Nate McCall created CASSANDRA-15443: --- Summary: Add data modeling documentation to docs Key: CASSANDRA-15443 URL: https://issues.apache.org/jira/browse/CASSANDRA-15443 Project: Cassandra Issue Type: Task Components: Documentation/Blog Reporter: Nate McCall Jeff Carpenter and O'Reilly have offered to contribute a complete chapter on data modeling from Cassandra, The Definitive Guide as a patch and thus under ASFv2.0 license. We've had this stubbed out for some time on our site so this will be a fantastic addition: http://cassandra.apache.org/doc/latest/data_modeling/index.html This issue will be for converting the text to our site format. For some background, see LEGAL-486. The consensus on a follow up thread on legal-discuss was that Jeff C. signing a CCLA was good enough: https://lists.apache.org/thread.html/86485fd59bdb8d6b7932447c7cd6e1d50d23bb91aaf2680153855597%40%3Clegal-discuss.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15270) cassandra jdbc connection string from exasol
[ https://issues.apache.org/jira/browse/CASSANDRA-15270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-15270: Resolution: Not A Bug Status: Resolved (was: Triage Needed) Hi [~rathomai], this type of question is more appropriately asked on our user mail list. Please see the following page for details on signing up: http://cassandra.apache.org/community/ > cassandra jdbc connection string from exasol > > > Key: CASSANDRA-15270 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15270 > Project: Cassandra > Issue Type: Bug >Reporter: Manishkumar Rathod >Priority: Normal > > Hello, could you please share how we can create cassandra jdbc connection > string from exasol to connect cassndra db with SSL option and multi node > option. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15246) Add more information around commit message format expected for a patch
[ https://issues.apache.org/jira/browse/CASSANDRA-15246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16902542#comment-16902542 ] Nate McCall commented on CASSANDRA-15246: - In the process of updating everything, I realized we have changed this worflow substantially recently. [~sumanth.pasupuleti] Please see the following: http://cassandra.apache.org/doc/latest/development/documentation.html#github-based-work-flow as [~benedict] was correct about the location. Create the PR and we'll take it from there. CC/ [~mshuler] because in looking through the (thankfully detailed) SVN log for the site, i'm going to have some questions for that step... > Add more information around commit message format expected for a patch > -- > > Key: CASSANDRA-15246 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15246 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Normal > Fix For: 4.0 > > Attachments: patch_commit_message.patch > > > This is primarily from the suggestion > https://issues.apache.org/jira/browse/CASSANDRA-15013?focusedCommentId=16885255=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16885255, > to have the expected commit message format documented. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15246) Add more information around commit message format expected for a patch
[ https://issues.apache.org/jira/browse/CASSANDRA-15246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16902504#comment-16902504 ] Nate McCall commented on CASSANDRA-15246: - LGTM as well. I'll make the necessary SVN incantations to get this added and published. Thanks, [~sumanth.pasupuleti]! > Add more information around commit message format expected for a patch > -- > > Key: CASSANDRA-15246 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15246 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Normal > Fix For: 4.0 > > Attachments: patch_commit_message.patch > > > This is primarily from the suggestion > https://issues.apache.org/jira/browse/CASSANDRA-15013?focusedCommentId=16885255=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16885255, > to have the expected commit message format documented. -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15249) Add documentation on release lifecycle
[ https://issues.apache.org/jira/browse/CASSANDRA-15249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895560#comment-16895560 ] Nate McCall commented on CASSANDRA-15249: - For folks who have not been following this, please check out the comment history, suggested changes, etc. on the google doc (the little talk bubble on the upper right hand corner of the UI next to the share link) . > Add documentation on release lifecycle > -- > > Key: CASSANDRA-15249 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15249 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Website >Reporter: Sumanth Pasupuleti >Assignee: Sumanth Pasupuleti >Priority: Normal > Fix For: 4.0 > > Attachments: release_lifecycle.patch > > > Relevant dev list mail thread: > https://lists.apache.org/thread.html/1a768d057d1af5a0f373c4c399a23e65cb04c61bbfff612634b9437c@%3Cdev.cassandra.apache.org%3E > Google doc with community collaboration on documenting release lifecycle > https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15245) cassandra-all| library uses non-existent Guava classes
[
https://issues.apache.org/jira/browse/CASSANDRA-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16892387#comment-16892387
]
Nate McCall commented on CASSANDRA-15245:
-
Hi [~sarkara1] thank you for the clarification. I read this issue initially as
a dependency problem when importing cassandra-all.jar. Apologies for the
confusion.
We do update dependencies such as guava on occasion (CASSANDRA-9653,
CASSANDRA-6639), but doing so within a stable major release without a
compelling reason such as a security issue or critical bug is generally not
something we do.
Do note that trunk is running a newer version:
https://github.com/apache/cassandra/blob/trunk/build.xml#L490
> cassandra-all| library uses non-existent Guava classes
> --
>
> Key: CASSANDRA-15245
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15245
> Project: Cassandra
> Issue Type: Bug
> Components: Build, Dependencies, Packaging
>Reporter: Abhijit Sarkar
>Priority: Normal
>
> The
> [cassandra-all|https://search.maven.org/artifact/org.apache.cassandra/cassandra-all/3.11.4/jar]
> library references classes that have been removed from Guava, for example
> {{com.google.common.base.CharMatcher.DIGIT}}. This causes runtime errors like
> {code}
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.cassandra.io.sstable.format.SSTableFormat$Type
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15245) cassandra-all| library uses non-existent Guava classes
[
https://issues.apache.org/jira/browse/CASSANDRA-15245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall updated CASSANDRA-15245:
Resolution: Not A Bug
Status: Resolved (was: Triage Needed)
Hi [~sarkara1], Cassandra 3.11 uses guava 18 which still contains
CharMatcher.DIGIT.
https://github.com/apache/cassandra/blob/cassandra-3.11/build.xml#L368
We use this specific matcher in a couple of critical places dealing with
SSTable component filenames, so we would not compile if there were a mismatch.
Please double check the dependency map via mvn dependency:tree or gradle
dependencies to make sure you are not pulling in a different version of guava
into your project.
Further, I recommend taking a look simulacron instead of using cassandra-all
for any sort of testing (assuming that is what you are doing):
https://github.com/datastax/simulacron/tree/master/doc/java_api
> cassandra-all| library uses non-existent Guava classes
> --
>
> Key: CASSANDRA-15245
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15245
> Project: Cassandra
> Issue Type: Bug
> Components: Build, Dependencies, Packaging
>Reporter: Abhijit Sarkar
>Priority: Normal
>
> The
> [cassandra-all|https://search.maven.org/artifact/org.apache.cassandra/cassandra-all/3.11.4/jar]
> library references classes that have been removed from Guava, for example
> {{com.google.common.base.CharMatcher.DIGIT}}. This causes runtime errors like
> {code}
> java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.cassandra.io.sstable.format.SSTableFormat$Type
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15244) After Delete the data for particular partition , even still selecting that row. nodes all are in sync. we did full repair as well.
[ https://issues.apache.org/jira/browse/CASSANDRA-15244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-15244: Resolution: Not A Problem Status: Resolved (was: Triage Needed) Hi [~sateesh.v] I'm not sure I understand the whole message, but from what I am reading Cassandra is functioning as designed. The users email list will be a good place to ask this question. You can find details on subscribing on this page: http://cassandra.apache.org/community/ > After Delete the data for particular partition , even still selecting that > row. nodes all are in sync. we did full repair as well. > -- > > Key: CASSANDRA-15244 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15244 > Project: Cassandra > Issue Type: Bug > Components: Consistency/Streaming >Reporter: sateesh Vemulapalli >Priority: Normal > Attachments: corrupt.csv > > > CASSANDRA VER: 3.11.4 > jdk 8 > Centos: 7 > > After Deleting the row for particular partition , even after still selecting > that row. nodes all are in sync. we did full repair as well. but row still > selecting .. > > If i trying to insert same partition , even though another row creating with > space. not overwriting row. this is unexpected behavior of Cassandra. > > > INSERT SAME PARTITION KEY (UNEXPECTED BEHAVIOR:) getting space on as > prefix. > > e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-24 02:00:00 | 1999091 | > 1558639781444 | -0.663086 | 0.775391 | 0.156738 > e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-27 03:00:00 | 1999092 | > 1558639781444 | -0.663086 | 0.775391 | 0.156738 > e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-27 03:00:00 | 1999091 | > 1558639781444 | -0.663086 | 0.775391 | 0.156738 > e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-06-01 01:00:00 | 1999092 | > 1558639781444 | -0.663086 | 0.775391 | 0.156738 > e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-06-01 00:00:00 | 1999092 | > 1558639781444 | -0.663086 | 0.775391 | 0.156738 > e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-27 02:00:00 | 1999091 | > 1558639781444 | -0.663086 | 0.775391 | 0.156738 > e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-24 00:00:00 | 1999091 | > 1558639781444 | -0.663086 | 0.775391 | 0.156738 > e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-26 02:00:00 | 1999091 | > 1558639781444 | -0.663086 | 0.775391 | 0.156738 > e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-26 02:00:00 | 19990901 | > 1558639781444 | -0.663086 | 0.775391 | 0.156738 > e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-07-22 21:00:00 | 1999092 | > 1558639781444 | -0.663086 | 0.775391 | 0.156738 > e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-29 03:00:00 | 1999092 | > 1558639781444 | -0.663086 | 0.775391 | 0.156738 > e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-06-01 02:00:00 | 1999092 | > 1558639781444 | -0.663086 | 0.775391 | 0.156738 > e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-06-01 02:00:00 | 1999090 | > 1558639781444 | -0.663086 | 0.775391 | 0.156738 > e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-06-22 01:00:00 | 1999092 | > null | null | null | null > e06afb1d-2d77-4ebb-9a57-6c6c8fa8f7eb | 2019-05-25 02:00:00 | 1999091 | > 1558639781444 | -0.663086 | 0.775391 | 0.156738 > > (15 rows) -- This message was sent by Atlassian JIRA (v7.6.14#76016) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15205) Update community page to include Slack details, deprecate IRC
[ https://issues.apache.org/jira/browse/CASSANDRA-15205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-15205: Component/s: Documentation/Website > Update community page to include Slack details, deprecate IRC > - > > Key: CASSANDRA-15205 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15205 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Nate McCall >Assignee: Nate McCall >Priority: Normal > > Slack transition has been seemless so let's update the community page > (http://cassandra.apache.org/community/) to include the slack rooms and > signup details. We should keep IRC links around for references for now but > call them 'deprecated.' -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-15205) Update community page to include Slack details, deprecate IRC
Nate McCall created CASSANDRA-15205: --- Summary: Update community page to include Slack details, deprecate IRC Key: CASSANDRA-15205 URL: https://issues.apache.org/jira/browse/CASSANDRA-15205 Project: Cassandra Issue Type: Task Reporter: Nate McCall Assignee: Nate McCall Slack transition has been seemless so let's update the community page (http://cassandra.apache.org/community/) to include the slack rooms and signup details. We should keep IRC links around for references for now but call them 'deprecated.' -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15190) Is there a way to auto-clean up data whenever an old node rejoins the cluster
[ https://issues.apache.org/jira/browse/CASSANDRA-15190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16875947#comment-16875947 ] Nate McCall commented on CASSANDRA-15190: - Hi [~yupingwyp], This issue system is not the appropriate avenue for technical support. Please sign up for and direct this question to our users mailing list. Details can be found here: http://cassandra.apache.org/community/ We will be happy to work with you there. > Is there a way to auto-clean up data whenever an old node rejoins the cluster > -- > > Key: CASSANDRA-15190 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15190 > Project: Cassandra > Issue Type: Bug >Reporter: Yuping Wang >Priority: Urgent > > Due to specific reasons of our use case, we have gc grace to 15 minutes > instead of default 10 days. Since we have a large amount of nodes in our > Cassandra fleet, not surprisingly, we encounter occasionally node status > going from up to down and up again. The problem is when the down node rejoins > the cluster after 15 minutes, it automatically adds already deleted data back > and causing zombie data. > our questions: > # Is there a way to not allow a down node to rejoin the cluster? > # or is there a way to configure rejoining node not adding stale data back > regardless of how long the node is down before rejoining > # or is there a way to auto clean up the data when rejoining ? > We know adding those data back is a conservative approach to avoid data loss > but in our specific case, we are not worried about deleted data being > revived we don’t have such use case. We really need a non-defaul option > to never add back deleted data on rejoining nodes. > this functionality will ultimately be a deciding factor on whether we can > continue with Cassandra. > > Please help! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15190) Is there a way to auto-clean up data whenever an old node rejoins the cluster
[ https://issues.apache.org/jira/browse/CASSANDRA-15190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-15190: Resolution: Not A Problem Status: Resolved (was: Triage Needed) > Is there a way to auto-clean up data whenever an old node rejoins the cluster > -- > > Key: CASSANDRA-15190 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15190 > Project: Cassandra > Issue Type: Bug >Reporter: Yuping Wang >Priority: Urgent > > Due to specific reasons of our use case, we have gc grace to 15 minutes > instead of default 10 days. Since we have a large amount of nodes in our > Cassandra fleet, not surprisingly, we encounter occasionally node status > going from up to down and up again. The problem is when the down node rejoins > the cluster after 15 minutes, it automatically adds already deleted data back > and causing zombie data. > our questions: > # Is there a way to not allow a down node to rejoin the cluster? > # or is there a way to configure rejoining node not adding stale data back > regardless of how long the node is down before rejoining > # or is there a way to auto clean up the data when rejoining ? > We know adding those data back is a conservative approach to avoid data loss > but in our specific case, we are not worried about deleted data being > revived we don’t have such use case. We really need a non-defaul option > to never add back deleted data on rejoining nodes. > this functionality will ultimately be a deciding factor on whether we can > continue with Cassandra. > > Please help! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15102) Add Architecture Overview Documentation
[
https://issues.apache.org/jira/browse/CASSANDRA-15102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall updated CASSANDRA-15102:
Labels: documentation pull-request-available (was: pull-request-available)
> Add Architecture Overview Documentation
> ---
>
> Key: CASSANDRA-15102
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15102
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Elijah Augustin
>Assignee: Shane Lester
>Priority: Normal
> Labels: documentation, pull-request-available
>
> {color:#FF} {color}
> Topics/Concepts To Cover
>
> * High level overview of the architecture
> * Principles of Dynamo and how it is implemented in Cassandra
> * Brief explanation of Gossip protocol
> * Data distribution over nodes
> * Brief explanation of partition key
> * How replication of data is possible
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15102) Add Architecture Overview Documentation
[
https://issues.apache.org/jira/browse/CASSANDRA-15102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall updated CASSANDRA-15102:
Component/s: Documentation/Blog
> Add Architecture Overview Documentation
> ---
>
> Key: CASSANDRA-15102
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15102
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Elijah Augustin
>Assignee: Shane Lester
>Priority: Normal
> Labels: pull-request-available
>
> {color:#FF} {color}
> Topics/Concepts To Cover
>
> * High level overview of the architecture
> * Principles of Dynamo and how it is implemented in Cassandra
> * Brief explanation of Gossip protocol
> * Data distribution over nodes
> * Brief explanation of partition key
> * How replication of data is possible
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15103) Add Failure Detection Documentation
[ https://issues.apache.org/jira/browse/CASSANDRA-15103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-15103: Labels: documentation pull-request-available (was: pull-request-available) > Add Failure Detection Documentation > --- > > Key: CASSANDRA-15103 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15103 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Elijah Augustin >Assignee: Elijah Augustin >Priority: Normal > Labels: documentation, pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Topics/Concepts To Cover > * Why Failure Detection is needed and used > * State tracking with Gossip > * Typical Reasons for Node Failure -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15101) Add Token Ring/Range Documentation
[ https://issues.apache.org/jira/browse/CASSANDRA-15101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-15101: Labels: documentation pull-request-available (was: pull-request-available) > Add Token Ring/Range Documentation > -- > > Key: CASSANDRA-15101 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15101 > Project: Cassandra > Issue Type: Improvement > Components: Documentation/Blog, Legacy/Documentation and Website >Reporter: Elijah Augustin >Assignee: Elijah Augustin >Priority: Normal > Labels: documentation, pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Topics/Concepts To Cover > > * What the Token Ring is used for > * How Cassandra decides where data is store within the Token Ring -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15103) Add Failure Detection Documentation
[ https://issues.apache.org/jira/browse/CASSANDRA-15103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-15103: Component/s: Documentation/Blog > Add Failure Detection Documentation > --- > > Key: CASSANDRA-15103 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15103 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Elijah Augustin >Assignee: Elijah Augustin >Priority: Normal > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Topics/Concepts To Cover > * Why Failure Detection is needed and used > * State tracking with Gossip > * Typical Reasons for Node Failure -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15103) Add Failure Detection Documentation
[ https://issues.apache.org/jira/browse/CASSANDRA-15103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835233#comment-16835233 ] Nate McCall commented on CASSANDRA-15103: - [~eli10] Can you add an idea of scope in the description of this ticket? Just a few things about what you intend to cover. Looks like the same goes for CASSANDRA-15102 and CASSANDRA-15101 as well. > Add Failure Detection Documentation > --- > > Key: CASSANDRA-15103 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15103 > Project: Cassandra > Issue Type: Task >Reporter: Elijah Augustin >Assignee: Elijah Augustin >Priority: Normal > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-13451) add gossip documentation
[ https://issues.apache.org/jira/browse/CASSANDRA-13451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835230#comment-16835230 ] Nate McCall edited comment on CASSANDRA-13451 at 5/8/19 1:28 AM: - [~eli10] Thanks for having a go at the gossip docs. It looks like PR #314 was closed in favor of PR #316, but the former had some additional high level content not in the latter. Are you in a position where you would like to have a peer review on this content? Regardless, very much appreciate the effort! (EDIT) Another quick point: please feel free to subscribe to and ask questions on d...@cassandra.apache.org this is a very complicated and fundamental piece of our architecture and we'd be happy to discuss, give pointers, etc. was (Author: zznate): [~eli10] Thanks for having a go at the gossip docs. It looks like PR #314 was closed in favor of PR #316, but the former had some additional high level content not in the latter. Are you in a position where you would like to have a peer review on this content? Regardless, very much appreciate the effort! > add gossip documentation > > > Key: CASSANDRA-13451 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13451 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/Documentation and Website >Reporter: Jon Haddad >Assignee: Elijah Augustin >Priority: Normal > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > There's a decent amount of valid info here: > https://wiki.apache.org/cassandra/ArchitectureGossip and we have basically > nothing in the official docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13451) add gossip documentation
[ https://issues.apache.org/jira/browse/CASSANDRA-13451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16835230#comment-16835230 ] Nate McCall commented on CASSANDRA-13451: - [~eli10] Thanks for having a go at the gossip docs. It looks like PR #314 was closed in favor of PR #316, but the former had some additional high level content not in the latter. Are you in a position where you would like to have a peer review on this content? Regardless, very much appreciate the effort! > add gossip documentation > > > Key: CASSANDRA-13451 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13451 > Project: Cassandra > Issue Type: Improvement > Components: Legacy/Documentation and Website >Reporter: Jon Haddad >Assignee: Elijah Augustin >Priority: Normal > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > There's a decent amount of valid info here: > https://wiki.apache.org/cassandra/ArchitectureGossip and we have basically > nothing in the official docs. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14765) Evaluate Recovery Time on Single Token Cluster Test
[ https://issues.apache.org/jira/browse/CASSANDRA-14765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16813969#comment-16813969 ] Nate McCall commented on CASSANDRA-14765: - Posted! Thanks again: [http://cassandra.apache.org/blog/2019/04/09/benchmarking_streaming.html] [~djoshi3] [~sumanth.pasupuleti] [~jolynch] should we keep this open or mark as complete? Seems like we hit the goal of "evaluate" IMO. > Evaluate Recovery Time on Single Token Cluster Test > --- > > Key: CASSANDRA-14765 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14765 > Project: Cassandra > Issue Type: Sub-task > Components: Legacy/Streaming and Messaging >Reporter: Joseph Lynch >Assignee: Sumanth Pasupuleti >Priority: Normal > Attachments: 3.0.17-4.0.x-Streaming.png, cassandra_streaming.png, > image-2018-11-06-13-34-33-108.png, streaming_benchmarking.patch > > > *Setup:* > * Cassandra: 6 (2*3 rack) node i3.8xlarge AWS instance (32 cpu cores, 240GB > ram) running cassandra trunk with Jason's 14503 changes vs the same footprint > running 3.0.17 > * One datacenter, single tokens > * No compression, encryption, or coalescing turned on > *Test #1:* > ndbench loaded ~150GB of data per node into a LCS table. Then we killed a > node and let a new node stream. With a single token this should be a worst > case recovery scenario (only a few peers to stream from). > *Result:* > As the table used LCS and we didn't not have encryption on, the zero copy > transfer was used via CASSANDRA-14556. We recovered *150GB in 5 minutes,* > going at a consistent rate of about 3 gigabit per second. Theoretically we > should be able to get 10 gigabit, but this is still something like an > estimated 16x improvement over 3.0.x. We're still running the 3.0.x test for > a hard comparison. > *Follow Ups:* > We need to get more rigorous measurements (over more terminations), as well > as finishing the 3.0.x test. [~sumanth.pasupuleti] and [~djoshi3] are driving > this. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14765) Evaluate Recovery Time on Single Token Cluster Test
[ https://issues.apache.org/jira/browse/CASSANDRA-14765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16813899#comment-16813899 ] Nate McCall commented on CASSANDRA-14765: - Awesome - thanks for the post, [~sumanth.pasupuleti]. I have a couple of small edits for clarity and a few typo fixes, can I just do those in place or would you like me to post the changes back? > Evaluate Recovery Time on Single Token Cluster Test > --- > > Key: CASSANDRA-14765 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14765 > Project: Cassandra > Issue Type: Sub-task > Components: Legacy/Streaming and Messaging >Reporter: Joseph Lynch >Assignee: Sumanth Pasupuleti >Priority: Normal > Attachments: 3.0.17-4.0.x-Streaming.png, cassandra_streaming.png, > image-2018-11-06-13-34-33-108.png, streaming_benchmarking.patch > > > *Setup:* > * Cassandra: 6 (2*3 rack) node i3.8xlarge AWS instance (32 cpu cores, 240GB > ram) running cassandra trunk with Jason's 14503 changes vs the same footprint > running 3.0.17 > * One datacenter, single tokens > * No compression, encryption, or coalescing turned on > *Test #1:* > ndbench loaded ~150GB of data per node into a LCS table. Then we killed a > node and let a new node stream. With a single token this should be a worst > case recovery scenario (only a few peers to stream from). > *Result:* > As the table used LCS and we didn't not have encryption on, the zero copy > transfer was used via CASSANDRA-14556. We recovered *150GB in 5 minutes,* > going at a consistent rate of about 3 gigabit per second. Theoretically we > should be able to get 10 gigabit, but this is still something like an > estimated 16x improvement over 3.0.x. We're still running the 3.0.x test for > a hard comparison. > *Follow Ups:* > We need to get more rigorous measurements (over more terminations), as well > as finishing the 3.0.x test. [~sumanth.pasupuleti] and [~djoshi3] are driving > this. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-15051) Website: Add Page Announcing ApacheCon 2019 Event + CFP
[ https://issues.apache.org/jira/browse/CASSANDRA-15051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-15051: Resolution: Fixed Status: Resolved (was: Triage) > Website: Add Page Announcing ApacheCon 2019 Event + CFP > --- > > Key: CASSANDRA-15051 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15051 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: C. Scott Andreas >Assignee: C. Scott Andreas >Priority: Normal > Attachments: apachecon-2019.jpeg, apachecon-cfp.diff, > apachecon-cfp.png > > > This patch for the Apache Cassandra SVN repo adds a page to > cassandra.apache.org for Cassandra's presence at ApacheCon 2019. > It also contains a one-line fix for building the site via the non-Dockerized > flow (excluding vendor/ from Jekyll's search path for compilation). > When published, the URI for this page will be: > /events/2019-apache-cassandra-summit. This address won't be linked publicly > from the website as part of this commit, though we can follow with a short > blog post announcing + linking to it. > A visual rendering of the page is also attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15051) Website: Add Page Announcing ApacheCon 2019 Event + CFP
[ https://issues.apache.org/jira/browse/CASSANDRA-15051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791105#comment-16791105 ] Nate McCall commented on CASSANDRA-15051: - Reviewed and committed. Thanks, [~cscotta]! > Website: Add Page Announcing ApacheCon 2019 Event + CFP > --- > > Key: CASSANDRA-15051 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15051 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: C. Scott Andreas >Assignee: C. Scott Andreas >Priority: Normal > Attachments: apachecon-2019.jpeg, apachecon-cfp.diff, > apachecon-cfp.png > > > This patch for the Apache Cassandra SVN repo adds a page to > cassandra.apache.org for Cassandra's presence at ApacheCon 2019. > It also contains a one-line fix for building the site via the non-Dockerized > flow (excluding vendor/ from Jekyll's search path for compilation). > When published, the URI for this page will be: > /events/2019-apache-cassandra-summit. This address won't be linked publicly > from the website as part of this commit, though we can follow with a short > blog post announcing + linking to it. > A visual rendering of the page is also attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14825) Expose table schema for drivers
[ https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16681820#comment-16681820 ] Nate McCall commented on CASSANDRA-14825: - [~slebresne] I'm talking specifically about returning a single (potentially large - which is my concern) row and column. At the least we should provide selecting by keyspace, ideally keyspace and table. > Expose table schema for drivers > --- > > Key: CASSANDRA-14825 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14825 > Project: Cassandra > Issue Type: Improvement >Reporter: Chris Lohfink >Assignee: Chris Lohfink >Priority: Major > Labels: pull-request-available > Time Spent: 0.5h > Remaining Estimate: 0h > > Currently the drivers recreate the CQL for the tables by putting together the > system table values. This is very difficult to keep up to date and buggy > enough that its only even supported in Java and Python drivers. Cassandra > already has some limited output available for snapshots that we could provide > in a virtual table or new query that the drivers can fetch. This can greatly > reduce the complexity of drivers while also reducing bugs like > CASSANDRA-14822 as the underlying schema and properties change. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14883) Let Cassandra support the new JVM, Eclipse Openj9.
[ https://issues.apache.org/jira/browse/CASSANDRA-14883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16681729#comment-16681729 ] Nate McCall commented on CASSANDRA-14883: - Hi [~leesangboo] thanks for the report. So it sounds like the scope of this ticket from the title is an issue with the JAMM library? That log message is probably superfluous or maybe incorrect and in need of re-wording if there are going to be issues with some features on non-mainstream (probably wrong word?) JVMs. > Let Cassandra support the new JVM, Eclipse Openj9. > -- > > Key: CASSANDRA-14883 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14883 > Project: Cassandra > Issue Type: Improvement > Components: 4.0 > Environment: jdk8u192-b12_openj9-0.11.0 > cassandra 4.0.0_beta_20181109_build >Reporter: Lee Sangboo >Priority: Major > Fix For: 4.0.x > > > Cassandra does not currently support the new JVM, Eclipse Openj9. In internal > testing, Openj9 outperforms Hotspot. I have deployed a modified jamm library > that has a problem with the current startup, but when I started Cassandra, I > got a log message saying "Non-Oracle JVM detected." Some features, such as > unimported compact SSTables, may not work as intended "If there is no > problem, I would also like to delete the above message. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14825) Expose table schema for drivers
[ https://issues.apache.org/jira/browse/CASSANDRA-14825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16681696#comment-16681696 ] Nate McCall commented on CASSANDRA-14825: - bq. 1. Return a single row and column that just has the entire schema in it. I'm -1 on this. Good, bad or ugly, there are *a lot* of clusters out there that do multi-tennancy or otherwise have > 1k tables for which this would be untenable. Second option could work though as it would facilitate paging, etc. > Expose table schema for drivers > --- > > Key: CASSANDRA-14825 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14825 > Project: Cassandra > Issue Type: Improvement >Reporter: Chris Lohfink >Assignee: Chris Lohfink >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Currently the drivers recreate the CQL for the tables by putting together the > system table values. This is very difficult to keep up to date and buggy > enough that its only even supported in Java and Python drivers. Cassandra > already has some limited output available for snapshots that we could provide > in a virtual table or new query that the drivers can fetch. This can greatly > reduce the complexity of drivers while also reducing bugs like > CASSANDRA-14822 as the underlying schema and properties change. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14855) Message Flusher scheduling fell off the event loop, resulting in out of memory
[
https://issues.apache.org/jira/browse/CASSANDRA-14855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16681689#comment-16681689
]
Nate McCall commented on CASSANDRA-14855:
-
[~sumanth.pasupuleti] Thanks for the detailed analysis. Was this the first time
your team has seen this or has it potentially manifested in other clusters
previously?
> Message Flusher scheduling fell off the event loop, resulting in out of memory
> --
>
> Key: CASSANDRA-14855
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14855
> Project: Cassandra
> Issue Type: Bug
> Components: Core
>Reporter: Sumanth Pasupuleti
>Priority: Major
> Fix For: 3.0.17
>
> Attachments: blocked_thread_pool.png, cpu.png,
> eventloop_scheduledtasks.png, flusher running state.png, heap.png,
> heap_dump.png, read_latency.png
>
>
> We recently had a production issue where about 10 nodes in a 96 node cluster
> ran out of heap.
> From heap dump analysis, I believe there is enough evidence to indicate
> `queued` data member of the Flusher got too big, resulting in out of memory.
> Below are specifics on what we found from the heap dump (relevant screenshots
> attached):
> * non-empty "queued" data member of Flusher having retaining heap of 0.5GB,
> and multiple such instances.
> * "running" data member of Flusher having "true" value
> * Size of scheduledTasks on the eventloop was 0.
> We suspect something (maybe an exception) caused the Flusher running state to
> continue to be true, but was not able to schedule itself with the event loop.
> Could not find any ERROR in the system.log, except for following INFO logs
> around the incident time.
> {code:java}
> INFO [epollEventLoopGroup-2-4] 2018-xx-xx xx:xx:xx,592 Message.java:619 -
> Unexpected exception during request; channel = [id: 0x8d288811,
> L:/xxx.xx.xxx.xxx:7104 - R:/xxx.xx.x.xx:18886]
> io.netty.channel.unix.Errors$NativeIoException: readAddress() failed:
> Connection timed out
> at io.netty.channel.unix.Errors.newIOException(Errors.java:117)
> ~[netty-all-4.0.44.Final.jar:4.0.44.Final]
> at io.netty.channel.unix.Errors.ioResult(Errors.java:138)
> ~[netty-all-4.0.44.Final.jar:4.0.44.Final]
> at io.netty.channel.unix.FileDescriptor.readAddress(FileDescriptor.java:175)
> ~[netty-all-4.0.44.Final.jar:4.0.44.Final]
> at
> io.netty.channel.epoll.AbstractEpollChannel.doReadBytes(AbstractEpollChannel.java:238)
> ~[netty-all-4.0.44.Final.jar:4.0.44.Final]
> at
> io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:926)
> ~[netty-all-4.0.44.Final.jar:4.0.44.Final]
> at
> io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:397)
> [netty-all-4.0.44.Final.jar:4.0.44.Final]
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:302)
> [netty-all-4.0.44.Final.jar:4.0.44.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:131)
> [netty-all-4.0.44.Final.jar:4.0.44.Final]
> at
> io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144)
> [netty-all-4.0.44.Final.jar:4.0.44.Final]
> {code}
> I would like to pursue the following proposals to fix this issue:
> # ImmediateFlusher: Backport trunk's ImmediateFlusher (
> [CASSANDRA-13651|https://issues.apache.org/jira/browse/CASSANDRA-13651]
> https://github.com/apache/cassandra/commit/96ef514917e5a4829dbe864104dbc08a7d0e0cec)
> to 3.0.x and maybe to other versions as well, since ImmediateFlusher seems
> to be more robust than the existing Flusher as it does not depend on any
> running state/scheduling.
> # Make "queued" data member of the Flusher bounded to avoid any potential of
> causing out of memory due to otherwise unbounded nature.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-14855) Message Flusher scheduling fell off the event loop, resulting in out of memory
[
https://issues.apache.org/jira/browse/CASSANDRA-14855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16681689#comment-16681689
]
Nate McCall edited comment on CASSANDRA-14855 at 11/9/18 4:46 PM:
--
[~sumanth.pasupuleti] Thanks for the detailed analysis and patch. Was this the
first time your team has seen this or has it potentially manifested in other
clusters previously?
was (Author: zznate):
[~sumanth.pasupuleti] Thanks for the detailed analysis. Was this the first time
your team has seen this or has it potentially manifested in other clusters
previously?
> Message Flusher scheduling fell off the event loop, resulting in out of memory
> --
>
> Key: CASSANDRA-14855
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14855
> Project: Cassandra
> Issue Type: Bug
> Components: Core
>Reporter: Sumanth Pasupuleti
>Priority: Major
> Fix For: 3.0.17
>
> Attachments: blocked_thread_pool.png, cpu.png,
> eventloop_scheduledtasks.png, flusher running state.png, heap.png,
> heap_dump.png, read_latency.png
>
>
> We recently had a production issue where about 10 nodes in a 96 node cluster
> ran out of heap.
> From heap dump analysis, I believe there is enough evidence to indicate
> `queued` data member of the Flusher got too big, resulting in out of memory.
> Below are specifics on what we found from the heap dump (relevant screenshots
> attached):
> * non-empty "queued" data member of Flusher having retaining heap of 0.5GB,
> and multiple such instances.
> * "running" data member of Flusher having "true" value
> * Size of scheduledTasks on the eventloop was 0.
> We suspect something (maybe an exception) caused the Flusher running state to
> continue to be true, but was not able to schedule itself with the event loop.
> Could not find any ERROR in the system.log, except for following INFO logs
> around the incident time.
> {code:java}
> INFO [epollEventLoopGroup-2-4] 2018-xx-xx xx:xx:xx,592 Message.java:619 -
> Unexpected exception during request; channel = [id: 0x8d288811,
> L:/xxx.xx.xxx.xxx:7104 - R:/xxx.xx.x.xx:18886]
> io.netty.channel.unix.Errors$NativeIoException: readAddress() failed:
> Connection timed out
> at io.netty.channel.unix.Errors.newIOException(Errors.java:117)
> ~[netty-all-4.0.44.Final.jar:4.0.44.Final]
> at io.netty.channel.unix.Errors.ioResult(Errors.java:138)
> ~[netty-all-4.0.44.Final.jar:4.0.44.Final]
> at io.netty.channel.unix.FileDescriptor.readAddress(FileDescriptor.java:175)
> ~[netty-all-4.0.44.Final.jar:4.0.44.Final]
> at
> io.netty.channel.epoll.AbstractEpollChannel.doReadBytes(AbstractEpollChannel.java:238)
> ~[netty-all-4.0.44.Final.jar:4.0.44.Final]
> at
> io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:926)
> ~[netty-all-4.0.44.Final.jar:4.0.44.Final]
> at
> io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:397)
> [netty-all-4.0.44.Final.jar:4.0.44.Final]
> at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:302)
> [netty-all-4.0.44.Final.jar:4.0.44.Final]
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:131)
> [netty-all-4.0.44.Final.jar:4.0.44.Final]
> at
> io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144)
> [netty-all-4.0.44.Final.jar:4.0.44.Final]
> {code}
> I would like to pursue the following proposals to fix this issue:
> # ImmediateFlusher: Backport trunk's ImmediateFlusher (
> [CASSANDRA-13651|https://issues.apache.org/jira/browse/CASSANDRA-13651]
> https://github.com/apache/cassandra/commit/96ef514917e5a4829dbe864104dbc08a7d0e0cec)
> to 3.0.x and maybe to other versions as well, since ImmediateFlusher seems
> to be more robust than the existing Flusher as it does not depend on any
> running state/scheduling.
> # Make "queued" data member of the Flusher bounded to avoid any potential of
> causing out of memory due to otherwise unbounded nature.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14847) improvement of nodetool status -r
[
https://issues.apache.org/jira/browse/CASSANDRA-14847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668068#comment-16668068
]
Nate McCall commented on CASSANDRA-14847:
-
This seems reasonable to me. [~fyamashi] can you verify that the patch applies
cleanly on the following branches: cassandra-3.0, cassandra-3.11 and trunk?
> improvement of nodetool status -r
> -
>
> Key: CASSANDRA-14847
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14847
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Fumiya Yamashita
>Priority: Major
> Fix For: 3.11.x
>
> Attachments: 3.11.1.patch
>
>
> Hello,
> When using "nodetool status -r", I found a problem that the response time
> becomes longer depending on the number of vnodes.
> In my testing environment, when the num_token is 256 and the number of nodes
> is 6, the response takes about 60 seconds.
> It turned out that the findMaxAddressLength method in status.java is causing
> the delay.
> Despite only obtaining the maximum length of the address by the number of
> vnodes, `tokenrange * vnode` times also loop processing, there is redundancy.
> To prevent duplicate host names from being referenced every time, I modified
> to check with hash.
> In my environment, the response time has been reduced from 60 seconds to 2
> seconds.
> I attached the patch, so please check it.
> Thank you
> {code:java}
> [before]
> Datacenter: dc1
> ===
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> -- Address Load Tokens Owns (effective) Host ID Rack
> UN *** 559.32 KB 256 48.7% 0555746a-60c2-4717-b042-94ba951ef679 ***
> UN *** 721.48 KB 256 51.4% 1af4acb6-e0a0-4bcb-8bba-76ae2e225cd5 ***
> UN *** 699.98 KB 256 48.3% 5215c728-9b80-4e3c-b46b-c5b8e5eb753f ***
> UN *** 691.65 KB 256 48.1% 57da4edf-4acb-474d-b26c-27f048c37bd6 ***
> UN *** 705.66 KB 256 52.8% 07520eab-47d2-4f5d-aeeb-f6e599c9b084 ***
> UN *** 610.87 KB 256 50.7% 6b39acaf-6ed6-42e4-a357-0d258bdf87b7 ***
> time : 66s
> [after]
> Datacenter: dc1
> ===
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> -- Address Load Tokens Owns (effective) Host ID Rack
> UN *** 559.32 KB 256 48.7% 0555746a-60c2-4717-b042-94ba951ef679 ***
> UN *** 721.48 KB 256 51.4% 1af4acb6-e0a0-4bcb-8bba-76ae2e225cd5 ***
> UN *** 699.98 KB 256 48.3% 5215c728-9b80-4e3c-b46b-c5b8e5eb753f ***
> UN *** 691.65 KB 256 48.1% 57da4edf-4acb-474d-b26c-27f048c37bd6 ***
> UN *** 705.66 KB 256 52.8% 07520eab-47d2-4f5d-aeeb-f6e599c9b084 ***
> UN *** 610.87 KB 256 50.7% 6b39acaf-6ed6-42e4-a357-0d258bdf87b7 ***
> time : 2s
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14851) Blog Post: "Introducing Transient Replication"
[ https://issues.apache.org/jira/browse/CASSANDRA-14851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16668044#comment-16668044 ] Nate McCall commented on CASSANDRA-14851: - Post looks good. We just posted content from CASSANDRA-14835 so i'd like to sit on this until Monday so we have a more gradual publishing output. WDYT [~aweisberg] ? > Blog Post: "Introducing Transient Replication" > -- > > Key: CASSANDRA-14851 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14851 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: Ariel Weisberg >Assignee: Ariel Weisberg >Priority: Minor > Labels: blog > Attachments: introducing_transient_replication.patch > > > This is a blog post introducing transient replication. The patch (patch > compatible) attached applies to the website repo (outside the project's > primary Git repo). > SVN patch containing the post is attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14835) Blog Post: "Audit Logging in Apache Cassandra 4.0"
[ https://issues.apache.org/jira/browse/CASSANDRA-14835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-14835: Resolution: Fixed Status: Resolved (was: Patch Available) Posted. Thanks again [~vinaykumarcse]! > Blog Post: "Audit Logging in Apache Cassandra 4.0" > -- > > Key: CASSANDRA-14835 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14835 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: Vinay Chella >Assignee: Vinay Chella >Priority: Minor > Labels: blog > Attachments: 14835_audit_logging_cassandra.patch, > 14835_auditlog_blog_rendered.png > > > This is a blog post talking about Audit Logging feature in Apache Cassandra > 4.0 (CASSANDRA-12151). > I am sharing the google doc link at this moment for reviews, as soon as we > finalize, will send the SVN patch with markdown -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14835) Blog Post: "Audit Logging in Apache Cassandra 4.0"
[ https://issues.apache.org/jira/browse/CASSANDRA-14835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16667852#comment-16667852 ] Nate McCall commented on CASSANDRA-14835: - Assigned and toggled to patch submitted (which !patch submitted may have been the issue?) > Blog Post: "Audit Logging in Apache Cassandra 4.0" > -- > > Key: CASSANDRA-14835 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14835 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: Vinay Chella >Assignee: Vinay Chella >Priority: Minor > Labels: blog > Attachments: 14835_audit_logging_cassandra.patch, > 14835_auditlog_blog_rendered.png > > > This is a blog post talking about Audit Logging feature in Apache Cassandra > 4.0 (CASSANDRA-12151). > I am sharing the google doc link at this moment for reviews, as soon as we > finalize, will send the SVN patch with markdown -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14835) Blog Post: "Audit Logging in Apache Cassandra 4.0"
[ https://issues.apache.org/jira/browse/CASSANDRA-14835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-14835: Reviewer: Nate McCall Status: Patch Available (was: Open) > Blog Post: "Audit Logging in Apache Cassandra 4.0" > -- > > Key: CASSANDRA-14835 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14835 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: Vinay Chella >Assignee: Vinay Chella >Priority: Minor > Labels: blog > Attachments: 14835_audit_logging_cassandra.patch, > 14835_auditlog_blog_rendered.png > > > This is a blog post talking about Audit Logging feature in Apache Cassandra > 4.0 (CASSANDRA-12151). > I am sharing the google doc link at this moment for reviews, as soon as we > finalize, will send the SVN patch with markdown -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-14835) Blog Post: "Audit Logging in Apache Cassandra 4.0"
[ https://issues.apache.org/jira/browse/CASSANDRA-14835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16663086#comment-16663086 ] Nate McCall edited comment on CASSANDRA-14835 at 10/25/18 1:34 AM: --- Stylistic nits, some typos and grammatical tightening on placed on the doc as comments. Excellent work overall - this will be hugely valuable. IMO/IME let's target this for release on Monday morning PST so we have the whole week for the news cycle. [~vinaykumarcse] when you are done w. comments, move this to jekyll, send the patch and add me as the reviewer. Thanks again! was (Author: zznate): Stylistic nits, some typos and grammatical tightening on placed on the doc as comments. Excellent work overall - this will be hugely valuable. IMO/IME let's target this for release on Monday morning PST so we have the whole week for the news cycle. > Blog Post: "Audit Logging in Apache Cassandra 4.0" > -- > > Key: CASSANDRA-14835 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14835 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: Vinay Chella >Assignee: Vinay Chella >Priority: Minor > Labels: blog > > This is a blog post talking about Audit Logging feature in Apache Cassandra > 4.0 (CASSANDRA-12151). > I am sharing the google doc link at this moment for reviews, as soon as we > finalize, will send the SVN patch with markdown -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14835) Blog Post: "Audit Logging in Apache Cassandra 4.0"
[ https://issues.apache.org/jira/browse/CASSANDRA-14835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16663086#comment-16663086 ] Nate McCall commented on CASSANDRA-14835: - Stylistic nits, some typos and grammatical tightening on placed on the doc as comments. Excellent work overall - this will be hugely valuable. IMO/IME let's target this for release on Monday morning PST so we have the whole week for the news cycle. > Blog Post: "Audit Logging in Apache Cassandra 4.0" > -- > > Key: CASSANDRA-14835 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14835 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: Vinay Chella >Assignee: Vinay Chella >Priority: Minor > Labels: blog > > This is a blog post talking about Audit Logging feature in Apache Cassandra > 4.0 (CASSANDRA-12151). > I am sharing the google doc link at this moment for reviews, as soon as we > finalize, will send the SVN patch with markdown -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14827) Blog Post: "Finding Bugs in Cassandra's Internals with Property-based Testing"
[ https://issues.apache.org/jira/browse/CASSANDRA-14827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-14827: Resolution: Fixed Status: Resolved (was: Patch Available) Published and verified display and links all render on the site. Thanks [~jrwest]! > Blog Post: "Finding Bugs in Cassandra's Internals with Property-based Testing" > -- > > Key: CASSANDRA-14827 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14827 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: Jordan West >Assignee: Jordan West >Priority: Minor > Labels: blog > Attachments: quicktheories-blogpost-v2.patch, > quicktheories-blogpost.patch, rendered.png > > > This blog post introduces > [QuickTheories|https://github.com/ncredinburgh/QuickTheories] and describes > usage of it when testing -CASSANDRA-13304.- > > SVN patch contained the post and a rendered screenshot are attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14827) Blog Post: "Finding Bugs in Cassandra's Internals with Property-based Testing"
[ https://issues.apache.org/jira/browse/CASSANDRA-14827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-14827: Attachment: quicktheories-blogpost-v2.patch Status: Patch Available (was: Open) Some edits, small formatting tweaks and moving the date up to 10/18. [~jrwest] take a look and if you are cool with it, i'll post asap. > Blog Post: "Finding Bugs in Cassandra's Internals with Property-based Testing" > -- > > Key: CASSANDRA-14827 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14827 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: Jordan West >Assignee: Jordan West >Priority: Minor > Labels: blog > Attachments: quicktheories-blogpost-v2.patch, > quicktheories-blogpost.patch, rendered.png > > > This blog post introduces > [QuickTheories|https://github.com/ncredinburgh/QuickTheories] and describes > usage of it when testing -CASSANDRA-13304.- > > SVN patch contained the post and a rendered screenshot are attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14827) Blog Post: "Finding Bugs in Cassandra's Internals with Property-based Testing"
[ https://issues.apache.org/jira/browse/CASSANDRA-14827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-14827: Status: Open (was: Patch Available) > Blog Post: "Finding Bugs in Cassandra's Internals with Property-based Testing" > -- > > Key: CASSANDRA-14827 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14827 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: Jordan West >Assignee: Jordan West >Priority: Minor > Labels: blog > Attachments: quicktheories-blogpost.patch, rendered.png > > > This blog post introduces > [QuickTheories|https://github.com/ncredinburgh/QuickTheories] and describes > usage of it when testing -CASSANDRA-13304.- > > SVN patch contained the post and a rendered screenshot are attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14827) Blog Post: "Finding Bugs in Cassandra's Internals with Property-based Testing"
[ https://issues.apache.org/jira/browse/CASSANDRA-14827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-14827: Reviewer: Nate McCall Status: Patch Available (was: Open) > Blog Post: "Finding Bugs in Cassandra's Internals with Property-based Testing" > -- > > Key: CASSANDRA-14827 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14827 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: Jordan West >Assignee: Jordan West >Priority: Minor > Labels: blog > Attachments: quicktheories-blogpost.patch, rendered.png > > > This blog post introduces > [QuickTheories|https://github.com/ncredinburgh/QuickTheories] and describes > usage of it when testing -CASSANDRA-13304.- > > SVN patch contained the post and a rendered screenshot are attached. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Resolved] (CASSANDRA-14631) Add RSS support for Cassandra blog
[
https://issues.apache.org/jira/browse/CASSANDRA-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall resolved CASSANDRA-14631.
-
Resolution: Fixed
> Add RSS support for Cassandra blog
> --
>
> Key: CASSANDRA-14631
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14631
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation and Website
>Reporter: Jacques-Henri Berthemet
>Assignee: Jeff Beck
>Priority: Major
> Labels: blog
> Attachments: 14631-site.txt, Screen Shot 2018-08-17 at 5.32.08
> PM.png, Screen Shot 2018-08-17 at 5.32.25 PM.png, feed404.png
>
>
> It would be convenient to add RSS support to Cassandra blog:
> [http://cassandra.apache.org/blog/2018/08/07/faster_streaming_in_cassandra.html]
> And maybe also for other resources like new versions, but this ticket is
> about blog.
>
> {quote}From: Scott Andreas
> Sent: Wednesday, August 08, 2018 6:53 PM
> To: [d...@cassandra.apache.org|mailto:d...@cassandra.apache.org]
> Subject: Re: Apache Cassandra Blog is now live
>
> Please feel free to file a ticket (label: Documentation and Website).
>
> It looks like Jekyll, the static site generator used to build the website,
> has a plugin that generates Atom feeds if someone would like to work on
> adding one: [https://github.com/jekyll/jekyll-feed]
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14631) Add RSS support for Cassandra blog
[
https://issues.apache.org/jira/browse/CASSANDRA-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16652721#comment-16652721
]
Nate McCall commented on CASSANDRA-14631:
-
Ooh - looks like I forgot to add the generated feed.xml. Fixed - sorry folks
and thanks for the catch [~jhb]
> Add RSS support for Cassandra blog
> --
>
> Key: CASSANDRA-14631
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14631
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation and Website
>Reporter: Jacques-Henri Berthemet
>Assignee: Jeff Beck
>Priority: Major
> Labels: blog
> Attachments: 14631-site.txt, Screen Shot 2018-08-17 at 5.32.08
> PM.png, Screen Shot 2018-08-17 at 5.32.25 PM.png, feed404.png
>
>
> It would be convenient to add RSS support to Cassandra blog:
> [http://cassandra.apache.org/blog/2018/08/07/faster_streaming_in_cassandra.html]
> And maybe also for other resources like new versions, but this ticket is
> about blog.
>
> {quote}From: Scott Andreas
> Sent: Wednesday, August 08, 2018 6:53 PM
> To: [d...@cassandra.apache.org|mailto:d...@cassandra.apache.org]
> Subject: Re: Apache Cassandra Blog is now live
>
> Please feel free to file a ticket (label: Documentation and Website).
>
> It looks like Jekyll, the static site generator used to build the website,
> has a plugin that generates Atom feeds if someone would like to work on
> adding one: [https://github.com/jekyll/jekyll-feed]
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-9312) Provide a way to retrieve the write time of a CQL row
[ https://issues.apache.org/jira/browse/CASSANDRA-9312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-9312: --- Fix Version/s: (was: 2.2.x) 4.x > Provide a way to retrieve the write time of a CQL row > - > > Key: CASSANDRA-9312 > URL: https://issues.apache.org/jira/browse/CASSANDRA-9312 > Project: Cassandra > Issue Type: New Feature > Components: CQL >Reporter: Nicolas Favre-Felix >Priority: Major > Fix For: 4.x > > > There is currently no way to retrieve the "writetime" of a CQL row. This is > an issue for tables in which all dimensions are part of the primary key. > Since Cassandra already stores a cell for the CQL row, it would make sense to > provide a way to read its timestamp. This feature would be consistent with > the concept of a row as an entity containing a number of optional columns, > but able to exist on its own. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14787) nodetool status "Load" columns has wrong width
[
https://issues.apache.org/jira/browse/CASSANDRA-14787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall updated CASSANDRA-14787:
Labels: lhf nodetool (was: )
> nodetool status "Load" columns has wrong width
> --
>
> Key: CASSANDRA-14787
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14787
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
>Reporter: Lapo Luchini
>Priority: Trivial
> Labels: lhf, nodetool
>
> Using Cassandra 3.11.2 on FreeBSD, I get:
> {code:java}
> Status=Up/Down
> |/ State=Normal/Leaving/Joining/Moving
> -- AddressLoad Tokens Owns (effective) Host ID ...
> UN server1.andxor.it 11.11 MiB 256 39.6% ...
> UN server2.andxor.it 32.04 MiB 256 41.8% ...
> UN server3.andxor.it 519.33 KiB 256 40.0% ...
> UN server4.andxor.it 10.95 MiB 256 40.3% ...
> UN server5.andxor.it 11.03 MiB 256 38.4% ...
> {code}
> AFAICT this is caused by {{"%-9s"}} in
> [Status.java:292|https://github.com/apache/cassandra/blob/06209037ea56b5a2a49615a99f1542d6ea1b2947/src/java/org/apache/cassandra/tools/nodetool/Status.java#L292]
> which should be probably a 10 instead of 9.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14742) Race Condition in batchlog replica collection
[
https://issues.apache.org/jira/browse/CASSANDRA-14742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall updated CASSANDRA-14742:
Fix Version/s: 4.0
> Race Condition in batchlog replica collection
> -
>
> Key: CASSANDRA-14742
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14742
> Project: Cassandra
> Issue Type: Bug
>Reporter: Alex Petrov
>Assignee: Alex Petrov
>Priority: Major
> Labels: pull-request-available
> Fix For: 4.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When we collect nodes for it in {{StorageProxy#getBatchlogReplicas}}, we
> already filter out down replicas; subsequently they get picked up and taken
> for liveAndDown.
> There's a possible race condition due to picking tokens from token metadata
> twice (once in {{StorageProxy#getBatchlogReplicas}} and second one in
> {{ReplicaPlan#forBatchlogWrite}})
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14788) Add test coverage workflows to CircleCI config
[ https://issues.apache.org/jira/browse/CASSANDRA-14788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16633520#comment-16633520 ] Nate McCall commented on CASSANDRA-14788: - [~jmeredithco] If this is ready can you toggle to Patch Available via submit patch above? (Thanks a bunch, btw!) > Add test coverage workflows to CircleCI config > -- > > Key: CASSANDRA-14788 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14788 > Project: Cassandra > Issue Type: Improvement > Components: 4.0, Build >Reporter: Jon Meredith >Assignee: Jon Meredith >Priority: Minor > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > To support 4.0 testing efforts it's helpful to know how much of the code is > being exercised by unit tests and dtests. > Add support for running the unit tests and dtests instrumented for test > coverage on CircleCI and then combine the results of all tests (unit, dtest > with vnodes, dtest without vnodes) into a single coverage report. > All of the hard work of getting JaCoCo to work with unit tests and dtests has > already been done, it just needs wiring up. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Resolved] (CASSANDRA-14634) Review Handling Crypto Rules and update ECCN page if needed
[
https://issues.apache.org/jira/browse/CASSANDRA-14634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall resolved CASSANDRA-14634.
-
Resolution: Fixed
Exports page edited to include Cassandra
(https://svn.apache.org/repos/asf/infrastructure/site/trunk/content/licenses/exports/index.page/eccnmatrix.xml).
Email sent per instructions on http://www.apache.org/dev/crypto.html
> Review Handling Crypto Rules and update ECCN page if needed
> ---
>
> Key: CASSANDRA-14634
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14634
> Project: Cassandra
> Issue Type: Task
>Reporter: Henri Yandell
>Assignee: Nate McCall
>Priority: Blocker
> Labels: security
>
> It is suggested in LEGAL-358 that Cassandra is containing/using cryptographic
> functions and does not have an entry on the ECCN page (
> [http://www.apache.org/licenses/exports/] ).
> See [http://www.apache.org/dev/crypto.html] to review and confirm whether you
> should add something to the ECCN page, and if needed, please do so.
> The text in LEGAL-358 was:
>
> [~zznate] added a comment - 26/Dec/17 14:58
> Ok, I think I have this sorted. Our entry on that page will need to look like
> this:
> {noformat}
> Product Name VersionsECCNControlled Source
> Apache Cassandra development 5D002 ASF
> 0.8 and later 5D002 ASF
> {noformat}
> We first added SSL support in 0.8 via CASSANDRA-1567
> We rely solely on the JDK functionality for all encryption.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14634) Review Handling Crypto Rules and update ECCN page if needed
[
https://issues.apache.org/jira/browse/CASSANDRA-14634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625346#comment-16625346
]
Nate McCall commented on CASSANDRA-14634:
-
[~iamaleksey] agreed - I think I can just add a link for "The OpenSSL Project"
as others have done on the exports page. I'll get it sorted.
> Review Handling Crypto Rules and update ECCN page if needed
> ---
>
> Key: CASSANDRA-14634
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14634
> Project: Cassandra
> Issue Type: Task
>Reporter: Henri Yandell
>Assignee: Nate McCall
>Priority: Blocker
> Labels: security
>
> It is suggested in LEGAL-358 that Cassandra is containing/using cryptographic
> functions and does not have an entry on the ECCN page (
> [http://www.apache.org/licenses/exports/] ).
> See [http://www.apache.org/dev/crypto.html] to review and confirm whether you
> should add something to the ECCN page, and if needed, please do so.
> The text in LEGAL-358 was:
>
> [~zznate] added a comment - 26/Dec/17 14:58
> Ok, I think I have this sorted. Our entry on that page will need to look like
> this:
> {noformat}
> Product Name VersionsECCNControlled Source
> Apache Cassandra development 5D002 ASF
> 0.8 and later 5D002 ASF
> {noformat}
> We first added SSL support in 0.8 via CASSANDRA-1567
> We rely solely on the JDK functionality for all encryption.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-14634) Review Handling Crypto Rules and update ECCN page if needed
[
https://issues.apache.org/jira/browse/CASSANDRA-14634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall reassigned CASSANDRA-14634:
---
Assignee: Nate McCall
> Review Handling Crypto Rules and update ECCN page if needed
> ---
>
> Key: CASSANDRA-14634
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14634
> Project: Cassandra
> Issue Type: Task
>Reporter: Henri Yandell
>Assignee: Nate McCall
>Priority: Blocker
> Labels: security
>
> It is suggested in LEGAL-358 that Cassandra is containing/using cryptographic
> functions and does not have an entry on the ECCN page (
> [http://www.apache.org/licenses/exports/] ).
> See [http://www.apache.org/dev/crypto.html] to review and confirm whether you
> should add something to the ECCN page, and if needed, please do so.
> The text in LEGAL-358 was:
>
> [~zznate] added a comment - 26/Dec/17 14:58
> Ok, I think I have this sorted. Our entry on that page will need to look like
> this:
> {noformat}
> Product Name VersionsECCNControlled Source
> Apache Cassandra development 5D002 ASF
> 0.8 and later 5D002 ASF
> {noformat}
> We first added SSL support in 0.8 via CASSANDRA-1567
> We rely solely on the JDK functionality for all encryption.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14631) Add RSS support for Cassandra blog
[
https://issues.apache.org/jira/browse/CASSANDRA-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall updated CASSANDRA-14631:
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Add RSS support for Cassandra blog
> --
>
> Key: CASSANDRA-14631
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14631
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation and Website
>Reporter: Jacques-Henri Berthemet
>Assignee: Jeff Beck
>Priority: Major
> Labels: blog
> Attachments: 14631-site.txt, Screen Shot 2018-08-17 at 5.32.08
> PM.png, Screen Shot 2018-08-17 at 5.32.25 PM.png
>
>
> It would be convenient to add RSS support to Cassandra blog:
> [http://cassandra.apache.org/blog/2018/08/07/faster_streaming_in_cassandra.html]
> And maybe also for other resources like new versions, but this ticket is
> about blog.
>
> {quote}From: Scott Andreas
> Sent: Wednesday, August 08, 2018 6:53 PM
> To: [d...@cassandra.apache.org|mailto:d...@cassandra.apache.org]
> Subject: Re: Apache Cassandra Blog is now live
>
> Please feel free to file a ticket (label: Documentation and Website).
>
> It looks like Jekyll, the static site generator used to build the website,
> has a plugin that generates Atom feeds if someone would like to work on
> adding one: [https://github.com/jekyll/jekyll-feed]
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14631) Add RSS support for Cassandra blog
[
https://issues.apache.org/jira/browse/CASSANDRA-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16625255#comment-16625255
]
Nate McCall commented on CASSANDRA-14631:
-
Done and committed. Thanks [~beckje01] for the patch and [~djoshi3] for the
review!
> Add RSS support for Cassandra blog
> --
>
> Key: CASSANDRA-14631
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14631
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation and Website
>Reporter: Jacques-Henri Berthemet
>Assignee: Jeff Beck
>Priority: Major
> Labels: blog
> Attachments: 14631-site.txt, Screen Shot 2018-08-17 at 5.32.08
> PM.png, Screen Shot 2018-08-17 at 5.32.25 PM.png
>
>
> It would be convenient to add RSS support to Cassandra blog:
> [http://cassandra.apache.org/blog/2018/08/07/faster_streaming_in_cassandra.html]
> And maybe also for other resources like new versions, but this ticket is
> about blog.
>
> {quote}From: Scott Andreas
> Sent: Wednesday, August 08, 2018 6:53 PM
> To: [d...@cassandra.apache.org|mailto:d...@cassandra.apache.org]
> Subject: Re: Apache Cassandra Blog is now live
>
> Please feel free to file a ticket (label: Documentation and Website).
>
> It looks like Jekyll, the static site generator used to build the website,
> has a plugin that generates Atom feeds if someone would like to work on
> adding one: [https://github.com/jekyll/jekyll-feed]
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14631) Add RSS support for Cassandra blog
[
https://issues.apache.org/jira/browse/CASSANDRA-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16619941#comment-16619941
]
Nate McCall commented on CASSANDRA-14631:
-
That works for me - thanks, [~beckje01].
I'll get this put together later today (ie. set everything else down to
concentrate on interacting with svn).
> Add RSS support for Cassandra blog
> --
>
> Key: CASSANDRA-14631
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14631
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation and Website
>Reporter: Jacques-Henri Berthemet
>Assignee: Jeff Beck
>Priority: Major
> Labels: blog
> Attachments: 14631-site.txt, Screen Shot 2018-08-17 at 5.32.08
> PM.png, Screen Shot 2018-08-17 at 5.32.25 PM.png
>
>
> It would be convenient to add RSS support to Cassandra blog:
> [http://cassandra.apache.org/blog/2018/08/07/faster_streaming_in_cassandra.html]
> And maybe also for other resources like new versions, but this ticket is
> about blog.
>
> {quote}From: Scott Andreas
> Sent: Wednesday, August 08, 2018 6:53 PM
> To: [d...@cassandra.apache.org|mailto:d...@cassandra.apache.org]
> Subject: Re: Apache Cassandra Blog is now live
>
> Please feel free to file a ticket (label: Documentation and Website).
>
> It looks like Jekyll, the static site generator used to build the website,
> has a plugin that generates Atom feeds if someone would like to work on
> adding one: [https://github.com/jekyll/jekyll-feed]
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-14631) Add RSS support for Cassandra blog
[
https://issues.apache.org/jira/browse/CASSANDRA-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594374#comment-16594374
]
Nate McCall edited comment on CASSANDRA-14631 at 8/28/18 1:25 AM:
--
[~beckje01] I'm not clear on how fontawesome is licensed in this sense. From
looking around, it seems the icons are Creative Commons?
[https://github.com/FortAwesome/Font-Awesome/blob/master/LICENSE.txt#L8]
In the case of the CC license on the image, we have to give attribution somehow
- not sure how this works for an '.ico' file? If this is not straightforward,
i'd prefer we replace this with something public domain we can host ourselves.
was (Author: zznate):
[~beckje01] I'm not clear on how fontawesome is licensed in this sense. From
looking around, it seems the icons are Creative Commons:
[https://github.com/FortAwesome/Font-Awesome/blob/master/LICENSE.txt#L8]
Is this the case
In the case of the CC license on the image, we have to give attribution somehow
- not sure how this works for an '.ico' file? If this is not straightforward,
i'd prefer we replace this with something public domain we can host ourselves.
> Add RSS support for Cassandra blog
> --
>
> Key: CASSANDRA-14631
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14631
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation and Website
>Reporter: Jacques-Henri Berthemet
>Assignee: Jeff Beck
>Priority: Major
> Labels: blog
> Attachments: 14631-site.txt, Screen Shot 2018-08-17 at 5.32.08
> PM.png, Screen Shot 2018-08-17 at 5.32.25 PM.png
>
>
> It would be convenient to add RSS support to Cassandra blog:
> [http://cassandra.apache.org/blog/2018/08/07/faster_streaming_in_cassandra.html]
> And maybe also for other resources like new versions, but this ticket is
> about blog.
>
> {quote}From: Scott Andreas
> Sent: Wednesday, August 08, 2018 6:53 PM
> To: [d...@cassandra.apache.org|mailto:d...@cassandra.apache.org]
> Subject: Re: Apache Cassandra Blog is now live
>
> Please feel free to file a ticket (label: Documentation and Website).
>
> It looks like Jekyll, the static site generator used to build the website,
> has a plugin that generates Atom feeds if someone would like to work on
> adding one: [https://github.com/jekyll/jekyll-feed]
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-14631) Add RSS support for Cassandra blog
[
https://issues.apache.org/jira/browse/CASSANDRA-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594374#comment-16594374
]
Nate McCall edited comment on CASSANDRA-14631 at 8/28/18 1:22 AM:
--
[~beckje01] I'm not clear on how fontawesome is licensed in this sense. From
looking around, it seems the icons are Creative Commons:
[https://github.com/FortAwesome/Font-Awesome/blob/master/LICENSE.txt#L8]
Is this the case
In the case of the CC license on the image, we have to give attribution somehow
- not sure how this works for an '.ico' file? If this is not straightforward,
i'd prefer we replace this with something public domain we can host ourselves.
was (Author: zznate):
[~beckje01] I'm not clear on how fontawesome is licensed in this sense. From
looking around, it seems the icons are Creative Commons:
[https://github.com/FortAwesome/Font-Awesome/blob/master/LICENSE.txt#L8]
Is this the case
In the case of the CC license on the image, we have to give attribution somehow
- not sure how this works for an '.ico' file? If this is not straightforward,
i'd prefer we replace this with something public domain we can host ourselves.
The style sheet and code is MIT so we can do whatever with that.
> Add RSS support for Cassandra blog
> --
>
> Key: CASSANDRA-14631
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14631
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation and Website
>Reporter: Jacques-Henri Berthemet
>Assignee: Jeff Beck
>Priority: Major
> Labels: blog
> Attachments: 14631-site.txt, Screen Shot 2018-08-17 at 5.32.08
> PM.png, Screen Shot 2018-08-17 at 5.32.25 PM.png
>
>
> It would be convenient to add RSS support to Cassandra blog:
> [http://cassandra.apache.org/blog/2018/08/07/faster_streaming_in_cassandra.html]
> And maybe also for other resources like new versions, but this ticket is
> about blog.
>
> {quote}From: Scott Andreas
> Sent: Wednesday, August 08, 2018 6:53 PM
> To: [d...@cassandra.apache.org|mailto:d...@cassandra.apache.org]
> Subject: Re: Apache Cassandra Blog is now live
>
> Please feel free to file a ticket (label: Documentation and Website).
>
> It looks like Jekyll, the static site generator used to build the website,
> has a plugin that generates Atom feeds if someone would like to work on
> adding one: [https://github.com/jekyll/jekyll-feed]
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-14631) Add RSS support for Cassandra blog
[
https://issues.apache.org/jira/browse/CASSANDRA-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594374#comment-16594374
]
Nate McCall edited comment on CASSANDRA-14631 at 8/28/18 1:19 AM:
--
[~beckje01] I'm not clear on how fontawesome is licensed in this sense. From
looking around, it seems the icons are Creative Commons:
[https://github.com/FortAwesome/Font-Awesome/blob/master/LICENSE.txt#L8]
Is this the case
In the case of the CC license on the image, we have to give attribution somehow
- not sure how this works for an '.ico' file? If this is not straightforward,
i'd prefer we replace this with something public domain we can host ourselves.
The style sheet and code is MIT so we can do whatever with that.
was (Author: zznate):
[~beckje01] I'm not clear on how fontawesome is licensed in this sense. From
looking around, it seems the icons are Creative Commons:
[https://github.com/FortAwesome/Font-Awesome/blob/master/LICENSE.txt#L8]
Is this the case?
> Add RSS support for Cassandra blog
> --
>
> Key: CASSANDRA-14631
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14631
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation and Website
>Reporter: Jacques-Henri Berthemet
>Assignee: Jeff Beck
>Priority: Major
> Labels: blog
> Attachments: 14631-site.txt, Screen Shot 2018-08-17 at 5.32.08
> PM.png, Screen Shot 2018-08-17 at 5.32.25 PM.png
>
>
> It would be convenient to add RSS support to Cassandra blog:
> [http://cassandra.apache.org/blog/2018/08/07/faster_streaming_in_cassandra.html]
> And maybe also for other resources like new versions, but this ticket is
> about blog.
>
> {quote}From: Scott Andreas
> Sent: Wednesday, August 08, 2018 6:53 PM
> To: [d...@cassandra.apache.org|mailto:d...@cassandra.apache.org]
> Subject: Re: Apache Cassandra Blog is now live
>
> Please feel free to file a ticket (label: Documentation and Website).
>
> It looks like Jekyll, the static site generator used to build the website,
> has a plugin that generates Atom feeds if someone would like to work on
> adding one: [https://github.com/jekyll/jekyll-feed]
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14631) Add RSS support for Cassandra blog
[
https://issues.apache.org/jira/browse/CASSANDRA-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594374#comment-16594374
]
Nate McCall commented on CASSANDRA-14631:
-
[~beckje01] I'm not clear on how fontawesome is licensed in this sense. From
looking around, it seems the icons are Creative Commons:
[https://github.com/FortAwesome/Font-Awesome/blob/master/LICENSE.txt#L8]
Is this the case?
> Add RSS support for Cassandra blog
> --
>
> Key: CASSANDRA-14631
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14631
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation and Website
>Reporter: Jacques-Henri Berthemet
>Assignee: Jeff Beck
>Priority: Major
> Labels: blog
> Attachments: 14631-site.txt, Screen Shot 2018-08-17 at 5.32.08
> PM.png, Screen Shot 2018-08-17 at 5.32.25 PM.png
>
>
> It would be convenient to add RSS support to Cassandra blog:
> [http://cassandra.apache.org/blog/2018/08/07/faster_streaming_in_cassandra.html]
> And maybe also for other resources like new versions, but this ticket is
> about blog.
>
> {quote}From: Scott Andreas
> Sent: Wednesday, August 08, 2018 6:53 PM
> To: [d...@cassandra.apache.org|mailto:d...@cassandra.apache.org]
> Subject: Re: Apache Cassandra Blog is now live
>
> Please feel free to file a ticket (label: Documentation and Website).
>
> It looks like Jekyll, the static site generator used to build the website,
> has a plugin that generates Atom feeds if someone would like to work on
> adding one: [https://github.com/jekyll/jekyll-feed]
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14661) Blog Post: "Testing Apache Cassandra 4.0"
[ https://issues.apache.org/jira/browse/CASSANDRA-14661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594367#comment-16594367 ] Nate McCall commented on CASSANDRA-14661: - Made some edits with [~cscotta] for more active voice intro. Otherwise looks good. Committed and published. Thanks, Scott! > Blog Post: "Testing Apache Cassandra 4.0" > - > > Key: CASSANDRA-14661 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14661 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: C. Scott Andreas >Assignee: C. Scott Andreas >Priority: Minor > Labels: blog > Attachments: CASSANDRA-14661.diff, rendered.png > > > This is a blog post highlighting some of the approaches being used to test > Apache Cassandra 4.0. The patch attached applies as an SVN diff to the > website repo (outside the project's primary Git repo). > SVN patch containing the post and rendered screenshot attached. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14661) Blog Post: "Testing Apache Cassandra 4.0"
[ https://issues.apache.org/jira/browse/CASSANDRA-14661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-14661: Resolution: Fixed Status: Resolved (was: Patch Available) > Blog Post: "Testing Apache Cassandra 4.0" > - > > Key: CASSANDRA-14661 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14661 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: C. Scott Andreas >Assignee: C. Scott Andreas >Priority: Minor > Labels: blog > Attachments: CASSANDRA-14661.diff, rendered.png > > > This is a blog post highlighting some of the approaches being used to test > Apache Cassandra 4.0. The patch attached applies as an SVN diff to the > website repo (outside the project's primary Git repo). > SVN patch containing the post and rendered screenshot attached. > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14631) Add RSS support for Cassandra blog
[
https://issues.apache.org/jira/browse/CASSANDRA-14631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16589339#comment-16589339
]
Nate McCall commented on CASSANDRA-14631:
-
Will try this out later today and commit if it looks good. Thanks [~beckje01]
and [~djoshi3] for getting it ready.
> Add RSS support for Cassandra blog
> --
>
> Key: CASSANDRA-14631
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14631
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation and Website
>Reporter: Jacques-Henri Berthemet
>Assignee: Jeff Beck
>Priority: Major
> Labels: blog
> Attachments: 14631-site.txt, Screen Shot 2018-08-17 at 5.32.08
> PM.png, Screen Shot 2018-08-17 at 5.32.25 PM.png
>
>
> It would be convenient to add RSS support to Cassandra blog:
> [http://cassandra.apache.org/blog/2018/08/07/faster_streaming_in_cassandra.html]
> And maybe also for other resources like new versions, but this ticket is
> about blog.
>
> {quote}From: Scott Andreas
> Sent: Wednesday, August 08, 2018 6:53 PM
> To: [d...@cassandra.apache.org|mailto:d...@cassandra.apache.org]
> Subject: Re: Apache Cassandra Blog is now live
>
> Please feel free to file a ticket (label: Documentation and Website).
>
> It looks like Jekyll, the static site generator used to build the website,
> has a plugin that generates Atom feeds if someone would like to work on
> adding one: [https://github.com/jekyll/jekyll-feed]
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14624) Website: Add blog post for Faster Streaming
[ https://issues.apache.org/jira/browse/CASSANDRA-14624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16573934#comment-16573934 ] Nate McCall commented on CASSANDRA-14624: - Good catch! Thanks, [~iamaleksey]. Updated and pushed. > Website: Add blog post for Faster Streaming > --- > > Key: CASSANDRA-14624 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14624 > Project: Cassandra > Issue Type: Task > Components: Documentation and Website >Reporter: Dinesh Joshi >Assignee: Dinesh Joshi >Priority: Major > Labels: blog > Attachments: 14624.patch, faster-streaming-blog.patch > > > Please add a new blog post entry on the Cassandra website. It describes the > recent work on performance optimizations in Cassandra related to streaming > enhancements. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14624) Website: Add blog post for Faster Streaming
[ https://issues.apache.org/jira/browse/CASSANDRA-14624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-14624: Resolution: Fixed Status: Resolved (was: Ready to Commit) > Website: Add blog post for Faster Streaming > --- > > Key: CASSANDRA-14624 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14624 > Project: Cassandra > Issue Type: Task > Components: Documentation and Website >Reporter: Dinesh Joshi >Assignee: Dinesh Joshi >Priority: Major > Labels: blog > Attachments: 14624.patch, faster-streaming-blog.patch > > > Please add a new blog post entry on the Cassandra website. It describes the > recent work on performance optimizations in Cassandra related to streaming > enhancements. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-14624) Website: Add blog post for Faster Streaming
[ https://issues.apache.org/jira/browse/CASSANDRA-14624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16572547#comment-16572547 ] Nate McCall edited comment on CASSANDRA-14624 at 8/8/18 2:18 AM: - Good content! Did an editing pass and looks fine. I can verify this publishes and looks as it should style wise locally. Adding to SVN and publishing (I think - we'll see). was (Author: zznate): I can verify this publishes and looks as it should locally. Adding to SVN and publishing (I think - we'll see). > Website: Add blog post for Faster Streaming > --- > > Key: CASSANDRA-14624 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14624 > Project: Cassandra > Issue Type: Task > Components: Documentation and Website >Reporter: Dinesh Joshi >Assignee: Dinesh Joshi >Priority: Major > Attachments: faster-streaming-blog.patch > > > Please add a new blog post entry on the Cassandra website. It describes the > recent work on performance optimizations in Cassandra related to streaming > enhancements. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Resolved] (CASSANDRA-14624) Website: Add blog post for Faster Streaming
[ https://issues.apache.org/jira/browse/CASSANDRA-14624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall resolved CASSANDRA-14624. - Resolution: Fixed > Website: Add blog post for Faster Streaming > --- > > Key: CASSANDRA-14624 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14624 > Project: Cassandra > Issue Type: Task > Components: Documentation and Website >Reporter: Dinesh Joshi >Assignee: Dinesh Joshi >Priority: Major > Attachments: faster-streaming-blog.patch > > > Please add a new blog post entry on the Cassandra website. It describes the > recent work on performance optimizations in Cassandra related to streaming > enhancements. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14624) Website: Add blog post for Faster Streaming
[ https://issues.apache.org/jira/browse/CASSANDRA-14624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16572547#comment-16572547 ] Nate McCall commented on CASSANDRA-14624: - I can verify this publishes and looks as it should locally. Adding to SVN and publishing (I think - we'll see). > Website: Add blog post for Faster Streaming > --- > > Key: CASSANDRA-14624 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14624 > Project: Cassandra > Issue Type: Task > Components: Documentation and Website >Reporter: Dinesh Joshi >Assignee: Dinesh Joshi >Priority: Major > Attachments: faster-streaming-blog.patch > > > Please add a new blog post entry on the Cassandra website. It describes the > recent work on performance optimizations in Cassandra related to streaming > enhancements. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Resolved] (CASSANDRA-14552) Website: Add Static Blogging / Article Publishing to cassandra.apache.org
[ https://issues.apache.org/jira/browse/CASSANDRA-14552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall resolved CASSANDRA-14552. - Resolution: Fixed > Website: Add Static Blogging / Article Publishing to cassandra.apache.org > - > > Key: CASSANDRA-14552 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14552 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: C. Scott Andreas >Assignee: C. Scott Andreas >Priority: Minor > Attachments: blog-post-listing.png, blog-post.png, blog.diff > > > To make it easier for members of the community to share what's happening in > Apache Cassandra, advertise meetups, and publish other article-style content, > this patch enables simple blogging functionality via the static > cassandra.apache.org site. > > *How does it work?* > The patch uses Jekyll's built-in static blog functionality to add > article-style publishing. It adds no dynamic content, and does not include > commenting or a mechanism for accepting any user-generated content. It makes > the following changes: > – Adds a new layout file for a blog post listing and single-post detail view > (+ supporting CSS). > – Enables pagination of posts via `jekyll-paginate-v2` > – Adds documentation on how to contribute. > – And fixes a minor documentation issue specifying a Ruby version that > conflicts with earlier guidance in the documentation. > > *How do I write a post?* > The patch includes a /_templates folder with an example post to begin. Blog > posts are written using Markdown. To write a new post, copy the template into > /_posts, rename the file in keeping with the > `MM-DD--blog-post-slug.markdown` convention, add the title/date, and > begin writing. > These pages are generated via the existing build process documented in the > README – `make serve` to preview, `make` to publish. > > *What else should I know?* > The aim of this patch is to make it easy to write and publish. The "/blog" > link is currently hidden from the top nav and no posts are included in this > patch, but this can be enabled once the first article is ready. > > *What's it look like?* > Screenshots of the generated post list view and single-post view attached. > !blog-post-listing.png|width=592,height=619! > > !blog-post.png|width=592,height=619! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14552) Website: Add Static Blogging / Article Publishing to cassandra.apache.org
[ https://issues.apache.org/jira/browse/CASSANDRA-14552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16553949#comment-16553949 ] Nate McCall commented on CASSANDRA-14552: - Can confirm jekyll publishing steps work and README looks good. Committed to svn repo as revision 1836533. > Website: Add Static Blogging / Article Publishing to cassandra.apache.org > - > > Key: CASSANDRA-14552 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14552 > Project: Cassandra > Issue Type: Improvement > Components: Documentation and Website >Reporter: C. Scott Andreas >Assignee: C. Scott Andreas >Priority: Minor > Attachments: blog-post-listing.png, blog-post.png, blog.diff > > > To make it easier for members of the community to share what's happening in > Apache Cassandra, advertise meetups, and publish other article-style content, > this patch enables simple blogging functionality via the static > cassandra.apache.org site. > > *How does it work?* > The patch uses Jekyll's built-in static blog functionality to add > article-style publishing. It adds no dynamic content, and does not include > commenting or a mechanism for accepting any user-generated content. It makes > the following changes: > – Adds a new layout file for a blog post listing and single-post detail view > (+ supporting CSS). > – Enables pagination of posts via `jekyll-paginate-v2` > – Adds documentation on how to contribute. > – And fixes a minor documentation issue specifying a Ruby version that > conflicts with earlier guidance in the documentation. > > *How do I write a post?* > The patch includes a /_templates folder with an example post to begin. Blog > posts are written using Markdown. To write a new post, copy the template into > /_posts, rename the file in keeping with the > `MM-DD--blog-post-slug.markdown` convention, add the title/date, and > begin writing. > These pages are generated via the existing build process documented in the > README – `make serve` to preview, `make` to publish. > > *What else should I know?* > The aim of this patch is to make it easy to write and publish. The "/blog" > link is currently hidden from the top nav and no posts are included in this > patch, but this can be enabled once the first article is ready. > > *What's it look like?* > Screenshots of the generated post list view and single-post view attached. > !blog-post-listing.png|width=592,height=619! > > !blog-post.png|width=592,height=619! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-7814) enable describe on indices
[ https://issues.apache.org/jira/browse/CASSANDRA-7814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517721#comment-16517721 ] Nate McCall commented on CASSANDRA-7814: [~ptbannister] If you narrowed in on the cause of a flaky test (it sounds like you indeed have), please do open a new Jira with a patch for such. Thanks for bringing this up, regardless. > enable describe on indices > -- > > Key: CASSANDRA-7814 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7814 > Project: Cassandra > Issue Type: Improvement > Components: Tools >Reporter: radha >Assignee: Stefania >Priority: Minor > Labels: doc-impacting > Fix For: 2.1.8, 2.2.0 rc2, 3.0 alpha 1 > > > Describe index should be supported, right now, the only way is to export the > schema and find what it really is before updating/dropping the index. > verified in > [cqlsh 3.1.8 | Cassandra 1.2.18.1 | CQL spec 3.0.0 | Thrift protocol 19.36.2] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-14431) Replace deprecated junit.framework.Assert usages with org.junit.Assert
[ https://issues.apache.org/jira/browse/CASSANDRA-14431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall reassigned CASSANDRA-14431: --- Assignee: Iuri Sitinschi > Replace deprecated junit.framework.Assert usages with org.junit.Assert > -- > > Key: CASSANDRA-14431 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14431 > Project: Cassandra > Issue Type: Test >Reporter: Iuri Sitinschi >Assignee: Iuri Sitinschi >Priority: Minor > Attachments: 14431-trunk.txt > > > I found a lot of tests which are still using old deprecated junit class > *junit.framework.Assert*. I suggest to replace it with recommended > *org.junit.Assert*. I can prepare a patch as soon as I receive a green light. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14335) C* nodetool should report the lowest of the highest CQL protocol version supported by all clients connecting to it
[ https://issues.apache.org/jira/browse/CASSANDRA-14335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16460378#comment-16460378 ] Nate McCall commented on CASSANDRA-14335: - [~djoshi3] You have some config changes to CircleCI as part of this branch - was that intentional? Can we put those in a separate ticket if so? > C* nodetool should report the lowest of the highest CQL protocol version > supported by all clients connecting to it > -- > > Key: CASSANDRA-14335 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14335 > Project: Cassandra > Issue Type: Bug >Reporter: Dinesh Joshi >Assignee: Dinesh Joshi >Priority: Major > > While upgrading C*, it makes it hard to tell whether any client will be > affected if C* is upgraded. C* should internally store the highest protocol > version of all clients connecting to it. The lowest supported version will > help determining if any client will be adversely affected by the upgrade. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-12743) Assertion error while running compaction
[
https://issues.apache.org/jira/browse/CASSANDRA-12743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall updated CASSANDRA-12743:
Fix Version/s: 3.11.3
3.0.17
2.2.13
> Assertion error while running compaction
> -
>
> Key: CASSANDRA-12743
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12743
> Project: Cassandra
> Issue Type: Bug
> Components: Compaction
> Environment: unix
>Reporter: Jean-Baptiste Le Duigou
>Assignee: Jay Zhuang
>Priority: Major
> Fix For: 4.0, 2.2.13, 3.0.17, 3.11.3
>
>
> While running compaction I run into an error sometimes :
> {noformat}
> nodetool compact
> error: null
> -- StackTrace --
> java.lang.AssertionError
> at
> org.apache.cassandra.io.compress.CompressionMetadata$Chunk.(CompressionMetadata.java:463)
> at
> org.apache.cassandra.io.compress.CompressionMetadata.chunkFor(CompressionMetadata.java:228)
> at
> org.apache.cassandra.io.util.CompressedSegmentedFile.createMappedSegments(CompressedSegmentedFile.java:80)
> at
> org.apache.cassandra.io.util.CompressedPoolingSegmentedFile.(CompressedPoolingSegmentedFile.java:38)
> at
> org.apache.cassandra.io.util.CompressedPoolingSegmentedFile$Builder.complete(CompressedPoolingSegmentedFile.java:101)
> at
> org.apache.cassandra.io.util.SegmentedFile$Builder.complete(SegmentedFile.java:198)
> at
> org.apache.cassandra.io.sstable.format.big.BigTableWriter.openEarly(BigTableWriter.java:315)
> at
> org.apache.cassandra.io.sstable.SSTableRewriter.maybeReopenEarly(SSTableRewriter.java:171)
> at
> org.apache.cassandra.io.sstable.SSTableRewriter.append(SSTableRewriter.java:116)
> at
> org.apache.cassandra.db.compaction.writers.DefaultCompactionWriter.append(DefaultCompactionWriter.java:64)
> at
> org.apache.cassandra.db.compaction.CompactionTask.runMayThrow(CompactionTask.java:184)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> at
> org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:74)
> at
> org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:59)
> at
> org.apache.cassandra.db.compaction.CompactionManager$8.runMayThrow(CompactionManager.java:599)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Why is that happening?
> Is there anyway to provide more details (e.g. which SSTable cannot be
> compacted)?
> We are using Cassandra 2.2.7
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-12743) Assertion error while running compaction
[
https://issues.apache.org/jira/browse/CASSANDRA-12743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall updated CASSANDRA-12743:
Fix Version/s: (was: 3.11.x)
(was: 4.x)
(was: 3.0.x)
(was: 2.2.x)
4.0
> Assertion error while running compaction
> -
>
> Key: CASSANDRA-12743
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12743
> Project: Cassandra
> Issue Type: Bug
> Components: Compaction
> Environment: unix
>Reporter: Jean-Baptiste Le Duigou
>Assignee: Jay Zhuang
>Priority: Major
> Fix For: 4.0
>
>
> While running compaction I run into an error sometimes :
> {noformat}
> nodetool compact
> error: null
> -- StackTrace --
> java.lang.AssertionError
> at
> org.apache.cassandra.io.compress.CompressionMetadata$Chunk.(CompressionMetadata.java:463)
> at
> org.apache.cassandra.io.compress.CompressionMetadata.chunkFor(CompressionMetadata.java:228)
> at
> org.apache.cassandra.io.util.CompressedSegmentedFile.createMappedSegments(CompressedSegmentedFile.java:80)
> at
> org.apache.cassandra.io.util.CompressedPoolingSegmentedFile.(CompressedPoolingSegmentedFile.java:38)
> at
> org.apache.cassandra.io.util.CompressedPoolingSegmentedFile$Builder.complete(CompressedPoolingSegmentedFile.java:101)
> at
> org.apache.cassandra.io.util.SegmentedFile$Builder.complete(SegmentedFile.java:198)
> at
> org.apache.cassandra.io.sstable.format.big.BigTableWriter.openEarly(BigTableWriter.java:315)
> at
> org.apache.cassandra.io.sstable.SSTableRewriter.maybeReopenEarly(SSTableRewriter.java:171)
> at
> org.apache.cassandra.io.sstable.SSTableRewriter.append(SSTableRewriter.java:116)
> at
> org.apache.cassandra.db.compaction.writers.DefaultCompactionWriter.append(DefaultCompactionWriter.java:64)
> at
> org.apache.cassandra.db.compaction.CompactionTask.runMayThrow(CompactionTask.java:184)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> at
> org.apache.cassandra.db.compaction.CompactionTask.executeInternal(CompactionTask.java:74)
> at
> org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(AbstractCompactionTask.java:59)
> at
> org.apache.cassandra.db.compaction.CompactionManager$8.runMayThrow(CompactionManager.java:599)
> at
> org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Why is that happening?
> Is there anyway to provide more details (e.g. which SSTable cannot be
> compacted)?
> We are using Cassandra 2.2.7
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13971) Automatic certificate management using Vault
[ https://issues.apache.org/jira/browse/CASSANDRA-13971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16441812#comment-16441812 ] Nate McCall commented on CASSANDRA-13971: - [~jasobrown] MPLv2.0 is on the Category-B list as you pointed out, so we are good to go there. [~spo...@gmail.com] Just make sure you put a reference to the version and license following the pattern in [https://github.com/apache/cassandra/tree/trunk/lib/licenses|https://github.com/apache/cassandra/tree/trunk/lib/licenses.] > Automatic certificate management using Vault > > > Key: CASSANDRA-13971 > URL: https://issues.apache.org/jira/browse/CASSANDRA-13971 > Project: Cassandra > Issue Type: Improvement > Components: Streaming and Messaging >Reporter: Stefan Podkowinski >Assignee: Stefan Podkowinski >Priority: Major > Labels: security > Fix For: 4.x > > > We've been adding security features during the last years to enable users to > secure their clusters, if they are willing to use them and do so correctly. > Some features are powerful and easy to work with, such as role based > authorization. Other features that require to manage a local keystore are > rather painful to deal with. Think about setting up SSL.. > To be fair, keystore related issues and certificate handling hasn't been > invented by us. We're just following Java standards there. But that doesn't > mean that we absolutely have to, if there are better options. I'd like to > give it a shoot and find out if we can automate certificate/key handling > (PKI) by using external APIs. In this case, the implementation will be based > on [Vault|https://vaultproject.io]. But certificate management services > offered by cloud providers may also be able to handle the use-case and I > intend to create a generic, pluggable API for that. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-14372) data_file_directories config - update documentation in cassandra.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-14372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall reassigned CASSANDRA-14372: --- Assignee: Venkata Harikrishna Nukala > data_file_directories config - update documentation in cassandra.yaml > - > > Key: CASSANDRA-14372 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14372 > Project: Cassandra > Issue Type: Bug > Components: Documentation and Website >Reporter: Venkata Harikrishna Nukala >Assignee: Venkata Harikrishna Nukala >Priority: Minor > > If "data_file_directories" configuration is enabled with multiple > directories, data is partitioned by token range so that data gets distributed > evenly. But the current documentation says that "Cassandra will spread data > evenly across them, subject to the granularity of the configured compaction > strategy". Need to update this comment to reflect the correct behavior. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-12151) Audit logging for database activity
[
https://issues.apache.org/jira/browse/CASSANDRA-12151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16431160#comment-16431160
]
Nate McCall commented on CASSANDRA-12151:
-
{quote}I've now managed to update CASSANDRA-13668 by implementing IAuditLogger
and expose audit events as diagnostic events via native transport to subscribed
clients. Went pretty much as expected and seems to work fine.
{quote}
[~spo...@gmail.com] That's a fantastic idea! Thank you.
> Audit logging for database activity
> ---
>
> Key: CASSANDRA-12151
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12151
> Project: Cassandra
> Issue Type: New Feature
>Reporter: stefan setyadi
>Assignee: Vinay Chella
>Priority: Major
> Fix For: 4.x
>
> Attachments: 12151.txt, CASSANDRA_12151-benchmark.html,
> DesignProposal_AuditingFeature_ApacheCassandra_v1.docx
>
>
> we would like a way to enable cassandra to log database activity being done
> on our server.
> It should show username, remote address, timestamp, action type, keyspace,
> column family, and the query statement.
> it should also be able to log connection attempt and changes to the
> user/roles.
> I was thinking of making a new keyspace and insert an entry for every
> activity that occurs.
> Then It would be possible to query for specific activity or a query targeting
> a specific keyspace and column family.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14355) Memory leak
[
https://issues.apache.org/jira/browse/CASSANDRA-14355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426387#comment-16426387
]
Nate McCall commented on CASSANDRA-14355:
-
{quote}I am (so far) at a loss to understand what is different about this
environment.
{quote}
So other cluster(s) with the same version are running fine?
> Memory leak
> ---
>
> Key: CASSANDRA-14355
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14355
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: Debian Jessie, OpenJDK 1.8.0_151
>Reporter: Eric Evans
>Priority: Major
> Fix For: 3.11.3
>
> Attachments: 01_Screenshot from 2018-04-04 14-24-00.png,
> 02_Screenshot from 2018-04-04 14-28-33.png, 03_Screenshot from 2018-04-04
> 14-24-50.png
>
>
> We're seeing regular, frequent {{OutOfMemoryError}} exceptions. Similar to
> CASSANDRA-13754, an analysis of the heap dumps shows the heap consumed by the
> {{threadLocals}} member of the instances of
> {{io.netty.util.concurrent.FastThreadLocalThread}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14355) Memory leak
[
https://issues.apache.org/jira/browse/CASSANDRA-14355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16426118#comment-16426118
]
Nate McCall commented on CASSANDRA-14355:
-
[~urandom] Did this just start happening again or is this a continuation of the
issues you saw with CASSANDRA-13754?
Also, [~tsteinmaurer] this issue looks different from what you experienced in
CASSANDRA-13929, but have you all encountered anything like this before?
> Memory leak
> ---
>
> Key: CASSANDRA-14355
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14355
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: Debian Jessie, OpenJDK 1.8.0_151
>Reporter: Eric Evans
>Priority: Major
> Fix For: 3.11.3
>
> Attachments: 01_Screenshot from 2018-04-04 14-24-00.png,
> 02_Screenshot from 2018-04-04 14-28-33.png, 03_Screenshot from 2018-04-04
> 14-24-50.png
>
>
> We're seeing regular, frequent {{OutOfMemoryError}} exceptions. Similar to
> CASSANDRA-13754, an analysis of the heap dumps shows the heap consumed by the
> {{threadLocals}} member of the instances of
> {{io.netty.util.concurrent.FastThreadLocalThread}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-14346) Scheduled Repair in Cassandra
[
https://issues.apache.org/jira/browse/CASSANDRA-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424554#comment-16424554
]
Nate McCall edited comment on CASSANDRA-14346 at 4/3/18 8:35 PM:
-
{quote}Do you think it is good for the community that every user is inventing
this (complex) functionality again and again with different requirements on
external tools?
{quote}
Absolutely! This gets folks involved in the ecosystem, gaining an
understanding of a critical piece of functionality while allowing them to do so
in an environment in which they are comfortable.
We saw this with thrift-based drivers early on. There were at one point eight
Java drivers, but Astyanax eventually won out because it was a better design
that catered to the most common Java programming paradigms. The net effect of
this is that we trained a whole lot of devs on how to effectively use the APIs
and were at the point where we as a community answered thrift API and data
modeling questions in minutes regardless of time of day or channel in which
they came in.
{quote}We continue doing nothing and the community just solves this in
different ways.
{quote}
So we find ourselves again in a spot where opinionated designs are competing
and a vendor is offering a commercial solution. I don't call that nothing. We
have multiple working solutions _right now_ that folks will pick based on the
needs of their environments. Operations of distsys (at any scale) is quite
different from one shop to another.
We _are_ duplicating effort but fundamentally, broader community effort, not
necessarily core Cassandra development resources. The largest benefit of this
is that we will be stressing/soak testing all the recent work done on repair so
the mechanism itself will be solid. Once we figure out what works best for most
users, we build from there, perhaps focusing our efforts in the meantime on a
meaningful feedback and control mechanism to make this a whole lot easier when
we do.
I want to be clear that from what I have read and seen so far, I think
[~jolynch] and [~vinaykumarcse] have done excellent work on thinking this
through. I'm calling into question the timing and prioritization (vs.
CASSANDRA-12944 and/or general purpose management plumbing revamp) and maybe
still whether we are in process, side-car'ed or externally managed (or some
combination?), but i'll admit there are a quite debatable set of pros and cons
for each when these are all listed out.
My thoughts at this point are that we (for 4.0) ensure repair works really
well, invoked similarly as it is today out of the box and provide links to
external options, and we continue this ticket/general discussion targeting
'trunk' in a post 4.0 released world.
EDIT: to be clear, I *do* think status-quo is the way to go for shipping 4.0.
Not for beyond.
was (Author: zznate):
bq. Do you think it is good for the community that every user is inventing this
(complex) functionality again and again with different requirements on external
tools?
Absolutely! This gets folks involved in the ecosystem, gaining an understanding
of a critical piece of functionality while allowing them to do so in an
environment in which they are comfortable.
We saw this with thrift-based drivers early on. There were at one point eight
Java drivers, but Astyanax eventually won out because it was a better design
that catered to the most common Java programming paradigms. The net effect of
this is that we trained a whole lot of devs on how to effectively use the APIs
and were at the point where we as a community answered thrift API and data
modeling questions in minutes regardless of time of day or channel in which
they came in.
bq. We continue doing nothing and the community just solves this in different
ways.
So we find ourselves again in a spot where opinionated designs are competing
and a vendor is offering a commercial solution. I don't call that nothing. We
have multiple working solutions _right now_ that folks will pick based on the
needs of their environments. Operations of distsys (at any scale) is quite
different from one shop to another.
We _are_ duplicating effort but fundamentally, broader community effort, not
necessarily core Cassandra development resources. The largest benefit of this
is that we will be stressing/soak testing all the recent work done on repair so
the mechanism itself will be solid. Once we figure out what works best for most
users, we build from there, perhaps focusing our efforts in the meantime on a
meaningful feedback and control mechanism to make this a whole lot easier when
we do.
I want to be clear that from what I have read and seen so far, I think
[~jolynch] and [~vinaykumarcse] have done excellent work on thinking this
through. I'm calling into question the timing and prioritization (vs.
[jira] [Commented] (CASSANDRA-14346) Scheduled Repair in Cassandra
[ https://issues.apache.org/jira/browse/CASSANDRA-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16424554#comment-16424554 ] Nate McCall commented on CASSANDRA-14346: - bq. Do you think it is good for the community that every user is inventing this (complex) functionality again and again with different requirements on external tools? Absolutely! This gets folks involved in the ecosystem, gaining an understanding of a critical piece of functionality while allowing them to do so in an environment in which they are comfortable. We saw this with thrift-based drivers early on. There were at one point eight Java drivers, but Astyanax eventually won out because it was a better design that catered to the most common Java programming paradigms. The net effect of this is that we trained a whole lot of devs on how to effectively use the APIs and were at the point where we as a community answered thrift API and data modeling questions in minutes regardless of time of day or channel in which they came in. bq. We continue doing nothing and the community just solves this in different ways. So we find ourselves again in a spot where opinionated designs are competing and a vendor is offering a commercial solution. I don't call that nothing. We have multiple working solutions _right now_ that folks will pick based on the needs of their environments. Operations of distsys (at any scale) is quite different from one shop to another. We _are_ duplicating effort but fundamentally, broader community effort, not necessarily core Cassandra development resources. The largest benefit of this is that we will be stressing/soak testing all the recent work done on repair so the mechanism itself will be solid. Once we figure out what works best for most users, we build from there, perhaps focusing our efforts in the meantime on a meaningful feedback and control mechanism to make this a whole lot easier when we do. I want to be clear that from what I have read and seen so far, I think [~jolynch] and [~vinaykumarcse] have done excellent work on thinking this through. I'm calling into question the timing and prioritization (vs. CASSANDRA-12944 and/or general purpose management plumbing revamp) and maybe still whether we are in process, side-car'ed or externally managed (or some combination?), but i'll admit there are a quite debatable set of pros and cons for each when these are all listed out. My thoughts at this point are that we (for 4.0) ensure repair works really well, invoked similarly as it is today out of the box and provide links to external options, and we continue this ticket/general discussion targeting 'trunk' in a post 4.0 released world. > Scheduled Repair in Cassandra > - > > Key: CASSANDRA-14346 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14346 > Project: Cassandra > Issue Type: Improvement > Components: Repair >Reporter: Joseph Lynch >Priority: Major > Labels: CommunityFeedbackRequested > Fix For: 4.0 > > Attachments: ScheduledRepairV1_20180327.pdf > > > There have been many attempts to automate repair in Cassandra, which makes > sense given that it is necessary to give our users eventual consistency. Most > recently CASSANDRA-10070, CASSANDRA-8911 and CASSANDRA-13924 have all looked > for ways to solve this problem. > At Netflix we've built a scheduled repair service within Priam (our sidecar), > which we spoke about last year at NGCC. Given the positive feedback at NGCC > we focussed on getting it production ready and have now been using it in > production to repair hundreds of clusters, tens of thousands of nodes, and > petabytes of data for the past six months. Also based on feedback at NGCC we > have invested effort in figuring out how to integrate this natively into > Cassandra rather than open sourcing it as an external service (e.g. in Priam). > As such, [~vinaykumarcse] and I would like to re-work and merge our > implementation into Cassandra, and have created a [design > document|https://docs.google.com/document/d/1RV4rOrG1gwlD5IljmrIq_t45rz7H3xs9GbFSEyGzEtM/edit?usp=sharing] > showing how we plan to make it happen, including the the user interface. > As we work on the code migration from Priam to Cassandra, any feedback would > be greatly appreciated about the interface or v1 implementation features. I > have tried to call out in the document features which we explicitly consider > future work (as well as a path forward to implement them in the future) > because I would very much like to get this done before the 4.0 merge window > closes, and to do that I think aggressively pruning scope is going to be a > necessity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CASSANDRA-14346) Scheduled Repair in Cassandra
[ https://issues.apache.org/jira/browse/CASSANDRA-14346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423716#comment-16423716 ] Nate McCall commented on CASSANDRA-14346: - We've never coordinated system level maintenance tasks before, and just looking through the state machine in your design document (thanks a bunch for taking the time to put that together) makes me nervous about the amount of moving parts (basically what [~bdeggleston] pointed out above) that we'd be introducing. I'm in the camp of relying on externalized coordination and control as being an easier place to reason about what is happening in a repair session for now. There has been so much excellent work on repair over the past year that I would really like to see some of that 'bake in' to get people comfortable and trusting us again before we add a dimension of complexity. I very much appreciate that you are running a version of this in production currently, but there is just so much that can go wrong and it's a whole new paradigm for us to include in the code base. We just cant afford to screw this up again. Curious about what [~spo...@gmail.com] thinks here, as I agree that some of these ideas might be much smoother to implement with CASSANDRA-12944 in place. As Blake suggested, maybe we walk this back a bit and start from the control-plain/event loop and approach this as part of refactoring management in general? > Scheduled Repair in Cassandra > - > > Key: CASSANDRA-14346 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14346 > Project: Cassandra > Issue Type: Improvement > Components: Repair >Reporter: Joseph Lynch >Priority: Major > Labels: CommunityFeedbackRequested > Fix For: 4.0 > > Attachments: ScheduledRepairV1_20180327.pdf > > > There have been many attempts to automate repair in Cassandra, which makes > sense given that it is necessary to give our users eventual consistency. Most > recently CASSANDRA-10070, CASSANDRA-8911 and CASSANDRA-13924 have all looked > for ways to solve this problem. > At Netflix we've built a scheduled repair service within Priam (our sidecar), > which we spoke about last year at NGCC. Given the positive feedback at NGCC > we focussed on getting it production ready and have now been using it in > production to repair hundreds of clusters, tens of thousands of nodes, and > petabytes of data for the past six months. Also based on feedback at NGCC we > have invested effort in figuring out how to integrate this natively into > Cassandra rather than open sourcing it as an external service (e.g. in Priam). > As such, [~vinaykumarcse] and I would like to re-work and merge our > implementation into Cassandra, and have created a [design > document|https://docs.google.com/document/d/1RV4rOrG1gwlD5IljmrIq_t45rz7H3xs9GbFSEyGzEtM/edit?usp=sharing] > showing how we plan to make it happen, including the the user interface. > As we work on the code migration from Priam to Cassandra, any feedback would > be greatly appreciated about the interface or v1 implementation features. I > have tried to call out in the document features which we explicitly consider > future work (as well as a path forward to implement them in the future) > because I would very much like to get this done before the 4.0 merge window > closes, and to do that I think aggressively pruning scope is going to be a > necessity. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-14349) Untracked CDC segment files are not deleted after replay
[ https://issues.apache.org/jira/browse/CASSANDRA-14349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall updated CASSANDRA-14349: Status: Patch Available (was: Open) > Untracked CDC segment files are not deleted after replay > > > Key: CASSANDRA-14349 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14349 > Project: Cassandra > Issue Type: Bug > Components: Local Write-Read Paths >Reporter: Shichao An >Assignee: Shichao An >Priority: Minor > > When CDC is enabled, a hard link to each commit log file will be created in > cdc_raw directory. Those commit logs with CDC mutations will also have cdc > index files created along with the hard links; these are intended for the > consumer to handle and clean them up. > However, if we don't produce any CDC traffic, those hard links in cdc_raw > will be never cleaned up (because hard links will still be created, without > the index files), whereas the real original commit logs are correctly deleted > after replay during process startup. This will results in many untracked hard > links in cdc_raw if we restart the cassandra process many times. I am able to > use CCM to reproduce it in trunk version which has the CASSANDRA-12148 > changes. > This seems a bug in handleReplayedSegment of the commit log segment manager > which neglects to take care of CDC commit logs. I will attach a patch here. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14349) Untracked CDC segment files are not deleted after replay
[ https://issues.apache.org/jira/browse/CASSANDRA-14349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16418351#comment-16418351 ] Nate McCall commented on CASSANDRA-14349: - [~shichao.an] thanks for the patch. Just to clarify, this is for an edge case where: * CDC is enabled, creating hard links * CDC has no traffic * Cassandra is restarted * original hardlinks remain, but new ones are created for current process? > Untracked CDC segment files are not deleted after replay > > > Key: CASSANDRA-14349 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14349 > Project: Cassandra > Issue Type: Bug > Components: Local Write-Read Paths >Reporter: Shichao An >Assignee: Shichao An >Priority: Minor > > When CDC is enabled, a hard link to each commit log file will be created in > cdc_raw directory. Those commit logs with CDC mutations will also have cdc > index files created along with the hard links; these are intended for the > consumer to handle and clean them up. > However, if we don't produce any CDC traffic, those hard links in cdc_raw > will be never cleaned up (because hard links will still be created, without > the index files), whereas the real original commit logs are correctly deleted > after replay during process startup. This will results in many untracked hard > links in cdc_raw if we restart the cassandra process many times. I am able to > use CCM to reproduce it in trunk version which has the CASSANDRA-12148 > changes. > This seems a bug in handleReplayedSegment of the commit log segment manager > which neglects to take care of CDC commit logs. I will attach a patch here. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13653) Create meaningful toString() methods
[
https://issues.apache.org/jira/browse/CASSANDRA-13653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16414723#comment-16414723
]
Nate McCall commented on CASSANDRA-13653:
-
[~djanand] Took a quick peek - looks like you have a format issue as the diffs
for each class are essentially the whole file. Can you double check you have
adhered to the formatting guidelines?
[http://cassandra.apache.org/doc/latest/development/code_style.html]
Appreciate the effort, regardless.
> Create meaningful toString() methods
>
>
> Key: CASSANDRA-13653
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13653
> Project: Cassandra
> Issue Type: Bug
>Reporter: Jeff Jirsa
>Assignee: Jogesh Anand
>Priority: Trivial
> Labels: lhf, low-hanging-fruit
>
> True low-hanging fruit, good for a first-time contributor:
> There are a lot of classes without meaningful {{toString()}} implementations.
> Some of these would be very nice to have for investigating bug reports.
> Some good places to start:
> - CQL3 statements (UpdateStatement, DeleteStatement, etc), QueryOptions, and
> Restrictions
> Some packages not to worry about:
> - Deep internals that don't already have them
> (org.apache.cassandra.db.rows/partitions/etc)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Resolved] (CASSANDRA-14250) ERROR 1815 (HY000) at line 28: Internal error: TimedOutException: Default TException.
[ https://issues.apache.org/jira/browse/CASSANDRA-14250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nate McCall resolved CASSANDRA-14250. - Resolution: Not A Bug > ERROR 1815 (HY000) at line 28: Internal error: TimedOutException: Default > TException. > - > > Key: CASSANDRA-14250 > URL: https://issues.apache.org/jira/browse/CASSANDRA-14250 > Project: Cassandra > Issue Type: Bug > Components: CQL > Environment: VMware Linux server CentOs 6 > [cqlsh 5.0.1 | Cassandra 3.11.1 | CQL spec 3.4.4 | Native protocol v4] > Server version: 10.0.33-MariaDB MariaDB Server > >Reporter: Silvio Amorim >Priority: Major > Fix For: 3.11.3 > > > Hello, > Good day, > > Please I need your support for solve this problem and I thank you for all the > help you can give. > I'm facing a very strange problem with cassandradb. > I installed cassandra version 3.11.1 on a virtual machine with linux CentOS, > where I had already converted a mysql database to MariaDb (Server version: > 10.0.33-MariaDB MariaDB Server). > > In MariaDB I created the following table: > > CREATE TABLE `tbl_paciente_crm_anexo` ( > `id` int (11) NOT NULL PRIMARY KEY, > `id_crm` int (11) DEFAULT NULL, > `patient_id` int (11) DEFAULT NULL, > `int_organization` int (11) NOT NULL DEFAULT '0', > `id_pasta_pai` int (11) DEFAULT '0', > `file` longblob, > `file_file` longblob, > `subtitle` varchar (255) DEFAULT NULL, > `key words` text, > `filename` varchar (100) DEFAULT NULL, > `filename` varchar (20) DEFAULT NULL, > `char_type` char (1) DEFAULT NULL, > blob data_foto, > `date_inclusion` blob, > `data_alteracao` blob, > `data_ult_access` blob, > `log_user` varchar (10) DEFAULT NULL, > `sign` char (1) DEFAULT NULL, > `login_id` int (11) DEFAULT NULL, > `xml` blob, > `hash_xml` varchar (64) DEFAULT NULL, > `hash_verif` varchar (64) DEFAULT NULL, > `status_assinatura` varchar (2) DEFAULT NULL > ) ENGINE = CASSANDRA thrift_host = `localhost` keyspace =` md_paciente` > column_family = `cf_crm_anexo`; > > > I'm trying to load 147Gb of data into this table, and there are 2 blob fields > in this table . > > * +During the loading, and after inserting several records, I receive the > following error:+ > > [root@srvmeddbh01 dbbkp]# mysql -p -u root –pxx > medicina_intramed *ERROR 1815 (HY000) at line 28: Internal error: TimedOutException: Default > TException*. > [root@srvmeddbh01 dbbkp]# > > *+Script with insert command and blob field converted to hex:+* > > INSERT INTO `tbl_paciente_crm_anexo` (`id`, `assinar`, `data_alteracao` , > `arquivo` , `arquivo_imagem`, `data_foto`, `data_inclusao`, > `data_ult_acesso`, `hash_verif`, ` > hash_xml`, `id_assinatura`, `id_crm`, `id_organizacao`, `id_paciente`, > `id_pasta_pai`, `legenda`, `log_usuario`, `nome_arquivo`, `palavras_chaves`, > `status_assinatura`, > `tamanhoarquivo`, `tipo_arquivo`, `xml` ) VALUES (30276,' ',' > ',x'FFD8FFE000104A464946000101480048FFE1004C457869664D4D002A0008000201120003000100010 > 00087690004000100260002A0020004000101E0A003000400010280FFED003850686F746F73686F7020332E30003842494D04043842494D04250 > 010D41D8CD98F00B204E9800998ECF8427EFFC0001108028001E00301220002110...); > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14250) ERROR 1815 (HY000) at line 28: Internal error: TimedOutException: Default TException.
[
https://issues.apache.org/jira/browse/CASSANDRA-14250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16414615#comment-16414615
]
Nate McCall commented on CASSANDRA-14250:
-
This seems like more of a system load issue to me. The fact that you were able
to get far enough to generate a {{TimedOutException}} implies that everything
more or less "worked."
You might be better served by looking into throttling options available to
mariadb's bulk load or increasing the amount of hardware (and not using a VM).
I'm going to mark this as closed/won't fix given this is out of scope from the
project's perspective. It might be worth opening a thread on the user mailing
list asking if anyone else has tuned mariadb's bulk load for this.
> ERROR 1815 (HY000) at line 28: Internal error: TimedOutException: Default
> TException.
> -
>
> Key: CASSANDRA-14250
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14250
> Project: Cassandra
> Issue Type: Bug
> Components: CQL
> Environment: VMware Linux server CentOs 6
> [cqlsh 5.0.1 | Cassandra 3.11.1 | CQL spec 3.4.4 | Native protocol v4]
> Server version: 10.0.33-MariaDB MariaDB Server
>
>Reporter: Silvio Amorim
>Priority: Major
> Fix For: 3.11.3
>
>
> Hello,
> Good day,
>
> Please I need your support for solve this problem and I thank you for all the
> help you can give.
> I'm facing a very strange problem with cassandradb.
> I installed cassandra version 3.11.1 on a virtual machine with linux CentOS,
> where I had already converted a mysql database to MariaDb (Server version:
> 10.0.33-MariaDB MariaDB Server).
>
> In MariaDB I created the following table:
>
> CREATE TABLE `tbl_paciente_crm_anexo` (
> `id` int (11) NOT NULL PRIMARY KEY,
> `id_crm` int (11) DEFAULT NULL,
> `patient_id` int (11) DEFAULT NULL,
> `int_organization` int (11) NOT NULL DEFAULT '0',
> `id_pasta_pai` int (11) DEFAULT '0',
> `file` longblob,
> `file_file` longblob,
> `subtitle` varchar (255) DEFAULT NULL,
> `key words` text,
> `filename` varchar (100) DEFAULT NULL,
> `filename` varchar (20) DEFAULT NULL,
> `char_type` char (1) DEFAULT NULL,
> blob data_foto,
> `date_inclusion` blob,
> `data_alteracao` blob,
> `data_ult_access` blob,
> `log_user` varchar (10) DEFAULT NULL,
> `sign` char (1) DEFAULT NULL,
> `login_id` int (11) DEFAULT NULL,
> `xml` blob,
> `hash_xml` varchar (64) DEFAULT NULL,
> `hash_verif` varchar (64) DEFAULT NULL,
> `status_assinatura` varchar (2) DEFAULT NULL
> ) ENGINE = CASSANDRA thrift_host = `localhost` keyspace =` md_paciente`
> column_family = `cf_crm_anexo`;
>
>
> I'm trying to load 147Gb of data into this table, and there are 2 blob fields
> in this table .
>
> * +During the loading, and after inserting several records, I receive the
> following error:+
>
> [root@srvmeddbh01 dbbkp]# mysql -p -u root –pxx
> medicina_intramed *ERROR 1815 (HY000) at line 28: Internal error: TimedOutException: Default
> TException*.
> [root@srvmeddbh01 dbbkp]#
>
> *+Script with insert command and blob field converted to hex:+*
>
> INSERT INTO `tbl_paciente_crm_anexo` (`id`, `assinar`, `data_alteracao` ,
> `arquivo` , `arquivo_imagem`, `data_foto`, `data_inclusao`,
> `data_ult_acesso`, `hash_verif`, `
> hash_xml`, `id_assinatura`, `id_crm`, `id_organizacao`, `id_paciente`,
> `id_pasta_pai`, `legenda`, `log_usuario`, `nome_arquivo`, `palavras_chaves`,
> `status_assinatura`,
> `tamanhoarquivo`, `tipo_arquivo`, `xml` ) VALUES (30276,' ','
> ',x'FFD8FFE000104A464946000101480048FFE1004C457869664D4D002A0008000201120003000100010
> 00087690004000100260002A0020004000101E0A003000400010280FFED003850686F746F73686F7020332E30003842494D04043842494D04250
> 010D41D8CD98F00B204E9800998ECF8427EFFC0001108028001E00301220002110...);
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-14260) Refactor pair to avoid boxing longs/ints
[
https://issues.apache.org/jira/browse/CASSANDRA-14260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407223#comment-16407223
]
Nate McCall edited comment on CASSANDRA-14260 at 3/20/18 11:32 PM:
---
-Nit on the {{equals()}} and {{hashCode()}} impls - those would be cleaner
using {{Objects.equals}} and {{Objects.hash}} (JDK version).- We use these in a
lot of other places in the code already and would be nice to keep new
contributions in line with such.
Update: [~jjirsa] just pointed out that Objects autoboxes with primitives which
was news to me and sort of makes sense when i think about it.
was (Author: zznate):
Nit on the {{equals()}} and {{hashCode()}} impls - those would be cleaner using
{{Objects.equals}} and {{Objects.hash}} (JDK version). We use these in a lot of
other places in the code already and would be nice to keep new contributions in
line with such.
> Refactor pair to avoid boxing longs/ints
>
>
> Key: CASSANDRA-14260
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14260
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Jeff Jirsa
>Assignee: Jeff Jirsa
>Priority: Minor
> Fix For: 4.x
>
>
> We uses Pair all over the place, and in many cases either/both of X and
> Y are primitives (ints, longs), and we end up boxing them into Integers and
> Longs. We should have specialized versions that take primitives.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-14260) Refactor pair to avoid boxing longs/ints
[
https://issues.apache.org/jira/browse/CASSANDRA-14260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16407223#comment-16407223
]
Nate McCall commented on CASSANDRA-14260:
-
Nit on the {{equals()}} and {{hashCode()}} impls - those would be cleaner using
{{Objects.equals}} and {{Objects.hash}} (JDK version). We use these in a lot of
other places in the code already and would be nice to keep new contributions in
line with such.
> Refactor pair to avoid boxing longs/ints
>
>
> Key: CASSANDRA-14260
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14260
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Jeff Jirsa
>Assignee: Jeff Jirsa
>Priority: Minor
> Fix For: 4.x
>
>
> We uses Pair all over the place, and in many cases either/both of X and
> Y are primitives (ints, longs), and we end up boxing them into Integers and
> Longs. We should have specialized versions that take primitives.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-7622) Implement virtual tables
[ https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16396386#comment-16396386 ] Nate McCall edited comment on CASSANDRA-7622 at 3/13/18 1:56 AM: - [~cnlwsu] (inadvertently) commented on the PR directly: [https://github.com/apache/cassandra/pull/205] Should do the rest of the discussion here as to not spam the ticket. was (Author: zznate): [~cnlwsu] (inadvertently) commented on the PR directly: [https://github.com/apache/cassandra/pull/205] > Implement virtual tables > > > Key: CASSANDRA-7622 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7622 > Project: Cassandra > Issue Type: Improvement >Reporter: Tupshin Harper >Assignee: Chris Lohfink >Priority: Major > Fix For: 4.x > > > There are a variety of reasons to want virtual tables, which would be any > table that would be backed by an API, rather than data explicitly managed and > stored as sstables. > One possible use case would be to expose JMX data through CQL as a > resurrection of CASSANDRA-3527. > Another is a more general framework to implement the ability to expose yaml > configuration information. So it would be an alternate approach to > CASSANDRA-7370. > A possible implementation would be in terms of CASSANDRA-7443, but I am not > presupposing. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-7622) Implement virtual tables
[ https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16396386#comment-16396386 ] Nate McCall commented on CASSANDRA-7622: [~cnlwsu] (inadvertently) commented on the PR directly: [https://github.com/apache/cassandra/pull/205] > Implement virtual tables > > > Key: CASSANDRA-7622 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7622 > Project: Cassandra > Issue Type: Improvement >Reporter: Tupshin Harper >Assignee: Chris Lohfink >Priority: Major > Fix For: 4.x > > > There are a variety of reasons to want virtual tables, which would be any > table that would be backed by an API, rather than data explicitly managed and > stored as sstables. > One possible use case would be to expose JMX data through CQL as a > resurrection of CASSANDRA-3527. > Another is a more general framework to implement the ability to expose yaml > configuration information. So it would be an alternate approach to > CASSANDRA-7370. > A possible implementation would be in terms of CASSANDRA-7443, but I am not > presupposing. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Issue Comment Deleted] (CASSANDRA-7622) Implement virtual tables
[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall updated CASSANDRA-7622:
---
Comment: was deleted
(was: Github user zznate commented on a diff in the pull request:
https://github.com/apache/cassandra/pull/205#discussion_r173962979
--- Diff: src/java/org/apache/cassandra/db/VirtualTable.java ---
@@ -0,0 +1,148 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.cassandra.db;
+
+import static java.lang.String.format;
+
+import java.lang.reflect.InvocationTargetException;
+import java.util.List;
+
+import org.apache.cassandra.cql3.Operation;
+import org.apache.cassandra.cql3.QueryOptions;
+import org.apache.cassandra.cql3.UpdateParameters;
+import org.apache.cassandra.cql3.statements.SelectStatement;
+import org.apache.cassandra.db.filter.DataLimits;
+import org.apache.cassandra.db.partitions.PartitionUpdate;
+import org.apache.cassandra.db.rows.Row;
+import org.apache.cassandra.exceptions.CassandraException;
+import org.apache.cassandra.exceptions.ConfigurationException;
+import org.apache.cassandra.exceptions.InvalidRequestException;
+import org.apache.cassandra.schema.TableMetadata;
+import org.apache.cassandra.transport.messages.ResultMessage;
+import org.apache.cassandra.utils.FBUtilities;
+
+import com.google.common.collect.Lists;
+
+/**
+ * Base requirements for a VirtualTable. This is required to provide
metadata about the virtual table, such as the
+ * partition and clustering keys, and provide a ReadQuery for a
SelectStatement.
+ */
+public abstract class VirtualTable
+{
+protected final TableMetadata metadata;
+protected String keyspace;
+protected String name;
+
+public VirtualTable(TableMetadata metadata)
+{
+this.metadata = metadata;
+}
+
+public String getTableName()
+{
+return this.metadata.name;
+}
+
+/**
+ * Is this table writable?
+ *
+ * @return True if UPDATE is supported
+ */
+public boolean writable()
+{
+return false;
+}
+
+/**
+ * If the table allows unrestricted queries (ie filter on clustering
key with no partition). Since These tables are
+ * not backed by the C* data model, this restriction isnt always
necessary.
+ */
+public boolean allowFiltering()
+{
+return true;
+}
+
+/**
+ * Return some implementation of a ReadQuery for a given select
statement and query options.
+ *
+ * @param selectStatement
+ * @param options
+ * @param limits
+ * @param nowInSec
+ * @return ReadQuery
+ */
+public abstract ReadQuery getQuery(SelectStatement selectStatement,
QueryOptions options, DataLimits limits,
+int nowInSec);
+
+/**
+ * Execute an update operation.
+ *
+ * @param partitionKey
+ *partition key for the update.
+ * @param params
+ *parameters of the update.
+ */
+public void mutate(DecoratedKey partitionKey, Row row) throws
CassandraException
+{
+// this should not be called unless writable is overridden
+throw new InvalidRequestException("Not Implemented");
+}
+
+public static Class classFromName(String name)
+{
+String className = name.contains(".")
+? name
+: "org.apache.cassandra.db.virtual." + name;
+Class strategyClass =
FBUtilities.classForName(className, "virtual table");
+
+if (!VirtualTable.class.isAssignableFrom(strategyClass))
+{
+throw new ConfigurationException(format("Compaction strategy
class %s is not derived from VirtualTable",
+
[jira] [Issue Comment Deleted] (CASSANDRA-7622) Implement virtual tables
[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall updated CASSANDRA-7622:
---
Comment: was deleted
(was: Github user zznate commented on a diff in the pull request:
https://github.com/apache/cassandra/pull/205#discussion_r173965848
--- Diff: src/java/org/apache/cassandra/schema/Schema.java ---
@@ -713,20 +727,24 @@ private void dropView(ViewMetadata metadata)
private void dropTable(TableMetadata metadata)
{
-ColumnFamilyStore cfs =
Keyspace.open(metadata.keyspace).getColumnFamilyStore(metadata.name);
-assert cfs != null;
-// make sure all the indexes are dropped, or else.
-cfs.indexManager.markAllIndexesRemoved();
-
CompactionManager.instance.interruptCompactionFor(Collections.singleton(metadata),
true);
-if (DatabaseDescriptor.isAutoSnapshot())
-
cfs.snapshot(Keyspace.getTimestampedSnapshotNameWithPrefix(cfs.name,
ColumnFamilyStore.SNAPSHOT_DROP_PREFIX));
-
CommitLog.instance.forceRecycleAllSegments(Collections.singleton(metadata.id));
--- End diff --
I'll go back and look through comments, but _can_ i drop a VT?
)
> Implement virtual tables
>
>
> Key: CASSANDRA-7622
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7622
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Tupshin Harper
>Assignee: Chris Lohfink
>Priority: Major
> Fix For: 4.x
>
>
> There are a variety of reasons to want virtual tables, which would be any
> table that would be backed by an API, rather than data explicitly managed and
> stored as sstables.
> One possible use case would be to expose JMX data through CQL as a
> resurrection of CASSANDRA-3527.
> Another is a more general framework to implement the ability to expose yaml
> configuration information. So it would be an alternate approach to
> CASSANDRA-7370.
> A possible implementation would be in terms of CASSANDRA-7443, but I am not
> presupposing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Issue Comment Deleted] (CASSANDRA-7622) Implement virtual tables
[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall updated CASSANDRA-7622:
---
Comment: was deleted
(was: Github user zznate commented on a diff in the pull request:
https://github.com/apache/cassandra/pull/205#discussion_r173962324
--- Diff: src/java/org/apache/cassandra/db/Keyspace.java ---
@@ -331,8 +337,11 @@ private Keyspace(String keyspaceName, boolean
loadSSTables)
this.viewManager = new ViewManager(this);
for (TableMetadata cfm : metadata.tablesAndViews())
{
-logger.trace("Initializing {}.{}", getName(), cfm.name);
-initCf(Schema.instance.getTableMetadataRef(cfm.id),
loadSSTables);
+logger.info("Initializing {}.{}", getName(), cfm.name);
--- End diff --
Change from trace() to info() intentional?
)
> Implement virtual tables
>
>
> Key: CASSANDRA-7622
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7622
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Tupshin Harper
>Assignee: Chris Lohfink
>Priority: Major
> Fix For: 4.x
>
>
> There are a variety of reasons to want virtual tables, which would be any
> table that would be backed by an API, rather than data explicitly managed and
> stored as sstables.
> One possible use case would be to expose JMX data through CQL as a
> resurrection of CASSANDRA-3527.
> Another is a more general framework to implement the ability to expose yaml
> configuration information. So it would be an alternate approach to
> CASSANDRA-7370.
> A possible implementation would be in terms of CASSANDRA-7443, but I am not
> presupposing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Issue Comment Deleted] (CASSANDRA-7622) Implement virtual tables
[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall updated CASSANDRA-7622:
---
Comment: was deleted
(was: Github user zznate commented on a diff in the pull request:
https://github.com/apache/cassandra/pull/205#discussion_r173963715
--- Diff: src/java/org/apache/cassandra/db/marshal/AbstractType.java ---
@@ -529,4 +529,9 @@ public void checkComparable()
{
return testAssignment(receiver.type);
}
+
+public ByteBuffer unsafeDecompose(Object object)
--- End diff --
I dunno... that a pretty shoot-self-in-foot thing to add the the
marshalling API. What's the reasoning?
)
> Implement virtual tables
>
>
> Key: CASSANDRA-7622
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7622
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Tupshin Harper
>Assignee: Chris Lohfink
>Priority: Major
> Fix For: 4.x
>
>
> There are a variety of reasons to want virtual tables, which would be any
> table that would be backed by an API, rather than data explicitly managed and
> stored as sstables.
> One possible use case would be to expose JMX data through CQL as a
> resurrection of CASSANDRA-3527.
> Another is a more general framework to implement the ability to expose yaml
> configuration information. So it would be an alternate approach to
> CASSANDRA-7370.
> A possible implementation would be in terms of CASSANDRA-7443, but I am not
> presupposing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Issue Comment Deleted] (CASSANDRA-7622) Implement virtual tables
[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall updated CASSANDRA-7622:
---
Comment: was deleted
(was: Github user zznate commented on a diff in the pull request:
https://github.com/apache/cassandra/pull/205#discussion_r173957234
--- Diff:
src/java/org/apache/cassandra/cql3/statements/CreateTableStatement.java ---
@@ -195,11 +217,27 @@ public TableMetadata toTableMetadata()
private final Multiset definedNames =
HashMultiset.create(1);
private final boolean ifNotExists;
+private final boolean isVirtual;
+private final String klass;
public RawStatement(CFName name, boolean ifNotExists)
{
super(name);
this.ifNotExists = ifNotExists;
+this.isVirtual = false;
+this.klass = null;
+
+assert isVirtual == (klass != null);
--- End diff --
Sorta OT, but we should just stop doing this and use `Preconditions` to
throw IAEs. I hate the fact that a user can disable so much of our error
checking w. a command line arg.
)
> Implement virtual tables
>
>
> Key: CASSANDRA-7622
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7622
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Tupshin Harper
>Assignee: Chris Lohfink
>Priority: Major
> Fix For: 4.x
>
>
> There are a variety of reasons to want virtual tables, which would be any
> table that would be backed by an API, rather than data explicitly managed and
> stored as sstables.
> One possible use case would be to expose JMX data through CQL as a
> resurrection of CASSANDRA-3527.
> Another is a more general framework to implement the ability to expose yaml
> configuration information. So it would be an alternate approach to
> CASSANDRA-7370.
> A possible implementation would be in terms of CASSANDRA-7443, but I am not
> presupposing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Issue Comment Deleted] (CASSANDRA-7622) Implement virtual tables
[
https://issues.apache.org/jira/browse/CASSANDRA-7622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate McCall updated CASSANDRA-7622:
---
Comment: was deleted
(was: Github user zznate commented on a diff in the pull request:
https://github.com/apache/cassandra/pull/205#discussion_r173964414
--- Diff: src/java/org/apache/cassandra/db/virtual/Settings.java ---
@@ -0,0 +1,161 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+package org.apache.cassandra.db.virtual;
+
+import java.lang.reflect.Array;
+import java.lang.reflect.Field;
+import java.lang.reflect.Modifier;
+import java.util.HashMap;
+import java.util.Map;
+import java.util.function.Consumer;
+
+import org.apache.cassandra.config.Config;
+import org.apache.cassandra.config.DatabaseDescriptor;
+import org.apache.cassandra.cql3.CQL3Type;
+import org.apache.cassandra.cql3.ColumnIdentifier;
+import org.apache.cassandra.cql3.QueryOptions;
+import org.apache.cassandra.cql3.restrictions.StatementRestrictions;
+import org.apache.cassandra.db.DecoratedKey;
+import org.apache.cassandra.db.InMemoryVirtualTable;
+import org.apache.cassandra.db.rows.Row;
+import org.apache.cassandra.exceptions.CassandraException;
+import org.apache.cassandra.exceptions.InvalidRequestException;
+import org.apache.cassandra.schema.ColumnMetadata;
+import org.apache.cassandra.schema.TableMetadata;
+import org.apache.cassandra.service.StorageProxy;
+import org.apache.cassandra.service.StorageService;
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+import com.google.common.collect.ImmutableMap;
+
+public class Settings extends InMemoryVirtualTable
+{
+private static final Logger logger =
LoggerFactory.getLogger(Settings.class);
+private static Map WRITABLES =
ImmutableMap.builder()
+ .put("batch_size_warn_threshold_in_kb", v ->
DatabaseDescriptor.setBatchSizeWarnThresholdInKB(Integer.parseInt(v)))
+ .put("batch_size_fail_threshold_in_kb", v ->
DatabaseDescriptor.setBatchSizeFailThresholdInKB(Integer.parseInt(v)))
+
+ .put("compaction_throughput_mb_per_sec", v ->
StorageService.instance.setCompactionThroughputMbPerSec(Integer.parseInt(v)))
+ .put("concurrent_compactors", v ->
StorageService.instance.setConcurrentCompactors(Integer.parseInt(v)))
+ .put("concurrent_validations", v ->
StorageService.instance.setConcurrentValidators(Integer.parseInt(v)))
+
+ .put("tombstone_warn_threshold", v ->
DatabaseDescriptor.setTombstoneWarnThreshold(Integer.parseInt(v)))
+ .put("tombstone_failure_threshold", v ->
DatabaseDescriptor.setTombstoneFailureThreshold(Integer.parseInt(v)))
+
+ .put("hinted_handoff_enabled", v ->
StorageProxy.instance.setHintedHandoffEnabled(Boolean.parseBoolean(v)))
+ .put("hinted_handoff_throttle_in_kb", v ->
StorageService.instance.setHintedHandoffThrottleInKB(Integer.parseInt(v)))
+
+ .put("incremental_backups", v ->
DatabaseDescriptor.setIncrementalBackupsEnabled(Boolean.parseBoolean(v)))
+
+ .put("inter_dc_stream_throughput_outbound_megabits_per_sec", v ->
StorageService.instance.setInterDCStreamThroughputMbPerSec(Integer.parseInt(v)))
+ .put("stream_throughput_outbound_megabits_per_sec", v ->
StorageService.instance.setStreamThroughputMbPerSec(Integer.parseInt(v)))
+
+ .put("truncate_request_timeout_in_ms", v ->
StorageService.instance.setTruncateRpcTimeout(Long.parseLong(v)))
+ .put("cas_contention_timeout_in_ms", v ->
StorageService.instance.setCasContentionTimeout(Long.parseLong(v)))
+ .put("counter_write_request_timeout_in_ms", v ->
StorageService.instance.setCounterWriteRpcTimeout(Long.parseLong(v)))
+ .put("write_request_timeout_in_ms", v ->
StorageService.instance.setWriteRpcTimeout(Long.parseLong(v)))
+ .put("range_request_timeout_in_ms", v ->
