[jira] [Updated] (CASSANDRA-16491) nodetool bootstrap resume returns success even if there is an error during bootstrap
[ https://issues.apache.org/jira/browse/CASSANDRA-16491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonard Ma updated CASSANDRA-16491: --- Description: "nodetool bootstrap resume” prints a relevant error message if the operation fails, but it then proceeds to return a normal error code. It ignores the ProgressEventType.ERROR message that arrives before COMPLETE. This also happens when we handle failed connections. BootstrapMonitor should at least track whether or not it has seen an error, which would allow us to throw when one occurs after signaling, and therefore to inform callers. Trunk PR: [https://github.com/apache/cassandra/pull/1949] was:"nodetool bootstrap resume” prints a relevant error message if the operation fails, but it then proceeds to return a normal error code. It ignores the ProgressEventType.ERROR message that arrives before COMPLETE. This also happens when we handle failed connections. BootstrapMonitor should at least track whether or not it has seen an error, which would allow us to throw when one occurs after signaling, and therefore to inform callers. > nodetool bootstrap resume returns success even if there is an error during > bootstrap > > > Key: CASSANDRA-16491 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16491 > Project: Cassandra > Issue Type: Bug > Components: Tool/nodetool >Reporter: Caleb Rackliffe >Assignee: Leonard Ma >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x > > Time Spent: 10m > Remaining Estimate: 0h > > "nodetool bootstrap resume” prints a relevant error message if the operation > fails, but it then proceeds to return a normal error code. It ignores the > ProgressEventType.ERROR message that arrives before COMPLETE. This also > happens when we handle failed connections. BootstrapMonitor should at least > track whether or not it has seen an error, which would allow us to throw when > one occurs after signaling, and therefore to inform callers. > Trunk PR: [https://github.com/apache/cassandra/pull/1949] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16491) nodetool bootstrap resume returns success even if there is an error during bootstrap
[ https://issues.apache.org/jira/browse/CASSANDRA-16491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leonard Ma updated CASSANDRA-16491: --- Test and Documentation Plan: Test locally using ccm, `nodetool bootstrap resume`, and JConsole Status: Patch Available (was: In Progress) > nodetool bootstrap resume returns success even if there is an error during > bootstrap > > > Key: CASSANDRA-16491 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16491 > Project: Cassandra > Issue Type: Bug > Components: Tool/nodetool >Reporter: Caleb Rackliffe >Assignee: Leonard Ma >Priority: Normal > Fix For: 3.0.x, 3.11.x, 4.0.x > > Time Spent: 10m > Remaining Estimate: 0h > > "nodetool bootstrap resume” prints a relevant error message if the operation > fails, but it then proceeds to return a normal error code. It ignores the > ProgressEventType.ERROR message that arrives before COMPLETE. This also > happens when we handle failed connections. BootstrapMonitor should at least > track whether or not it has seen an error, which would allow us to throw when > one occurs after signaling, and therefore to inform callers. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17816) WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
[
https://issues.apache.org/jira/browse/CASSANDRA-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623531#comment-17623531
]
Erick Ramirez commented on CASSANDRA-17816:
---
I’ve completed final verification in staging and [published to
production|https://github.com/apache/cassandra-website#merging-asf-staging-to-asf-site]:
{noformat}
$ git branch
* trunk
$ git fetch origin
$ git checkout asf-site
Branch ‘asf-site’ set up to track remote branch ‘asf-site’ from ‘origin’.
Switched to a new branch ‘asf-site’
$ git branch
* asf-site
trunk
$ git reset --hard origin/asf-staging
HEAD is now at 82363267 generate docs for 65d5b952
$ git push -f origin asf-site
Username for ‘https://github.com’: erickramirezau
Password for ‘https://erickramire...@github.com’:
Total 0 (delta 0), reused 0 (delta 0)
To https://github.com/apache/cassandra-website.git
+ 64dd28d6...82363267 asf-site -> asf-site (forced update)
{noformat}
The updated page is now live on the site –
https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html.
> WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
> --
>
> Key: CASSANDRA-17816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17816
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
> Attachments: c17816-01-blog-post.png
>
>
> This ticket is to capture the work associated with fixing broken links on the
> blog [Apache Cassandra 4.1: Configuration
> Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
> {quote}
> For a full list of affected parameters, mapping of old to new names and
> supported units and how things work in general, please refer to the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> {quote}
> h3. Backward Compatibility
> We support backward compatibility. All properties which have changed names
> can still be set with the old name. Wherever the value format was also
> changed from numeric value to number + unit value, you can still use the old
> name + the old numeric value format. For a full list of parameter
> changes/mapping of old to new parameters and what to expect, please refer to
> the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> The correct page to link is
> https://cassandra.apache.org/doc/latest/cassandra/configuration/configuration.html.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-site updated (64dd28d6 -> 82363267)
This is an automated email from the ASF dual-hosted git repository. erickramirezau pushed a change to branch asf-site in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 64dd28d6 generate docs for 4212d0c8 add 65d5b952 WEBSITE - Fixed broken links in 4.1 Configuration Standardization blog add 82363267 generate docs for 65d5b952 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (64dd28d6) \ N -- N -- N refs/heads/asf-site (82363267) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: ...assandra-4.1-Configuration-Standardization.html | 4 ++-- ...assandra-4.1-Configuration-Standardization.adoc | 4 ++-- site-ui/build/ui-bundle.zip| Bin 4746956 -> 4746956 bytes 3 files changed, 4 insertions(+), 4 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17816) WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
[
https://issues.apache.org/jira/browse/CASSANDRA-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623528#comment-17623528
]
Erick Ramirez edited comment on CASSANDRA-17816 at 10/25/22 2:55 AM:
-
The build completed in 26 minutes and the updated page is now in staging –
[https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]
was (Author: JIRAUSER285101):
The build completed in 26 minutes and the page is now in staging –
https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html
> WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
> --
>
> Key: CASSANDRA-17816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17816
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
> Attachments: c17816-01-blog-post.png
>
>
> This ticket is to capture the work associated with fixing broken links on the
> blog [Apache Cassandra 4.1: Configuration
> Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
> {quote}
> For a full list of affected parameters, mapping of old to new names and
> supported units and how things work in general, please refer to the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> {quote}
> h3. Backward Compatibility
> We support backward compatibility. All properties which have changed names
> can still be set with the old name. Wherever the value format was also
> changed from numeric value to number + unit value, you can still use the old
> name + the old numeric value format. For a full list of parameter
> changes/mapping of old to new parameters and what to expect, please refer to
> the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> The correct page to link is
> https://cassandra.apache.org/doc/latest/cassandra/configuration/configuration.html.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17816) WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
[
https://issues.apache.org/jira/browse/CASSANDRA-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623528#comment-17623528
]
Erick Ramirez commented on CASSANDRA-17816:
---
The build completed in 26 minutes and the page is now in staging –
https://cassandra.staged.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html
> WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
> --
>
> Key: CASSANDRA-17816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17816
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
> Attachments: c17816-01-blog-post.png
>
>
> This ticket is to capture the work associated with fixing broken links on the
> blog [Apache Cassandra 4.1: Configuration
> Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
> {quote}
> For a full list of affected parameters, mapping of old to new names and
> supported units and how things work in general, please refer to the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> {quote}
> h3. Backward Compatibility
> We support backward compatibility. All properties which have changed names
> can still be set with the old name. Wherever the value format was also
> changed from numeric value to number + unit value, you can still use the old
> name + the old numeric value format. For a full list of parameter
> changes/mapping of old to new parameters and what to expect, please refer to
> the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> The correct page to link is
> https://cassandra.apache.org/doc/latest/cassandra/configuration/configuration.html.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (76082825 -> 82363267)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 76082825 generate docs for 4212d0c8 add 65d5b952 WEBSITE - Fixed broken links in 4.1 Configuration Standardization blog new 82363267 generate docs for 65d5b952 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (76082825) \ N -- N -- N refs/heads/asf-staging (82363267) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: ...assandra-4.1-Configuration-Standardization.html | 4 ++-- ...assandra-4.1-Configuration-Standardization.adoc | 4 ++-- site-ui/build/ui-bundle.zip| Bin 4746956 -> 4746956 bytes 3 files changed, 4 insertions(+), 4 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17816) WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
[
https://issues.apache.org/jira/browse/CASSANDRA-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623519#comment-17623519
]
Erick Ramirez commented on CASSANDRA-17816:
---
The website content is getting built in staging:
||Branch||PR||Commit||Build||
|{{trunk}}|[#186|https://github.com/apache/cassandra-website/pull/186]|[65d5b95|https://github.com/apache/cassandra-website/commit/65d5b952ffcb86d8d5e3f04425d678d9e5c42ee4]|[#690|https://ci-cassandra.apache.org/job/cassandra-website/690/]|
> WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
> --
>
> Key: CASSANDRA-17816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17816
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
> Attachments: c17816-01-blog-post.png
>
>
> This ticket is to capture the work associated with fixing broken links on the
> blog [Apache Cassandra 4.1: Configuration
> Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
> {quote}
> For a full list of affected parameters, mapping of old to new names and
> supported units and how things work in general, please refer to the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> {quote}
> h3. Backward Compatibility
> We support backward compatibility. All properties which have changed names
> can still be set with the old name. Wherever the value format was also
> changed from numeric value to number + unit value, you can still use the old
> name + the old numeric value format. For a full list of parameter
> changes/mapping of old to new parameters and what to expect, please refer to
> the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> The correct page to link is
> https://cassandra.apache.org/doc/latest/cassandra/configuration/configuration.html.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17816) WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
[
https://issues.apache.org/jira/browse/CASSANDRA-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17816:
--
Fix Version/s: NA
Source Control Link:
https://github.com/apache/cassandra-website/commit/65d5b952ffcb86d8d5e3f04425d678d9e5c42ee4
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed:
||Branch||PR||Commit||
|{{trunk}}|[#186|https://github.com/apache/cassandra-website/pull/186]|[65d5b95|https://github.com/apache/cassandra-website/commit/65d5b952ffcb86d8d5e3f04425d678d9e5c42ee4]|
> WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
> --
>
> Key: CASSANDRA-17816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17816
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
> Attachments: c17816-01-blog-post.png
>
>
> This ticket is to capture the work associated with fixing broken links on the
> blog [Apache Cassandra 4.1: Configuration
> Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
> {quote}
> For a full list of affected parameters, mapping of old to new names and
> supported units and how things work in general, please refer to the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> {quote}
> h3. Backward Compatibility
> We support backward compatibility. All properties which have changed names
> can still be set with the old name. Wherever the value format was also
> changed from numeric value to number + unit value, you can still use the old
> name + the old numeric value format. For a full list of parameter
> changes/mapping of old to new parameters and what to expect, please refer to
> the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> The correct page to link is
> https://cassandra.apache.org/doc/latest/cassandra/configuration/configuration.html.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch trunk updated: WEBSITE - Fixed broken links in 4.1 Configuration Standardization blog
This is an automated email from the ASF dual-hosted git repository. erickramirezau pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra-website.git The following commit(s) were added to refs/heads/trunk by this push: new 65d5b952 WEBSITE - Fixed broken links in 4.1 Configuration Standardization blog 65d5b952 is described below commit 65d5b952ffcb86d8d5e3f04425d678d9e5c42ee4 Author: Erick Ramirez AuthorDate: Tue Oct 25 13:14:36 2022 +1100 WEBSITE - Fixed broken links in 4.1 Configuration Standardization blog patch by Erick Ramirez; reviewed by Ekaterina Dimitrova for CASSANDRA-17816 --- .../blog/Apache-Cassandra-4.1-Configuration-Standardization.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-4.1-Configuration-Standardization.adoc b/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-4.1-Configuration-Standardization.adoc index c061527a..703b7bf1 100644 --- a/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-4.1-Configuration-Standardization.adoc +++ b/site-content/source/modules/ROOT/pages/blog/Apache-Cassandra-4.1-Configuration-Standardization.adoc @@ -35,7 +35,7 @@ permissions_update_interval: 0µs . Provide an easier and uniform way to add new parameters for Cassandra developers with the goal of reducing the chances of introducing bugs when adding new parameters. . The approach for backward compatibility can be reused for more parameters in different use cases in the future. -For a full list of affected parameters, mapping of old to new names and supported units and how things work in general, please refer to the link:doc/trunk/cassandra/new/configuration.html[documentation^]. +For a full list of affected parameters, mapping of old to new names and supported units and how things work in general, please refer to the link:/doc/4.1/cassandra/configuration/configuration.html[documentation^]. === Positive Side Effects @@ -45,7 +45,7 @@ Having standard naming conventions and common agreement on the units will make i === Backward Compatibility We support backward compatibility. All properties which have changed names can still be set with the old name. Wherever the value format was also changed from numeric value to number + unit value, you can still use the old name + the old numeric value format. -For a full list of parameter changes/mapping of old to new parameters and what to expect, please refer to the link:doc/trunk/cassandra/new/configuration.html[documentation^]. +For a full list of parameter changes/mapping of old to new parameters and what to expect, please refer to the link:/doc/4.1/cassandra/configuration/configuration.html[documentation^]. === Upgrade Advice - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17816) WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
[
https://issues.apache.org/jira/browse/CASSANDRA-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17816:
--
Reviewers: Ekaterina Dimitrova
Status: Review In Progress (was: Patch Available)
I've staged the change locally and verified that the links go to the right page.
!c17816-01-blog-post.png|width=300!
> WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
> --
>
> Key: CASSANDRA-17816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17816
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
> Labels: pull-request-available
> Attachments: c17816-01-blog-post.png
>
>
> This ticket is to capture the work associated with fixing broken links on the
> blog [Apache Cassandra 4.1: Configuration
> Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
> {quote}
> For a full list of affected parameters, mapping of old to new names and
> supported units and how things work in general, please refer to the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> {quote}
> h3. Backward Compatibility
> We support backward compatibility. All properties which have changed names
> can still be set with the old name. Wherever the value format was also
> changed from numeric value to number + unit value, you can still use the old
> name + the old numeric value format. For a full list of parameter
> changes/mapping of old to new parameters and what to expect, please refer to
> the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> The correct page to link is
> https://cassandra.apache.org/doc/latest/cassandra/configuration/configuration.html.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17816) WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
[
https://issues.apache.org/jira/browse/CASSANDRA-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17816:
--
Status: Ready to Commit (was: Review In Progress)
> WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
> --
>
> Key: CASSANDRA-17816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17816
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
> Labels: pull-request-available
> Attachments: c17816-01-blog-post.png
>
>
> This ticket is to capture the work associated with fixing broken links on the
> blog [Apache Cassandra 4.1: Configuration
> Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
> {quote}
> For a full list of affected parameters, mapping of old to new names and
> supported units and how things work in general, please refer to the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> {quote}
> h3. Backward Compatibility
> We support backward compatibility. All properties which have changed names
> can still be set with the old name. Wherever the value format was also
> changed from numeric value to number + unit value, you can still use the old
> name + the old numeric value format. For a full list of parameter
> changes/mapping of old to new parameters and what to expect, please refer to
> the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> The correct page to link is
> https://cassandra.apache.org/doc/latest/cassandra/configuration/configuration.html.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17816) WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
[
https://issues.apache.org/jira/browse/CASSANDRA-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17816:
--
Test and Documentation Plan: Stage locally and verify that the updated link
points to the right page (was: Fixing the "documentation" link)
Status: Patch Available (was: In Progress)
Patch:
||Branch||PR||
|{{trunk}}|[#186|https://github.com/apache/cassandra-website/pull/186]|
> WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
> --
>
> Key: CASSANDRA-17816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17816
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
> Labels: pull-request-available
> Attachments: c17816-01-blog-post.png
>
>
> This ticket is to capture the work associated with fixing broken links on the
> blog [Apache Cassandra 4.1: Configuration
> Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
> {quote}
> For a full list of affected parameters, mapping of old to new names and
> supported units and how things work in general, please refer to the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> {quote}
> h3. Backward Compatibility
> We support backward compatibility. All properties which have changed names
> can still be set with the old name. Wherever the value format was also
> changed from numeric value to number + unit value, you can still use the old
> name + the old numeric value format. For a full list of parameter
> changes/mapping of old to new parameters and what to expect, please refer to
> the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> The correct page to link is
> https://cassandra.apache.org/doc/latest/cassandra/configuration/configuration.html.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17816) WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
[
https://issues.apache.org/jira/browse/CASSANDRA-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17816:
--
Description:
This ticket is to capture the work associated with fixing broken links on the
blog [Apache Cassandra 4.1: Configuration
Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
{quote}
For a full list of affected parameters, mapping of old to new names and
supported units and how things work in general, please refer to the
[documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
{quote}
{quote}
h3. Backward Compatibility
We support backward compatibility. All properties which have changed names can
still be set with the old name. Wherever the value format was also changed from
numeric value to number + unit value, you can still use the old name + the old
numeric value format. For a full list of parameter changes/mapping of old to
new parameters and what to expect, please refer to the
[documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
{quote}
The correct page to link is
https://cassandra.apache.org/doc/latest/cassandra/configuration/configuration.html.
was:
This ticket is to capture the work associated with fixing broken links on the
blog [Apache Cassandra 4.1: Configuration
Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
{quote}
For a full list of affected parameters, mapping of old to new names and
supported units and how things work in general, please refer to the
[documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
{quote}
{quote}
h3. Backward Compatibility
We support backward compatibility. All properties which have changed names can
still be set with the old name. Wherever the value format was also changed from
numeric value to number + unit value, you can still use the old name + the old
numeric value format. For a full list of parameter changes/mapping of old to
new parameters and what to expect, please refer to the
[documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
{quote}
> WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
> --
>
> Key: CASSANDRA-17816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17816
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
> Labels: pull-request-available
> Attachments: c17816-01-blog-post.png
>
>
> This ticket is to capture the work associated with fixing broken links on the
> blog [Apache Cassandra 4.1: Configuration
> Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
> {quote}
> For a full list of affected parameters, mapping of old to new names and
> supported units and how things work in general, please refer to the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> {quote}
> h3. Backward Compatibility
> We support backward compatibility. All properties which have changed names
> can still be set with the old name. Wherever the value format was also
> changed from numeric value to number + unit value, you can still use the old
> name + the old numeric value format. For a full list of parameter
> changes/mapping of old to new parameters and what to expect, please refer to
> the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> The correct page to link is
> https://cassandra.apache.org/doc/latest/cassandra/configuration/configuration.html.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17816) WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
[
https://issues.apache.org/jira/browse/CASSANDRA-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17816:
--
Attachment: c17816-01-blog-post.png
> WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
> --
>
> Key: CASSANDRA-17816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17816
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
> Labels: pull-request-available
> Attachments: c17816-01-blog-post.png
>
>
> This ticket is to capture the work associated with fixing broken links on the
> blog [Apache Cassandra 4.1: Configuration
> Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
> {quote}
> For a full list of affected parameters, mapping of old to new names and
> supported units and how things work in general, please refer to the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> {quote}
> h3. Backward Compatibility
> We support backward compatibility. All properties which have changed names
> can still be set with the old name. Wherever the value format was also
> changed from numeric value to number + unit value, you can still use the old
> name + the old numeric value format. For a full list of parameter
> changes/mapping of old to new parameters and what to expect, please refer to
> the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17816) WEBSITE - Broken doc link in blog "4.1 Configuration Standardization"
[
https://issues.apache.org/jira/browse/CASSANDRA-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17816:
--
Description:
This ticket is to capture the work associated with fixing broken links on the
blog [Apache Cassandra 4.1: Configuration
Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
{quote}
For a full list of affected parameters, mapping of old to new names and
supported units and how things work in general, please refer to the
[documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
{quote}
{quote}
h3. Backward Compatibility
We support backward compatibility. All properties which have changed names can
still be set with the old name. Wherever the value format was also changed from
numeric value to number + unit value, you can still use the old name + the old
numeric value format. For a full list of parameter changes/mapping of old to
new parameters and what to expect, please refer to the
[documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
{quote}
was:This ticket is to capture the work associated with fixing an broken link
on the blog "Apache Cassandra 4.1: Configuration Standardization"
> WEBSITE - Broken doc link in blog "4.1 Configuration Standardization"
> -
>
> Key: CASSANDRA-17816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17816
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
> Labels: pull-request-available
>
> This ticket is to capture the work associated with fixing broken links on the
> blog [Apache Cassandra 4.1: Configuration
> Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
> {quote}
> For a full list of affected parameters, mapping of old to new names and
> supported units and how things work in general, please refer to the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> {quote}
> h3. Backward Compatibility
> We support backward compatibility. All properties which have changed names
> can still be set with the old name. Wherever the value format was also
> changed from numeric value to number + unit value, you can still use the old
> name + the old numeric value format. For a full list of parameter
> changes/mapping of old to new parameters and what to expect, please refer to
> the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17816) WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
[
https://issues.apache.org/jira/browse/CASSANDRA-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Ramirez updated CASSANDRA-17816:
--
Summary: WEBSITE - Broken doc links in blog "4.1 Configuration
Standardization" (was: WEBSITE - Broken doc link in blog "4.1 Configuration
Standardization")
> WEBSITE - Broken doc links in blog "4.1 Configuration Standardization"
> --
>
> Key: CASSANDRA-17816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17816
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Blog
>Reporter: Diogenese Topper
>Assignee: Erick Ramirez
>Priority: Normal
> Labels: pull-request-available
>
> This ticket is to capture the work associated with fixing broken links on the
> blog [Apache Cassandra 4.1: Configuration
> Standardization|https://cassandra.apache.org/_/blog/Apache-Cassandra-4.1-Configuration-Standardization.html]:
> {quote}
> For a full list of affected parameters, mapping of old to new names and
> supported units and how things work in general, please refer to the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
> {quote}
> h3. Backward Compatibility
> We support backward compatibility. All properties which have changed names
> can still be set with the old name. Wherever the value format was also
> changed from numeric value to number + unit value, you can still use the old
> name + the old numeric value format. For a full list of parameter
> changes/mapping of old to new parameters and what to expect, please refer to
> the
> [documentation|https://cassandra.apache.org/_/blog/doc/trunk/cassandra/new/configuration.html].
> {quote}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17816) WEBSITE - Broken doc link in blog "4.1 Configuration Standardization"
[ https://issues.apache.org/jira/browse/CASSANDRA-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17816: -- Status: In Progress (was: Patch Available) > WEBSITE - Broken doc link in blog "4.1 Configuration Standardization" > - > > Key: CASSANDRA-17816 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17816 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > > This ticket is to capture the work associated with fixing an broken link on > the blog "Apache Cassandra 4.1: Configuration Standardization" -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-17816) WEBSITE - Broken doc link in blog "4.1 Configuration Standardization"
[ https://issues.apache.org/jira/browse/CASSANDRA-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez reassigned CASSANDRA-17816: - Assignee: Erick Ramirez > WEBSITE - Broken doc link in blog "4.1 Configuration Standardization" > - > > Key: CASSANDRA-17816 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17816 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Assignee: Erick Ramirez >Priority: Normal > Labels: pull-request-available > > This ticket is to capture the work associated with fixing an broken link on > the blog "Apache Cassandra 4.1: Configuration Standardization" -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17816) WEBSITE - Broken doc link in blog "4.1 Configuration Standardization"
[ https://issues.apache.org/jira/browse/CASSANDRA-17816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17816: -- Summary: WEBSITE - Broken doc link in blog "4.1 Configuration Standardization" (was: WEBSITE - link fix for "Apache Cassandra 4.1: Configuration Standardization") > WEBSITE - Broken doc link in blog "4.1 Configuration Standardization" > - > > Key: CASSANDRA-17816 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17816 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > > This ticket is to capture the work associated with fixing an broken link on > the blog "Apache Cassandra 4.1: Configuration Standardization" -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17987) CircleCI: Add jobs for running specialized unit tests with Java 11
[
https://issues.apache.org/jira/browse/CASSANDRA-17987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623480#comment-17623480
]
Ekaterina Dimitrova edited comment on CASSANDRA-17987 at 10/25/22 1:23 AM:
---
I agree with everything you said. Let's not do it mandatory. Now we have an
initiative and short-term focus and I also expect CASSANDRA-17987 to be worked
on sooner than later. The keyspaces one were not a priority and their Jenkins
ticket was opened more than 1 year ago. They got broken 2 times and we did them
mandatory until someone find circles to finally add them in Jenkins so they do
not regress anymore.
{quote}I'm also adding the missing CDC unit tests, since doing it here doesn't
require too much extra effort:
{quote}
Thanks for doing it! I just checked we run cdc also with 3.11. I guess we will
have to add them there too.
I think you missed the keyspaces ones in the JDK11 pre-commit workflow. I
didn't find anything else suspicious in the UI :)
I noticed the trunk PR, you wanted to start from it as previous branches will
be actually less jobs I guess. I can take a look into the code tomorrow
was (Author: e.dimitrova):
I agree with everything you said. Let's not do it mandatory. Now we have an
initiative and short-term focus and I also expect CASSANDRA-17987 to be worked
on sooner than later. The keyspaces one were not a priority and their Jenkins
ticket was opened more than 1 year ago. They got broken 2 times and we did them
mandatory until someone find circles to finally add them in Jenkins so they do
not regress anymore.
{quote}I'm also adding the missing CDC unit tests, since doing it here doesn't
require too much extra effort:
{quote}
Thanks for doing it! I just checked we run cdc also with 3.11. I guess we will
have to add them there too.
I think you missed the keyspaces ones in the JDK11 pre-commit workflow. I
didn't find anything else suspicious in the UI :)
> CircleCI: Add jobs for running specialized unit tests with Java 11
> --
>
> Key: CASSANDRA-17987
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17987
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
>
> CircleCI has a set of jobs for running specialiazed unit tests that are only
> run with Java 8:
> * utests_compression
> * utests_system_keyspace_directory
> * utests_trie
> * utests_stress
> * utests_long
> * utests_fqltool
> It should probably be possible to run these tests with Java 11 tool.
> Rather than creating a ticket for every job, it's probably easier to use a
> single ticket for all of them. This should give us an overall vision for
> deciding job names, approval steps, etc. Also, the required config changes
> should be quite minimal and doing all of them at once should save us both
> effort and test runs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17987) CircleCI: Add jobs for running specialized unit tests with Java 11
[
https://issues.apache.org/jira/browse/CASSANDRA-17987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623480#comment-17623480
]
Ekaterina Dimitrova commented on CASSANDRA-17987:
-
I agree with everything you said. Let's not do it mandatory. Now we have an
initiative and short-term focus and I also expect CASSANDRA-17987 to be worked
on sooner than later. The keyspaces one were not a priority and their Jenkins
ticket was opened more than 1 year ago. They got broken 2 times and we did them
mandatory until someone find circles to finally add them in Jenkins so they do
not regress anymore.
{quote}I'm also adding the missing CDC unit tests, since doing it here doesn't
require too much extra effort:
{quote}
Thanks for doing it! I just checked we run cdc also with 3.11. I guess we will
have to add them there too.
I think you missed the keyspaces ones in the JDK11 pre-commit workflow. I
didn't find anything else suspicious in the UI :)
> CircleCI: Add jobs for running specialized unit tests with Java 11
> --
>
> Key: CASSANDRA-17987
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17987
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
>
> CircleCI has a set of jobs for running specialiazed unit tests that are only
> run with Java 8:
> * utests_compression
> * utests_system_keyspace_directory
> * utests_trie
> * utests_stress
> * utests_long
> * utests_fqltool
> It should probably be possible to run these tests with Java 11 tool.
> Rather than creating a ticket for every job, it's probably easier to use a
> single ticket for all of them. This should give us an overall vision for
> deciding job names, approval steps, etc. Also, the required config changes
> should be quite minimal and doing all of them at once should save us both
> effort and test runs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-dtest] branch trunk updated: Rework check_output text usage for python < 3.7
This is an automated email from the ASF dual-hosted git repository.
brandonwilliams pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-dtest.git
The following commit(s) were added to refs/heads/trunk by this push:
new 010f7ce6 Rework check_output text usage for python < 3.7
010f7ce6 is described below
commit 010f7ce609d7dfad280e81c155b99c2b3b8da212
Author: Brandon Williams
AuthorDate: Mon Oct 24 18:18:31 2022 -0500
Rework check_output text usage for python < 3.7
---
tools/jmxutils.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/jmxutils.py b/tools/jmxutils.py
index 8d82815f..b08f3591 100644
--- a/tools/jmxutils.py
+++ b/tools/jmxutils.py
@@ -216,11 +216,11 @@ class JolokiaAgent(object):
tries = 3
for i in range(tries):
try:
-subprocess.check_output(args, stderr=subprocess.STDOUT,
text=True)
+subprocess.check_output(args, stderr=subprocess.STDOUT)
logger.info("Jolokia successful on try %s" % i )
return
except subprocess.CalledProcessError as exc:
-if 'Jolokia is already attached' in exc.output:
+if 'Jolokia is already attached'.encode('utf-8') in exc.output:
logger.info("Jolokia reports being attached on try %s,
returning successfully" % i)
return;
if i < tries - 1:
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16606) Update libthrift jar to at least 0.9.3-1, investigate 0.14.0
[ https://issues.apache.org/jira/browse/CASSANDRA-16606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623445#comment-17623445 ] Ivo Dujmovic commented on CASSANDRA-16606: -- [~mck] [~stefan.miklosovic] reviewing cassadra 3.11.13, libthrift was left at 0.9.2 version instead of upgraded to 0.14 . Can you share why / your mitigation statement? Thanks > Update libthrift jar to at least 0.9.3-1, investigate 0.14.0 > > > Key: CASSANDRA-16606 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16606 > Project: Cassandra > Issue Type: Bug > Components: Messaging/Thrift >Reporter: Mark Denihan >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 3.0.26, 3.11.12 > > > Cassandra 3.x and 2.x uses libthrift 0.9.2, which has a number of > vulnerabilities associated with it which are applicable to Cassandra; > CVE-2015-3254 > CVE-2018-1320 (CASSANDRA-15424) > CVE-2019-0205 (CASSANDRA-15420) > Updating to 0.9.3-1 will mitigate these, however that branch suffers > CVE-2020-13949. > To mitigate risks from using out of date libthrift versions, Cassandra should > be updated to use 0.14.0 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17103) CEP-15 (C*): Messaging and storage engine integration
[ https://issues.apache.org/jira/browse/CASSANDRA-17103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623440#comment-17623440 ] David Capwell commented on CASSANDRA-17103: --- Some follow feedback accord-core: https://github.com/apache/cassandra-accord/pull/11 cassandra: https://github.com/apache/cassandra/pull/1948 CI: https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=feedback%2FCASSANDRA-17103 > CEP-15 (C*): Messaging and storage engine integration > - > > Key: CASSANDRA-17103 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17103 > Project: Cassandra > Issue Type: New Feature > Components: Accord >Reporter: Benedict Elliott Smith >Assignee: Blake Eggleston >Priority: Normal > Fix For: NA > > > This work encompasses implementing Accord’s storage and networking interfaces > within Cassandra, so that messages may be sent around the cluster and executed -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17918) DESCRIBE output does not quote column names using reserved keywords
[
https://issues.apache.org/jira/browse/CASSANDRA-17918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623438#comment-17623438
]
Bernardo Botella Corbi commented on CASSANDRA-17918:
[~yifanc] I just updated the trunk PR with a new unit test covering (hopefully)
the missing cases.
> DESCRIBE output does not quote column names using reserved keywords
> ---
>
> Key: CASSANDRA-17918
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17918
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/CQL
>Reporter: Yifan Cai
>Assignee: Bernardo Botella Corbi
>Priority: Normal
> Fix For: 4.0.x, 4.1.x
>
>
> The DESCRIBE output of the column names that using reserved keywords are not
> quoted for UDTs. The following test reproduces. Reading the code, it looks
> like that the such columns names are not quoted in materialized view, UDF and
> user defined aggregation.
> The impact of the bug is that schema described cannot be imported due to the
> usage of reserved keywords as column names.
>
> {code:java}
> @Test
> public void testUsingReservedInCreateType() throws Throwable
> {
> String type = createType(KEYSPACE_PER_TEST, "CREATE TYPE %s
> (\"token\" text, \"desc\" text);");
> assertRowsNet(executeDescribeNet(KEYSPACE_PER_TEST, "DESCRIBE TYPE " + type),
> row(KEYSPACE_PER_TEST, "type", type, "CREATE TYPE " +
> KEYSPACE_PER_TEST + "." + type + " (\n" +
> " \"token\" text,\n" +
> " \"desc\" text\n" +
> ");"));
> } {code}
> +Additional information for newcomers:+
> * Unit tests for DESCRIBE statements are in {{DescribeStatementTest}}
> * The statement implementation is in {{DescribeStatement and fetch the
> create statement from the different schema element using
> SchemaElement.toCqlString}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
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&focusedCommentId=17623385#comment-17623385
]
Doug Whitfield commented on CASSANDRA-14355:
It has been over two years since there has been any comment on this. Is it safe
to assume this was fixed in 3.11.5?
> Memory leak
> ---
>
> Key: CASSANDRA-14355
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14355
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Core
> Environment: Debian Jessie, OpenJDK 1.8.0_151
>Reporter: Eric Evans
>Priority: Normal
> Fix For: 3.11.x
>
> 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, LongGC_Dominator-Tree.png, LongGC_Histogram.png,
> LongGC_Problem-Suspect-1_FastThreadLocalThread.png, LongGC_nodetool_info.txt
>
>
> 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
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17987) CircleCI: Add jobs for running specialized unit tests with Java 11
[ https://issues.apache.org/jira/browse/CASSANDRA-17987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andres de la Peña updated CASSANDRA-17987: -- Test and Documentation Plan: https://github.com/apache/cassandra/pull/1947 Status: Patch Available (was: In Progress) > CircleCI: Add jobs for running specialized unit tests with Java 11 > -- > > Key: CASSANDRA-17987 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17987 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Andres de la Peña >Assignee: Andres de la Peña >Priority: Normal > > CircleCI has a set of jobs for running specialiazed unit tests that are only > run with Java 8: > * utests_compression > * utests_system_keyspace_directory > * utests_trie > * utests_stress > * utests_long > * utests_fqltool > It should probably be possible to run these tests with Java 11 tool. > Rather than creating a ticket for every job, it's probably easier to use a > single ticket for all of them. This should give us an overall vision for > deciding job names, approval steps, etc. Also, the required config changes > should be quite minimal and doing all of them at once should save us both > effort and test runs. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17987) CircleCI: Add jobs for running specialized unit tests with Java 11
[
https://issues.apache.org/jira/browse/CASSANDRA-17987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623331#comment-17623331
]
Andres de la Peña edited comment on CASSANDRA-17987 at 10/24/22 6:23 PM:
-
I'm also adding the missing CDC unit tests, since doing it here doesn't require
too much extra effort:
* [j8
pre-commit|https://app.circleci.com/pipelines/github/adelapena/cassandra/2318/workflows/7840c4a4-c280-45f8-871d-d3aa71a96372]
* [j11
pre-commit|https://app.circleci.com/pipelines/github/adelapena/cassandra/2318/workflows/df241342-aca4-4250-997f-d78aaee8d5cd]
* [j8
separate|https://app.circleci.com/pipelines/github/adelapena/cassandra/2318/workflows/78650a8e-4c7e-4278-93d2-744547b750f0]
* [j11
separate|https://app.circleci.com/pipelines/github/adelapena/cassandra/2318/workflows/125a1087-8e20-4e25-803b-daff5136e98f]
{quote}Shall we make the trie unit tests mandatory at least for jdk8 until they
are added also in Jenkins? Same as we did for keyspaces? Or do you want to do
it in a separate ticket or run it through the ML?
{quote}
Not sure:
# If we make them mandatory here. If CASSANDRA-17987 gets merged after this,
we'll need another ticket to make them not mandatory again. That's not ideal
given the time and money required to test this kind of patches.
# We could block this ticket until CASSANDRA-17987 gets merged, but that will
leave us without a way of running trie tests with Java 11 in the mean time.
# We could commit this in what is expected to be its final state and hope that
CASSANDRA-17987 gets merged soon, which seems likely.
In any case, note that the utests-trie job is mostly a just-in-case config, and
tries have their own tests that are run with the regular config.
was (Author: adelapena):
I'm also add the missing CDC unit tests, since doing it here doesn't require
too much extra effort:
* [j8
pre-commit|https://app.circleci.com/pipelines/github/adelapena/cassandra/2318/workflows/7840c4a4-c280-45f8-871d-d3aa71a96372]
* [j11
pre-commit|https://app.circleci.com/pipelines/github/adelapena/cassandra/2318/workflows/df241342-aca4-4250-997f-d78aaee8d5cd]
* [j8
separate|https://app.circleci.com/pipelines/github/adelapena/cassandra/2318/workflows/78650a8e-4c7e-4278-93d2-744547b750f0]
* [j11
separate|https://app.circleci.com/pipelines/github/adelapena/cassandra/2318/workflows/125a1087-8e20-4e25-803b-daff5136e98f]
{quote}Shall we make the trie unit tests mandatory at least for jdk8 until they
are added also in Jenkins? Same as we did for keyspaces? Or do you want to do
it in a separate ticket or run it through the ML?
{quote}
Not sure:
# If we make them mandatory here. If CASSANDRA-17987 gets merged after this,
we'll need another ticket to make them not mandatory again. That's not ideal
given the time and money required to test this kind of patches.
# We could block this ticket until CASSANDRA-17987 gets merged, but that will
leave us without a way of running trie tests with Java 11 in the mean time.
# We could commit this in what is expected to be its final state and hope that
CASSANDRA-17987 gets merged soon, which seems likely.
In any case, note that the utests-trie job is mostly a just-in-case config, and
tries have their own tests that are run with the regular config.
> CircleCI: Add jobs for running specialized unit tests with Java 11
> --
>
> Key: CASSANDRA-17987
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17987
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
>
> CircleCI has a set of jobs for running specialiazed unit tests that are only
> run with Java 8:
> * utests_compression
> * utests_system_keyspace_directory
> * utests_trie
> * utests_stress
> * utests_long
> * utests_fqltool
> It should probably be possible to run these tests with Java 11 tool.
> Rather than creating a ticket for every job, it's probably easier to use a
> single ticket for all of them. This should give us an overall vision for
> deciding job names, approval steps, etc. Also, the required config changes
> should be quite minimal and doing all of them at once should save us both
> effort and test runs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17987) CircleCI: Add jobs for running specialized unit tests with Java 11
[
https://issues.apache.org/jira/browse/CASSANDRA-17987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623331#comment-17623331
]
Andres de la Peña commented on CASSANDRA-17987:
---
I'm also add the missing CDC unit tests, since doing it here doesn't require
too much extra effort:
* [j8
pre-commit|https://app.circleci.com/pipelines/github/adelapena/cassandra/2318/workflows/7840c4a4-c280-45f8-871d-d3aa71a96372]
* [j11
pre-commit|https://app.circleci.com/pipelines/github/adelapena/cassandra/2318/workflows/df241342-aca4-4250-997f-d78aaee8d5cd]
* [j8
separate|https://app.circleci.com/pipelines/github/adelapena/cassandra/2318/workflows/78650a8e-4c7e-4278-93d2-744547b750f0]
* [j11
separate|https://app.circleci.com/pipelines/github/adelapena/cassandra/2318/workflows/125a1087-8e20-4e25-803b-daff5136e98f]
{quote}Shall we make the trie unit tests mandatory at least for jdk8 until they
are added also in Jenkins? Same as we did for keyspaces? Or do you want to do
it in a separate ticket or run it through the ML?
{quote}
Not sure:
# If we make them mandatory here. If CASSANDRA-17987 gets merged after this,
we'll need another ticket to make them not mandatory again. That's not ideal
given the time and money required to test this kind of patches.
# We could block this ticket until CASSANDRA-17987 gets merged, but that will
leave us without a way of running trie tests with Java 11 in the mean time.
# We could commit this in what is expected to be its final state and hope that
CASSANDRA-17987 gets merged soon, which seems likely.
In any case, note that the utests-trie job is mostly a just-in-case config, and
tries have their own tests that are run with the regular config.
> CircleCI: Add jobs for running specialized unit tests with Java 11
> --
>
> Key: CASSANDRA-17987
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17987
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
>
> CircleCI has a set of jobs for running specialiazed unit tests that are only
> run with Java 8:
> * utests_compression
> * utests_system_keyspace_directory
> * utests_trie
> * utests_stress
> * utests_long
> * utests_fqltool
> It should probably be possible to run these tests with Java 11 tool.
> Rather than creating a ticket for every job, it's probably easier to use a
> single ticket for all of them. This should give us an overall vision for
> deciding job names, approval steps, etc. Also, the required config changes
> should be quite minimal and doing all of them at once should save us both
> effort and test runs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17783) Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}} to {{CassandraRelevantProps}}
[
https://issues.apache.org/jira/browse/CASSANDRA-17783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623313#comment-17623313
]
Doug Rohrer commented on CASSANDRA-17783:
-
Just wanted to see if we can make some progress on this - would love to get
this merged soon if possible.
> Move {{Schema.FORCE_LOAD_KEYSPACES}} and {{Schema.FORCE_LOAD_KEYSPACES_PROP}}
> to {{CassandraRelevantProps}}
> ---
>
> Key: CASSANDRA-17783
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17783
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Startup and Shutdown
>Reporter: Doug Rohrer
>Assignee: Doug Rohrer
>Priority: Low
> Fix For: 4.x
>
> Attachments: CASSANDRA-17783-rebased.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{Schema.FORCE_LOAD_LOCAL_KEYSPACES_PROP}} and
> {{Schema.FORCE_LOAD_LOCAL_KEYSPACES}} should be moved to
> {{CassandraRelevantProps}} for two reasons.
> # Generally speaking, this is where these kinds of things live.
> # By having them in Schema, you can't actually use
> {{Schema.FORCE_LOAD_LOCAL_KEYSPACES_PROP}} without running all of the static
> initializers... and you want to use
> {{Schema.FORCE_LOAD_LOCAL_KEYSPACES_PROP}} to set the system property before
> the static initializer runs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17987) CircleCI: Add jobs for running specialized unit tests with Java 11
[ https://issues.apache.org/jira/browse/CASSANDRA-17987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623247#comment-17623247 ] Ekaterina Dimitrova commented on CASSANDRA-17987: - The UI seems to cover everything. Shall we make the trie unit tests mandatory at least for jdk8 until they are added also in Jenkins? Same as we did for keyspaces? Or do you want to do it in a separate ticket or run it through the ML? > CircleCI: Add jobs for running specialized unit tests with Java 11 > -- > > Key: CASSANDRA-17987 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17987 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Andres de la Peña >Assignee: Andres de la Peña >Priority: Normal > > CircleCI has a set of jobs for running specialiazed unit tests that are only > run with Java 8: > * utests_compression > * utests_system_keyspace_directory > * utests_trie > * utests_stress > * utests_long > * utests_fqltool > It should probably be possible to run these tests with Java 11 tool. > Rather than creating a ticket for every job, it's probably easier to use a > single ticket for all of them. This should give us an overall vision for > deciding job names, approval steps, etc. Also, the required config changes > should be quite minimal and doing all of them at once should save us both > effort and test runs. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17987) CircleCI: Add jobs for running specialized unit tests with Java 11
[ https://issues.apache.org/jira/browse/CASSANDRA-17987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623223#comment-17623223 ] Andres de la Peña commented on CASSANDRA-17987: --- Here is a preview of how the workflows would look like for trunk: * [j8 pre-commit|https://app.circleci.com/pipelines/github/adelapena/cassandra/2317/workflows/9bf66354-2b32-4589-9c3d-1aaa07cc51c5] * [j11 pre-commit|https://app.circleci.com/pipelines/github/adelapena/cassandra/2317/workflows/db51cab2-4912-4f71-8993-05aa41e2dfed] * [j8 separate|https://app.circleci.com/pipelines/github/adelapena/cassandra/2317/workflows/03855178-9e76-4aaa-a384-6d44b3f3d84a] * [j11 separate|https://app.circleci.com/pipelines/github/adelapena/cassandra/2317/workflows/f5e079a2-2eae-4f5b-b52b-f9fda87d2cf2] I still have do some fixes, prepare the patches for 4.0 and 4.1 and properly test it. > CircleCI: Add jobs for running specialized unit tests with Java 11 > -- > > Key: CASSANDRA-17987 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17987 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Andres de la Peña >Assignee: Andres de la Peña >Priority: Normal > > CircleCI has a set of jobs for running specialiazed unit tests that are only > run with Java 8: > * utests_compression > * utests_system_keyspace_directory > * utests_trie > * utests_stress > * utests_long > * utests_fqltool > It should probably be possible to run these tests with Java 11 tool. > Rather than creating a ticket for every job, it's probably easier to use a > single ticket for all of them. This should give us an overall vision for > deciding job names, approval steps, etc. Also, the required config changes > should be quite minimal and doing all of them at once should save us both > effort and test runs. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17671) Run utests_system_keyspace_directory with Java 11 in CircleCI
[ https://issues.apache.org/jira/browse/CASSANDRA-17671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17671: Resolution: Duplicate Status: Resolved (was: Open) > Run utests_system_keyspace_directory with Java 11 in CircleCI > - > > Key: CASSANDRA-17671 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17671 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Normal > > Currently we run those tests only with Java 8, I have to dig into it further > but it seems that there is no specific reason not to run those with Java 11 > too. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17671) Run utests_system_keyspace_directory with Java 11 in CircleCI
[ https://issues.apache.org/jira/browse/CASSANDRA-17671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623193#comment-17623193 ] Ekaterina Dimitrova commented on CASSANDRA-17671: - Great, I am closing it in favor of the other one. > Run utests_system_keyspace_directory with Java 11 in CircleCI > - > > Key: CASSANDRA-17671 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17671 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Normal > > Currently we run those tests only with Java 8, I have to dig into it further > but it seems that there is no specific reason not to run those with Java 11 > too. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17240) CEP-19: Trie memtable implementation
[ https://issues.apache.org/jira/browse/CASSANDRA-17240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623191#comment-17623191 ] Ekaterina Dimitrova commented on CASSANDRA-17240: - Thanks! > CEP-19: Trie memtable implementation > > > Key: CASSANDRA-17240 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17240 > Project: Cassandra > Issue Type: Improvement > Components: Local/Memtable >Reporter: Branimir Lambov >Assignee: Branimir Lambov >Priority: Normal > Fix For: 4.2 > > Attachments: SkipListMemtable-OSS.png, TrieMemtable-OSS.png, > density_SG.html.gz, density_test_with_sharding.html.gz, latency-1_1-95.png, > latency-9_1-95.png, throughput_SG.png, throughput_apache.png > > Time Spent: 13.5h > Remaining Estimate: 0h > > Trie-based memtable implementation as described in CEP-19, built on top of > CASSANDRA-17034 and CASSANDRA-6936. > The implementation is available in this > [branch|https://github.com/blambov/cassandra/tree/CASSANDRA-17240]. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17989) Jenkins: Add unit tests for trie-based memtables
[ https://issues.apache.org/jira/browse/CASSANDRA-17989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17989: Complexity: Normal (was: Low Hanging Fruit) > Jenkins: Add unit tests for trie-based memtables > > > Key: CASSANDRA-17989 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17989 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Andres de la Peña >Priority: Normal > Fix For: 4.x > > > CASSANDRA-17240 has recently added a CircleCI job for running unit tests with > trie-based memtables. These tests should also be added to Jenkins. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17987) CircleCI: Add jobs for running specialized unit tests with Java 11
[ https://issues.apache.org/jira/browse/CASSANDRA-17987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17987: Change Category: Quality Assurance Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > CircleCI: Add jobs for running specialized unit tests with Java 11 > -- > > Key: CASSANDRA-17987 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17987 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Andres de la Peña >Assignee: Andres de la Peña >Priority: Normal > > CircleCI has a set of jobs for running specialiazed unit tests that are only > run with Java 8: > * utests_compression > * utests_system_keyspace_directory > * utests_trie > * utests_stress > * utests_long > * utests_fqltool > It should probably be possible to run these tests with Java 11 tool. > Rather than creating a ticket for every job, it's probably easier to use a > single ticket for all of them. This should give us an overall vision for > deciding job names, approval steps, etc. Also, the required config changes > should be quite minimal and doing all of them at once should save us both > effort and test runs. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17987) CircleCI: Add jobs for running specialized unit tests with Java 11
[ https://issues.apache.org/jira/browse/CASSANDRA-17987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17987: Complexity: Normal (was: Low Hanging Fruit) > CircleCI: Add jobs for running specialized unit tests with Java 11 > -- > > Key: CASSANDRA-17987 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17987 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Andres de la Peña >Assignee: Andres de la Peña >Priority: Normal > > CircleCI has a set of jobs for running specialiazed unit tests that are only > run with Java 8: > * utests_compression > * utests_system_keyspace_directory > * utests_trie > * utests_stress > * utests_long > * utests_fqltool > It should probably be possible to run these tests with Java 11 tool. > Rather than creating a ticket for every job, it's probably easier to use a > single ticket for all of them. This should give us an overall vision for > deciding job names, approval steps, etc. Also, the required config changes > should be quite minimal and doing all of them at once should save us both > effort and test runs. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17989) Jenkins: Add unit tests for trie-based memtables
[ https://issues.apache.org/jira/browse/CASSANDRA-17989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17989: Fix Version/s: 4.x > Jenkins: Add unit tests for trie-based memtables > > > Key: CASSANDRA-17989 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17989 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Andres de la Peña >Priority: Normal > Fix For: 4.x > > > CASSANDRA-17240 has recently added a CircleCI job for running unit tests with > trie-based memtables. These tests should also be added to Jenkins. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17989) Jenkins: Add unit tests for trie-based memtables
[ https://issues.apache.org/jira/browse/CASSANDRA-17989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-17989: Change Category: Quality Assurance Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > Jenkins: Add unit tests for trie-based memtables > > > Key: CASSANDRA-17989 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17989 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Andres de la Peña >Priority: Normal > > CASSANDRA-17240 has recently added a CircleCI job for running unit tests with > trie-based memtables. These tests should also be added to Jenkins. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17922) Jolokia agent fails to connect though port is available
[
https://issues.apache.org/jira/browse/CASSANDRA-17922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17922:
-
Reviewers: Josh McKenzie (was: Brandon Williams, Josh McKenzie)
> Jolokia agent fails to connect though port is available
> ---
>
> Key: CASSANDRA-17922
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17922
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.0.8, 4.1-beta2, 4.2
>
>
> In CASSANDRA-17872 we added protection around failures similar to this,
> caused by the port being in use, which is no longer the case:
> {code}
> subprocess.CalledProcessError: Command
> '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '{-}cp',
> '/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
> 'org.jolokia.jvmagent.client.AgentLauncher', '{-}{-}host', '127.0.0.2',
> '{-}-port', '8778', 'start', '1123')' returned non-zero exit status 1.
> {code}
> [https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/junit/dtest-novnode.auth_test/TestNetworkAuth/test_revoked_dc_access/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17922) Jolokia agent fails to connect though port is available
[
https://issues.apache.org/jira/browse/CASSANDRA-17922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17922:
-
Fix Version/s: 4.0.8
4.1-beta2
4.2
(was: 4.x)
(was: 4.1.x)
Since Version: NA
Source Control Link:
https://github.com/apache/cassandra-dtest/commit/860d005f63f7a31dcdae234a24af605e279b6e75
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed.
> Jolokia agent fails to connect though port is available
> ---
>
> Key: CASSANDRA-17922
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17922
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.0.8, 4.1-beta2, 4.2
>
>
> In CASSANDRA-17872 we added protection around failures similar to this,
> caused by the port being in use, which is no longer the case:
> {code}
> subprocess.CalledProcessError: Command
> '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '{-}cp',
> '/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
> 'org.jolokia.jvmagent.client.AgentLauncher', '{-}{-}host', '127.0.0.2',
> '{-}-port', '8778', 'start', '1123')' returned non-zero exit status 1.
> {code}
> [https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/junit/dtest-novnode.auth_test/TestNetworkAuth/test_revoked_dc_access/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17922) Jolokia agent fails to connect though port is available
[
https://issues.apache.org/jira/browse/CASSANDRA-17922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17922:
-
Reviewers: Josh McKenzie, Brandon Williams (was: Josh McKenzie)
Josh McKenzie, Brandon Williams (was: Brandon Williams, Josh
McKenzie)
Status: Review In Progress (was: Patch Available)
> Jolokia agent fails to connect though port is available
> ---
>
> Key: CASSANDRA-17922
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17922
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.1.x, 4.x
>
>
> In CASSANDRA-17872 we added protection around failures similar to this,
> caused by the port being in use, which is no longer the case:
> {code}
> subprocess.CalledProcessError: Command
> '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '{-}cp',
> '/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
> 'org.jolokia.jvmagent.client.AgentLauncher', '{-}{-}host', '127.0.0.2',
> '{-}-port', '8778', 'start', '1123')' returned non-zero exit status 1.
> {code}
> [https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/junit/dtest-novnode.auth_test/TestNetworkAuth/test_revoked_dc_access/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17922) Jolokia agent fails to connect though port is available
[
https://issues.apache.org/jira/browse/CASSANDRA-17922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17922:
-
Status: Ready to Commit (was: Review In Progress)
> Jolokia agent fails to connect though port is available
> ---
>
> Key: CASSANDRA-17922
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17922
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.1.x, 4.x
>
>
> In CASSANDRA-17872 we added protection around failures similar to this,
> caused by the port being in use, which is no longer the case:
> {code}
> subprocess.CalledProcessError: Command
> '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '{-}cp',
> '/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
> 'org.jolokia.jvmagent.client.AgentLauncher', '{-}{-}host', '127.0.0.2',
> '{-}-port', '8778', 'start', '1123')' returned non-zero exit status 1.
> {code}
> [https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/junit/dtest-novnode.auth_test/TestNetworkAuth/test_revoked_dc_access/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17922) Jolokia agent fails to connect though port is available
[
https://issues.apache.org/jira/browse/CASSANDRA-17922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17922:
-
Status: Patch Available (was: Open)
> Jolokia agent fails to connect though port is available
> ---
>
> Key: CASSANDRA-17922
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17922
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.1.x, 4.x
>
>
> In CASSANDRA-17872 we added protection around failures similar to this,
> caused by the port being in use, which is no longer the case:
> {code}
> subprocess.CalledProcessError: Command
> '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '{-}cp',
> '/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
> 'org.jolokia.jvmagent.client.AgentLauncher', '{-}{-}host', '127.0.0.2',
> '{-}-port', '8778', 'start', '1123')' returned non-zero exit status 1.
> {code}
> [https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/junit/dtest-novnode.auth_test/TestNetworkAuth/test_revoked_dc_access/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-dtest] branch trunk updated: retry jmx, switch prints to logger
This is an automated email from the ASF dual-hosted git repository.
brandonwilliams pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-dtest.git
The following commit(s) were added to refs/heads/trunk by this push:
new 860d005f retry jmx, switch prints to logger
860d005f is described below
commit 860d005f63f7a31dcdae234a24af605e279b6e75
Author: Brandon Williams
AuthorDate: Mon Oct 3 09:13:14 2022 -0500
retry jmx, switch prints to logger
Patch by brandonwilliams; reviewed by jmckenzie for CASSANDRA-17922
---
tools/jmxutils.py | 32 ++--
1 file changed, 22 insertions(+), 10 deletions(-)
diff --git a/tools/jmxutils.py b/tools/jmxutils.py
index 137f0159..8d82815f 100644
--- a/tools/jmxutils.py
+++ b/tools/jmxutils.py
@@ -2,6 +2,7 @@ import json
import os
import subprocess
import socket
+import time
import urllib.request
import urllib.parse
import logging
@@ -204,6 +205,7 @@ class JolokiaAgent(object):
if not port:
raise Exception("Port 8778 still in use on {}, unable to find
another available port in range 8000-9000, cannot launch
jolokia".format(socket.gethostname()))
+logger.info("Port %s open for jolokia" % port)
args = (java_bin(),
'-cp', jolokia_classpath(),
'org.jolokia.jvmagent.client.AgentLauncher',
@@ -211,13 +213,23 @@ class JolokiaAgent(object):
'--port', str(port),
'start', str(self.node.pid))
-try:
-subprocess.check_output(args, stderr=subprocess.STDOUT)
-except subprocess.CalledProcessError as exc:
-print("Failed to start jolokia agent (command was: %s): %s" % ('
'.join(args), exc))
-print("Exit status was: %d" % (exc.returncode,))
-print("Output was: %s" % (exc.output,))
-raise
+tries = 3
+for i in range(tries):
+try:
+subprocess.check_output(args, stderr=subprocess.STDOUT,
text=True)
+logger.info("Jolokia successful on try %s" % i )
+return
+except subprocess.CalledProcessError as exc:
+if 'Jolokia is already attached' in exc.output:
+logger.info("Jolokia reports being attached on try %s,
returning successfully" % i)
+return;
+if i < tries - 1:
+logger.warn("Failed to start jolokia agent (command was:
%s): %s" % (' '.join(args), exc))
+logger.warn("Exit status was: %d" % (exc.returncode,))
+logger.warn("Output was: %s" % (exc.output,))
+time.sleep(2)
+else:
+raise
def stop(self):
"""
@@ -230,9 +242,9 @@ class JolokiaAgent(object):
try:
subprocess.check_output(args, stderr=subprocess.STDOUT)
except subprocess.CalledProcessError as exc:
-print("Failed to stop jolokia agent (command was: %s): %s" % ('
'.join(args), exc))
-print("Exit status was: %d" % (exc.returncode,))
-print("Output was: %s" % (exc.output,))
+logger.error("Failed to stop jolokia agent (command was: %s): %s"
% (' '.join(args), exc))
+logger.error("Exit status was: %d" % (exc.returncode,))
+logger.error("Output was: %s" % (exc.output,))
raise
def _query(self, body, verbose=True):
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17922) Jolokia agent fails to connect though port is available
[
https://issues.apache.org/jira/browse/CASSANDRA-17922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623176#comment-17623176
]
Josh McKenzie commented on CASSANDRA-17922:
---
+1
> Jolokia agent fails to connect though port is available
> ---
>
> Key: CASSANDRA-17922
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17922
> Project: Cassandra
> Issue Type: Bug
> Components: Build
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.1.x, 4.x
>
>
> In CASSANDRA-17872 we added protection around failures similar to this,
> caused by the port being in use, which is no longer the case:
> {code}
> subprocess.CalledProcessError: Command
> '('/usr/lib/jvm/java-8-openjdk-amd64/bin/java', '{-}cp',
> '/usr/lib/jvm/java-8-openjdk-amd64/lib/tools.jar:/home/cassandra/cassandra/cassandra-dtest/tools/../lib/jolokia-jvm-1.7.1-agent.jar',
> 'org.jolokia.jvmagent.client.AgentLauncher', '{-}{-}host', '127.0.0.2',
> '{-}-port', '8778', 'start', '1123')' returned non-zero exit status 1.
> {code}
> [https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/junit/dtest-novnode.auth_test/TestNetworkAuth/test_revoked_dc_access/]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17240) CEP-19: Trie memtable implementation
[ https://issues.apache.org/jira/browse/CASSANDRA-17240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623160#comment-17623160 ] Andres de la Peña commented on CASSANDRA-17240: --- Just created CASSANDRA-17989 for adding tries to Jenkins, and CASSANDRA-17987 for running specialised unit tests with Java 11 on CircleCI. > CEP-19: Trie memtable implementation > > > Key: CASSANDRA-17240 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17240 > Project: Cassandra > Issue Type: Improvement > Components: Local/Memtable >Reporter: Branimir Lambov >Assignee: Branimir Lambov >Priority: Normal > Fix For: 4.2 > > Attachments: SkipListMemtable-OSS.png, TrieMemtable-OSS.png, > density_SG.html.gz, density_test_with_sharding.html.gz, latency-1_1-95.png, > latency-9_1-95.png, throughput_SG.png, throughput_apache.png > > Time Spent: 13.5h > Remaining Estimate: 0h > > Trie-based memtable implementation as described in CEP-19, built on top of > CASSANDRA-17034 and CASSANDRA-6936. > The implementation is available in this > [branch|https://github.com/blambov/cassandra/tree/CASSANDRA-17240]. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17989) Jenkins: Add unit tests for trie-based memtables
Andres de la Peña created CASSANDRA-17989: - Summary: Jenkins: Add unit tests for trie-based memtables Key: CASSANDRA-17989 URL: https://issues.apache.org/jira/browse/CASSANDRA-17989 Project: Cassandra Issue Type: Task Components: CI Reporter: Andres de la Peña CASSANDRA-17240 has recently added a CircleCI job for running unit tests with trie-based memtables. These tests should also be added to Jenkins. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17988) A dedicated "events" section on Cassandra website
Stefano Lottini created CASSANDRA-17988: --- Summary: A dedicated "events" section on Cassandra website Key: CASSANDRA-17988 URL: https://issues.apache.org/jira/browse/CASSANDRA-17988 Project: Cassandra Issue Type: Improvement Components: Documentation/Website Reporter: Stefano Lottini Attachments: events1.png, events2.png This is a proposed "Events" section on the Cassandra website, listing (approved) events as small cards with a picture, a short description and a link to the external event website. The motivation behind this idea, which was discussed briefly on the [cassandra-website|https://issues.apache.org/jira/browse/CASSANDRA-website] Slack channel as well, is twofold: on one hand, it is desirable to provide this information to website visitors, which helps building the community through dedicated events; on the other hand, the Cassandra blog is preferrably not 'clogged' with too many event announcements so that it can retain its primary "technical" role. I tried to create a page that blends in with the rest of the website experience, but while doing so I had to make some choices. In particular, I propose an icon for the section (a circus tent) that I hope conveys a "playful but not silly" message; moreover, I added the "Events" page to the "Community" navbar menu to avoid adding another menu, even though all other "Community" menu items are from the community page. Also I am aware that the buttons alignment on the cards is imperfect. I blame my (very limited) css knowledge, this is of course something to improve if ever this draft gets accepted. The PR (which probably should be taken as a WIP, for the aforementioned button alignment issues if nothing else) is here: https://github.com/apache/cassandra-website/pull/185 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17671) Run utests_system_keyspace_directory with Java 11 in CircleCI
[ https://issues.apache.org/jira/browse/CASSANDRA-17671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623147#comment-17623147 ] Andres de la Peña commented on CASSANDRA-17671: --- Just created CASSANDRA-17987 for making Java 11 jobs for all specialized unit tests. This should give us a general picture for deciding job names, approval steps, etc. in a consistent manner. Also, the required config changes should be quite minimal, and doing all of them at once would probably save us both effort and test runs. > Run utests_system_keyspace_directory with Java 11 in CircleCI > - > > Key: CASSANDRA-17671 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17671 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Ekaterina Dimitrova >Priority: Normal > > Currently we run those tests only with Java 8, I have to dig into it further > but it seems that there is no specific reason not to run those with Java 11 > too. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17987) CircleCI: Add jobs for running specialized unit tests with Java 11
Andres de la Peña created CASSANDRA-17987: - Summary: CircleCI: Add jobs for running specialized unit tests with Java 11 Key: CASSANDRA-17987 URL: https://issues.apache.org/jira/browse/CASSANDRA-17987 Project: Cassandra Issue Type: Task Components: CI Reporter: Andres de la Peña Assignee: Andres de la Peña CircleCI has a set of jobs for running specialiazed unit tests that are only run with Java 8: * utests_compression * utests_system_keyspace_directory * utests_trie * utests_stress * utests_long * utests_fqltool It should probably be possible to run these tests with Java 11 tool. Rather than creating a ticket for every job, it's probably easier to use a single ticket for all of them. This should give us an overall vision for deciding job names, approval steps, etc. Also, the required config changes should be quite minimal and doing all of them at once should save us both effort and test runs. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17811) CQL aggregation functions on collections, tuples and UDTs
[
https://issues.apache.org/jira/browse/CASSANDRA-17811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-17811:
--
Epic Link: CASSANDRA-17940
> CQL aggregation functions on collections, tuples and UDTs
> -
>
> Key: CASSANDRA-17811
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17811
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Semantics
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
>
> It has been found during CASSANDRA-8877 that CQLS's aggregation functions
> {{{}max{}}}, {{min}} and {{count}} can be applied to collections, but the
> result is returned as a blob. For example:
> {code:java}
> CREATE TABLE t (k int PRIMARY KEY, l list);
> INSERT INTO t(k, l) VALUES (0, [1, 2, 3]);
> INSERT INTO t(k, l) VALUES (1, [10, 20, 30]);
> SELECT max(l) FROM t;
> system.max(l)
>
> 0x00030004000a000400140004001e
> {code}
> This happens on 3.0, 3.11, 4.0, 4.1 and trunk.
> I'm not sure on whether the function shouldn't be supported for collections,
> or it should be supported but the result is wrong.
> In the example above, the returned blob is the serialized value of {{{}[10,
> 20, 30]{}}}, which is the right one according to the list comparator. I think
> this happens because the matched version of the function is the one for
> {{{}(blob) -> blob{}}}. We would need a {{(list) -> list}} function
> instead, but this function doesn't exist.
> It would be quite easy to add versions of the {{{}max{}}}, {{min}} and
> {{count}} functions for every type of collection ({{{}list{}}},
> {{{}list{}}}, {{{}map{}}}, {{{}map{}}}, etc.). The
> downside of this approach is that it would increase the number of aggregation
> functions kept in memory from 82 to 2722, if my maths are right. This is
> quite an increase, mainly due to the many possible combinations of the
> {{map}} type.
> [Here|https://github.com/adelapena/cassandra/commit/e3ba3c2dc36ce58d06942078c708ffb93eb3cd84]
> is a quick, incomplete prototype of the approach.
> Also, I'm not sure that applying those aggregation functions to collections
> is very useful in practice. Thus, an alternative approach would be just
> forbidding them, considering them not supported. I don't think it would be a
> problem for backward compatibility since no one has complained about the
> current behaviour, and we might well consider that the original intent was
> not to allow aggregation on collections. At least, there aren't any tests for
> it, and I can't find any documentation about it either.
> Another idea that comes to mind is that we could change the meaning of those
> functions to aggregate the values within the collection, instead of
> aggregating the rows. In that case, the behaviour would be:
> {code:java}
> CREATE TABLE t (k int PRIMARY KEY, l list);
> INSERT INTO t(k, l) VALUES (0, [1, 2, 3]);
> INSERT INTO t(k, l) VALUES (1, [10, 20, 30]);
> SELECT max(l) FROM t;
> k | system.max(l)
> ---+---
> 1 | 30
> 0 | 3
> {code}
> Of course we could have separate function names for that type of collection
> aggregations, like {{{}collectionMax{}}}, {{{}maxItem{}}}, or something like
> that.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-17986) improve StartupException related codes
[
https://issues.apache.org/jira/browse/CASSANDRA-17986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623134#comment-17623134
]
Stefan Miklosovic edited comment on CASSANDRA-17986 at 10/24/22 11:52 AM:
--
We should probably revisit the methods around this code to clean System.out
logging as well. I am not completely sure if it done on purpose or not.
Suggested improvement in the description might be applied from 3.0 included.
was (Author: smiklosovic):
We should probably revisit the methods around this code to clean System.out
logging as well. I am not completely sure if it done on purpose or not.
> improve StartupException related codes
> --
>
> Key: CASSANDRA-17986
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17986
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Other
>Reporter: Ling Mao
>Priority: Normal
>
> 1. We should use the enum: _*ERR_WRONG_MACHINE_STATE*_ and
> *_ERR_WRONG_DISK_STATE_* to replace the magic number: 1 and 3
> {code:java}
> exitOrFail(1, e.getMessage(), e.getCause());
> exitOrFail(3, "Exception encountered during startup", e);{code}
>
> 2. Delete the useless field: *_ERR_OUTDATED_SCHEMA_*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17986) improve StartupException related codes
[
https://issues.apache.org/jira/browse/CASSANDRA-17986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623134#comment-17623134
]
Stefan Miklosovic commented on CASSANDRA-17986:
---
We should probably revisit the methods around this code to clean System.out
logging as well. I am not completely sure if it done on purpose or not.
> improve StartupException related codes
> --
>
> Key: CASSANDRA-17986
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17986
> Project: Cassandra
> Issue Type: Improvement
> Components: Local/Other
>Reporter: Ling Mao
>Priority: Normal
>
> 1. We should use the enum: _*ERR_WRONG_MACHINE_STATE*_ and
> *_ERR_WRONG_DISK_STATE_* to replace the magic number: 1 and 3
> {code:java}
> exitOrFail(1, e.getMessage(), e.getCause());
> exitOrFail(3, "Exception encountered during startup", e);{code}
>
> 2. Delete the useless field: *_ERR_OUTDATED_SCHEMA_*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17955) Race condition on repair snapshots
[
https://issues.apache.org/jira/browse/CASSANDRA-17955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623131#comment-17623131
]
Marcus Eriksson commented on CASSANDRA-17955:
-
Haven't looked at this in detail, but purpose of 17168 was just to avoid doing
this on GossipTasks, so as long as its not there we're fine
> Race condition on repair snapshots
> --
>
> Key: CASSANDRA-17955
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17955
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair, Local/Snapshots
>Reporter: Cameron Zemek
>Assignee: Stefan Miklosovic
>Priority: Normal
> Labels: 4.0
> Fix For: 4.0.x, 4.1-rc, 4.x
>
> Attachments: signature.asc
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> If an endpoint is convicted and that endpoint is a coordinator then
> ActiveRepairService::removeParentRepairSession is called.
> The issue is that this occurs on clearSnapshotExecutor and can happen while
> RepairMessageVerbHandler is in process of taking a snapshot. So then you get
> a race condition and clearSnapshot will throw a
> java.nio.file.DirectoryNotEmptyException
>
> {code:java}
> public static void deleteRecursiveWithThrottle(File dir, RateLimiter
> rateLimiter)
> {
> if (dir.isDirectory())
> {
> String[] children = dir.list();
> for (String child : children)
> deleteRecursiveWithThrottle(new File(dir, child), rateLimiter);
> }
> // The directory is now empty so now it can be smoked
> deleteWithConfirmWithThrottle(dir, rateLimiter);
> } {code}
> Due to the directory not being empty when it goes to remove the directory at
> the end.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17986) improve StartupException related codes
Ling Mao created CASSANDRA-17986:
Summary: improve StartupException related codes
Key: CASSANDRA-17986
URL: https://issues.apache.org/jira/browse/CASSANDRA-17986
Project: Cassandra
Issue Type: Improvement
Components: Local/Other
Reporter: Ling Mao
1. We should use the enum: _*ERR_WRONG_MACHINE_STATE*_ and
*_ERR_WRONG_DISK_STATE_* to replace the magic number: 1 and 3
{code:java}
exitOrFail(1, e.getMessage(), e.getCause());
exitOrFail(3, "Exception encountered during startup", e);{code}
2. Delete the useless field: *_ERR_OUTDATED_SCHEMA_*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17985) Handle timeouts when shutting down MessagingService
[ https://issues.apache.org/jira/browse/CASSANDRA-17985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-17985: Test and Documentation Plan: new test + cci run Status: Patch Available (was: Open) 4.0; https://github.com/apache/cassandra/pull/1944 https://app.circleci.com/pipelines/github/krummas/cassandra/833/workflows/4213ed2e-4b62-400a-a9e9-e67e2b12f5bd 4.1; https://github.com/apache/cassandra/pull/1945 https://app.circleci.com/pipelines/github/krummas/cassandra/834/workflows/67af09f6-685e-4c6e-a35e-a9c211135bef trunk; https://github.com/apache/cassandra/pull/1946 https://app.circleci.com/pipelines/github/krummas/cassandra/835/workflows/c9327dc4-afde-41c6-ae2c-74f80feca43d > Handle timeouts when shutting down MessagingService > --- > > Key: CASSANDRA-17985 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17985 > Project: Cassandra > Issue Type: Bug > Components: Local/Startup and Shutdown >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 4.0.x, 4.1.x, 4.x > > > Sometimes when shutting down messaging service during decommission we get a > timeout exception, which leaves StorageService.operationMode in "LEAVING" > instead of "DECOMMISSIONED" > We should catch the exception, improve logging and increase the timeout -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17985) Handle timeouts when shutting down MessagingService
[ https://issues.apache.org/jira/browse/CASSANDRA-17985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-17985: Discovered By: Adhoc Test (was: Code Inspection) > Handle timeouts when shutting down MessagingService > --- > > Key: CASSANDRA-17985 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17985 > Project: Cassandra > Issue Type: Bug > Components: Local/Startup and Shutdown >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 4.0.x, 4.1.x, 4.x > > > Sometimes when shutting down messaging service during decommission we get a > timeout exception, which leaves StorageService.operationMode in "LEAVING" > instead of "DECOMMISSIONED" > We should catch the exception, improve logging and increase the timeout -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17985) Handle timeouts when shutting down MessagingService
[ https://issues.apache.org/jira/browse/CASSANDRA-17985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcus Eriksson updated CASSANDRA-17985: Bug Category: Parent values: Degradation(12984)Level 1 values: Other Exception(12998) Complexity: Low Hanging Fruit Component/s: Local/Startup and Shutdown Discovered By: Code Inspection Fix Version/s: 4.0.x 4.1.x 4.x Severity: Low Status: Open (was: Triage Needed) > Handle timeouts when shutting down MessagingService > --- > > Key: CASSANDRA-17985 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17985 > Project: Cassandra > Issue Type: Bug > Components: Local/Startup and Shutdown >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > Fix For: 4.0.x, 4.1.x, 4.x > > > Sometimes when shutting down messaging service during decommission we get a > timeout exception, which leaves StorageService.operationMode in "LEAVING" > instead of "DECOMMISSIONED" > We should catch the exception, improve logging and increase the timeout -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-17985) Handle timeouts when shutting down MessagingService
Marcus Eriksson created CASSANDRA-17985: --- Summary: Handle timeouts when shutting down MessagingService Key: CASSANDRA-17985 URL: https://issues.apache.org/jira/browse/CASSANDRA-17985 Project: Cassandra Issue Type: Bug Reporter: Marcus Eriksson Assignee: Marcus Eriksson Sometimes when shutting down messaging service during decommission we get a timeout exception, which leaves StorageService.operationMode in "LEAVING" instead of "DECOMMISSIONED" We should catch the exception, improve logging and increase the timeout -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (c6077b90 -> 76082825)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard c6077b90 generate docs for 4212d0c8 new 76082825 generate docs for 4212d0c8 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (c6077b90) \ N -- N -- N refs/heads/asf-staging (76082825) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4746956 -> 4746956 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16369) JaCoCo reports on all unit test jobs on ci-cassandra.a.o
[ https://issues.apache.org/jira/browse/CASSANDRA-16369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17622990#comment-17622990 ] Berenguer Blasi commented on CASSANDRA-16369: - Yep why not. It still amazes me the 100MB report though... > JaCoCo reports on all unit test jobs on ci-cassandra.a.o > > > Key: CASSANDRA-16369 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16369 > Project: Cassandra > Issue Type: Task > Components: CI >Reporter: Michael Semb Wever >Assignee: Michael Semb Wever >Priority: Normal > Attachments: Screenshot 2020-12-24 at 14.23.13.png, Screenshot > 2020-12-24 at 14.23.57.png > > > Enable the jenkins [jacoco plugin|https://plugins.jenkins.io/jacoco/] and > wrap all test runs with jacoco. > Patch at > https://github.com/apache/cassandra-builds/compare/trunk...thelastpickle:mck/tests_jacoco > Example results are: > - CI build: > https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-test/149/ > - CI JaCoCo report: > https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch-test/149/jdk=jdk_1.8_latest,label=cassandra/jacoco/ -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
