[jira] [Updated] (CASSANDRA-17988) WEBSITE - Add a dedicated Events page
[ https://issues.apache.org/jira/browse/CASSANDRA-17988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17988: -- Status: In Progress (was: Patch Available) > WEBSITE - Add a dedicated Events page > - > > Key: CASSANDRA-17988 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17988 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Stefano Lottini >Assignee: Stefano Lottini >Priority: Normal > Fix For: NA > > Attachments: c17988-03-events-v3.png, c17988-04-top_menu_option.png, > events-B-1-1.png, events-B-1.png, events-B-2-1.png, events-B-2.png, > 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] [Updated] (CASSANDRA-17988) WEBSITE - Add a dedicated Events page
[ https://issues.apache.org/jira/browse/CASSANDRA-17988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17988: -- Status: Patch Available (was: Review In Progress) > WEBSITE - Add a dedicated Events page > - > > Key: CASSANDRA-17988 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17988 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Stefano Lottini >Assignee: Stefano Lottini >Priority: Normal > Fix For: NA > > Attachments: c17988-03-events-v3.png, c17988-04-top_menu_option.png, > events-B-1-1.png, events-B-1.png, events-B-2-1.png, events-B-2.png, > 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
[cassandra-website] branch asf-staging updated (5f38c40a -> 83c88e7a)
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 5f38c40a generate docs for 383ccc6e new 83c88e7a generate docs for 383ccc6e 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 (5f38c40a) \ N -- N -- N refs/heads/asf-staging (83c88e7a) 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-15402) Make incremental backup configurable per keyspace and table
[ https://issues.apache.org/jira/browse/CASSANDRA-15402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625384#comment-17625384 ] maxwellguo commented on CASSANDRA-15402: [~blerer] My patch is ready now [CASSANDRA-15402|https://github.com/Maxwell-Guo/cassandra/tree/CASSANDRA-15402] . [CI |https://app.circleci.com/pipelines/github/Maxwell-Guo/cassandra?branch=CASSANDRA-15402] Can you help to look at this patch ? and I found it is just like [CASSANDRA-10383|https://issues.apache.org/jira/browse/CASSANDRA-10383] [~stefan.miklosovic] can you help to look at this too? > Make incremental backup configurable per keyspace and table > --- > > Key: CASSANDRA-15402 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15402 > Project: Cassandra > Issue Type: Improvement > Components: Local/Other, Tool/nodetool >Reporter: maxwellguo >Assignee: maxwellguo >Priority: Normal > Labels: pull-request-available > Fix For: 4.2 > > Time Spent: 20m > Remaining Estimate: 0h > > We know that when we do backup for cassandra, we can do full bakcup with > snapshot, when we need to backup incremental data , incremental_backup can do > some help . > For snapshot we can just make snapshot for some keyspace/table. but > incremental backup will do all data backup(make hard link for all sstable > that flush from memtable or streaming ). we also know that commitlog's replay > can do some keyspace /table 's filter. > So I think for incremental backup we also need some filter for it.After all > not all keyspace/table is so important to do backup. -- 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-15402) Make incremental backup configurable per keyspace and table
[ https://issues.apache.org/jira/browse/CASSANDRA-15402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] maxwellguo updated CASSANDRA-15402: --- Fix Version/s: 4.2 (was: 4.x) > Make incremental backup configurable per keyspace and table > --- > > Key: CASSANDRA-15402 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15402 > Project: Cassandra > Issue Type: Improvement > Components: Local/Other, Tool/nodetool >Reporter: maxwellguo >Assignee: maxwellguo >Priority: Normal > Labels: pull-request-available > Fix For: 4.2 > > Time Spent: 20m > Remaining Estimate: 0h > > We know that when we do backup for cassandra, we can do full bakcup with > snapshot, when we need to backup incremental data , incremental_backup can do > some help . > For snapshot we can just make snapshot for some keyspace/table. but > incremental backup will do all data backup(make hard link for all sstable > that flush from memtable or streaming ). we also know that commitlog's replay > can do some keyspace /table 's filter. > So I think for incremental backup we also need some filter for it.After all > not all keyspace/table is so important to do backup. -- 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=17625369#comment-17625369 ] Ekaterina Dimitrova commented on CASSANDRA-17987: - Sorry, It's 10pm already and my brain is frying already, I will check those tomorrow morning first thing. I briefly looked the 3.0 patch and it looked fine to me > 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-17992) Upgrade Netty on 4.x(current trunk)
[
https://issues.apache.org/jira/browse/CASSANDRA-17992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625366#comment-17625366
]
Ekaterina Dimitrova edited comment on CASSANDRA-17992 at 10/28/22 1:37 AM:
---
{quote}Getting the full stack trace will help inform next steps.
{quote}
I think I have some preliminary good news. I ran some rough tests today to get
to it. I suspect things might have improved on Netty side recently.
So with the Netty version that was current in March, [current trunk and
JDK17|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=trunk-jdk17-oct]
I can see 55 failing tests and a bunch of SSL tests.
Now looking into the cqlsh tests
[here|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2005/workflows/18b54727-8b82-42cc-9dd2-5a04bfb06e5a/jobs/16218/tests#failed-test-1]
I can also find the issue we discussed, test_tls:
{code:java}
test teardown failure Unexpected error found in node logs (see stdout for full
details). Errors: [[node1] "WARN [nioEventLoopGroup-5-5] 2022-10-27
22:45:13,917 ExceptionHandlers.java:140 - Unknown exception in client
networking\nio.netty.handler.codec.DecoderException:
javax.net.ssl.SSLException: Fail to unwrap network record\n\tat
io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:480)\n\tat
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:279)\n\tat
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)\n\tat
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)\n\tat
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)\n\tat
io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)\n\tat
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)\n\tat
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)\n\tat
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)\n\tat
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)\n\tat
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:722)\n\tat
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:658)\n\tat
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:584)\n\tat
io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:496)\n\tat
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)\n\tat
io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)\n\tat
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
java.base/java.lang.Thread.run(Thread.java:833)\nCaused by:
javax.net.ssl.SSLException: Fail to unwrap network record\n\tat
java.base/sun.security.ssl.Alert.createSSLException(Alert.java:133)\n\tat
java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:371)\n\tat
java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:314)\n\tat
java.base/sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:522)\n\tat
java.base/sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:482)\n\tat
java.base/javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:679)\n\tat
io.netty.handler.ssl.SslHandler$SslEngineType$3.unwrap(SslHandler.java:295)\n\tat
io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1341)\n\tat
io.netty.handler.ssl.SslHandler.decodeJdkCompatible(SslHandler.java:1234)\n\tat
io.netty.handler.ssl.SslHandler.decode(SslHandler.java:1283)\n\tat
io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:510)\n\tat
io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:449)\n\t...
17 common frames omitted\nCaused by: java.lang.ClassCastException: class
org.apache.cassandra.utils.memory.BufferPool$Chunk cannot be cast to class
sun.nio.ch.DirectBuffer (org.apache.cassandra.utils.memory.BufferPool$Chunk is
in unnamed module of loader 'app'; sun.nio.ch.DirectBuffer is in module
java.base of loader 'bootstrap')\n\tat
java.base/com.sun.crypto.provider.GaloisCounterMode$GCMEngine.overlapDetection(GaloisCounterMode.java:865)\n\tat
java.base/com.sun.crypto.provider.GaloisCounterMode$GCMDecrypt.doFinal(GaloisCounterMode.java:1502)\n\tat
java.base/com.sun.crypto.provider.GaloisCounterMode.engineDoFinal(GaloisCounterMode.java:447)\n\tat
java.base/javax.crypto.Cipher.doFinal(Cipher.java:2500)\n\tat
java.base/sun.security.ssl.SSLCipher$T12GcmReadCipherGenerator$GcmReadCipher.decrypt(SSLCipher.java:1659)\n\tat
[jira] [Commented] (CASSANDRA-17992) Upgrade Netty on 4.x(current trunk)
[
https://issues.apache.org/jira/browse/CASSANDRA-17992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625366#comment-17625366
]
Ekaterina Dimitrova commented on CASSANDRA-17992:
-
{quote}Getting the full stack trace will help inform next steps.
{quote}
I think I have some preliminary good news. I ran some rough tests today to get
to it. I suspect things might have improved on Netty side recently.
So with the version that was current in March, [current trunk and
JDK17|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=trunk-jdk17-oct]
I can see 55 failing tests and a bunch of SSL tests.
Now looking into the cqlsh tests
[here|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2005/workflows/18b54727-8b82-42cc-9dd2-5a04bfb06e5a/jobs/16218/tests#failed-test-1]
I can also find the issue we discussed, test_tls:
{code:java}
test teardown failure Unexpected error found in node logs (see stdout for full
details). Errors: [[node1] "WARN [nioEventLoopGroup-5-5] 2022-10-27
22:45:13,917 ExceptionHandlers.java:140 - Unknown exception in client
networking\nio.netty.handler.codec.DecoderException:
javax.net.ssl.SSLException: Fail to unwrap network record\n\tat
io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:480)\n\tat
io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:279)\n\tat
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)\n\tat
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)\n\tat
io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)\n\tat
io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)\n\tat
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)\n\tat
io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)\n\tat
io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)\n\tat
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:166)\n\tat
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:722)\n\tat
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:658)\n\tat
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:584)\n\tat
io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:496)\n\tat
io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:986)\n\tat
io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)\n\tat
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
java.base/java.lang.Thread.run(Thread.java:833)\nCaused by:
javax.net.ssl.SSLException: Fail to unwrap network record\n\tat
java.base/sun.security.ssl.Alert.createSSLException(Alert.java:133)\n\tat
java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:371)\n\tat
java.base/sun.security.ssl.TransportContext.fatal(TransportContext.java:314)\n\tat
java.base/sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:522)\n\tat
java.base/sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:482)\n\tat
java.base/javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:679)\n\tat
io.netty.handler.ssl.SslHandler$SslEngineType$3.unwrap(SslHandler.java:295)\n\tat
io.netty.handler.ssl.SslHandler.unwrap(SslHandler.java:1341)\n\tat
io.netty.handler.ssl.SslHandler.decodeJdkCompatible(SslHandler.java:1234)\n\tat
io.netty.handler.ssl.SslHandler.decode(SslHandler.java:1283)\n\tat
io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:510)\n\tat
io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:449)\n\t...
17 common frames omitted\nCaused by: java.lang.ClassCastException: class
org.apache.cassandra.utils.memory.BufferPool$Chunk cannot be cast to class
sun.nio.ch.DirectBuffer (org.apache.cassandra.utils.memory.BufferPool$Chunk is
in unnamed module of loader 'app'; sun.nio.ch.DirectBuffer is in module
java.base of loader 'bootstrap')\n\tat
java.base/com.sun.crypto.provider.GaloisCounterMode$GCMEngine.overlapDetection(GaloisCounterMode.java:865)\n\tat
java.base/com.sun.crypto.provider.GaloisCounterMode$GCMDecrypt.doFinal(GaloisCounterMode.java:1502)\n\tat
java.base/com.sun.crypto.provider.GaloisCounterMode.engineDoFinal(GaloisCounterMode.java:447)\n\tat
java.base/javax.crypto.Cipher.doFinal(Cipher.java:2500)\n\tat
java.base/sun.security.ssl.SSLCipher$T12GcmReadCipherGenerator$GcmReadCipher.decrypt(SSLCipher.java:1659)\n\tat
[cassandra-website] branch asf-staging updated (faee4637 -> 5f38c40a)
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 faee4637 generate docs for 383ccc6e new 5f38c40a generate docs for 383ccc6e 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 (faee4637) \ N -- N -- N refs/heads/asf-staging (5f38c40a) 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: site-ui/build/ui-bundle.zip | Bin 4746956 -> 4746956 bytes 1 file changed, 0 insertions(+), 0 deletions(-) - 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 (8b89685b -> faee4637)
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 8b89685b generate docs for 383ccc6e new faee4637 generate docs for 383ccc6e 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 (8b89685b) \ N -- N -- N refs/heads/asf-staging (faee4637) 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: site-ui/build/ui-bundle.zip | Bin 4746956 -> 4746956 bytes 1 file changed, 0 insertions(+), 0 deletions(-) - 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 (08179a99 -> 8b89685b)
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 08179a99 generate docs for 383ccc6e new 8b89685b generate docs for 383ccc6e 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 (08179a99) \ N -- N -- N refs/heads/asf-staging (8b89685b) 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: site-ui/build/ui-bundle.zip | Bin 4746956 -> 4746956 bytes 1 file changed, 0 insertions(+), 0 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17915) Confusing error message when using ? with functions
[
https://issues.apache.org/jira/browse/CASSANDRA-17915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Natnael Adere updated CASSANDRA-17915:
--
Status: Patch Available (was: In Progress)
Patch: [trunk|https://github.com/apache/cassandra/pull/1957] ,
[4.0|https://github.com/apache/cassandra/pull/1928] ,
[4.1|https://github.com/apache/cassandra/pull/1929]
Circle CI:
[trunk|https://app.circleci.com/pipelines/github/NateAdere/cassandra?branch=Cassandra-17915-trun]
,
[4.0|https://app.circleci.com/pipelines/github/NateAdere/cassandra?branch=Cassandra-17915-4.0]
,
[4.1|https://app.circleci.com/pipelines/github/NateAdere/cassandra?branch=Cassandra-17915-4.1]
> Confusing error message when using ? with functions
> ---
>
> Key: CASSANDRA-17915
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17915
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Interpreter
>Reporter: David Capwell
>Assignee: Natnael Adere
>Priority: Normal
> Fix For: 4.0.x, 4.1.x
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> {code}
> INSERT INTO %S (a, b, c) VALUES (? + 1, ?, ?)
> {code}
> Errors saying
> {code}
> Ambiguous '+' operation with args ? and 1: use type casts to disambiguate
> {code}
> Now, if you google “type casts CQL” you get
> https://docs.datastax.com/en/dse/5.1/cql/cql/cql_reference/refCqlFunction.html
> which says to do
> {code}
> CAST( selector AS to_type )
> {code}
> But this also fails!
> {code}
> InvalidRequestException: Ambiguous call to function system.castAsFloat (can
> be matched by following signatures: system."castAsFloat" : (bigint) -> float,
> system."castAsFloat" : (counter) -> float, system."castAsFloat" : (double) ->
> float, system."castAsFloat" : (int) -> float, system."castAsFloat" :
> (tinyint) -> float, system."castAsFloat" : (varint) -> float,
> system."castAsFloat" : (decimal) -> float, system."castAsFloat" : (smallint)
> -> float): use type casts to disambiguate
> {code}
> What we have to do is
> {code}
> INSERT INTO %S (a, b, c) VALUES ((int) ? + 1, ?, ?)
> {code}
> We should improve the error message to show the expected syntax (or fix CAST
> to work in this case).
--
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-17928) Test Failure: org.apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest.testCommitLogInitWithException-compression
[
https://issues.apache.org/jira/browse/CASSANDRA-17928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625284#comment-17625284
]
Brandon Williams commented on CASSANDRA-17928:
--
The spin wait timed out on 8 of those runs. :(
> Test Failure:
> org.apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest.testCommitLogInitWithException-compression
> -
>
> Key: CASSANDRA-17928
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17928
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.1-rc
>
>
> [Link|https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/org.apache.cassandra.db.commitlog/CommitLogInitWithExceptionTest/testCommitLogInitWithException_compression/]
> Failed 1 times in the last 14 runs. Flakiness: 7%, Stability: 92%
> Stacktrace
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest.testCommitLogInitWithException(CommitLogInitWithExceptionTest.java:93)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at java.base/java.lang.Thread.run(Thread.java:829)
> {code}
> {code:java}
> Standard Output
> INFO [main] 2022-09-25 11:43:16,512 Reflections.java:219 - Reflections took
> 1221 ms to scan 8 urls, producing 1756 keys and 6922 values
> INFO [main] 2022-09-25 11:43:17,480 Reflections.java:219 - Reflections took
> 907 ms to scan 8 urls, producing 1756 keys and 6922 values
> INFO [main] 2022-09-25 11:43:17,573 YamlConfigurationLoader.java:104 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2022-09-25 11:43:17,574 YamlConfigurationLoader
> ...[truncated 35568 chars]...
> .apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest$MockCommitLogSegmentMgr.createSegment(CommitLogInitWithExceptionTest.java:106)
> at
> org.apache.cassandra.db.commitlog.AbstractCommitLogSegmentManager$AllocatorRunnable.run(AbstractCommitLogSegmentManager.java:155)
> at
> org.apache.cassandra.concurrent.InfiniteLoopExecutor.loop(InfiniteLoopExecutor.java:121)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
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-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:comment-tabpanel=17625263#comment-17625263 ] Caleb Rackliffe edited comment on CASSANDRA-16491 at 10/27/22 7:15 PM: --- +1 Just need to find a second committer to review now. Also, I'll start a CircleCI run w/ a clone of your branch shortly... was (Author: maedhroz): +1 Just need to find a second committer now. Also, I'll start a CircleCI run w/ a clone of your branch shortly... > 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: 4.x > > Time Spent: 1h 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] [Commented] (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:comment-tabpanel=17625263#comment-17625263 ] Caleb Rackliffe commented on CASSANDRA-16491: - +1 Just need to find a second committer now. Also, I'll start a CircleCI run w/ a clone of your branch shortly... > 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: 4.x > > Time Spent: 1h 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
[cassandra-website] branch asf-staging updated (252f98fe -> 08179a99)
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 omit 252f98fe generate docs for 383ccc6e new 08179a99 generate docs for 383ccc6e 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 (252f98fe) \ N -- N -- N refs/heads/asf-staging (08179a99) 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: .../4.1/cassandra/tools/nodetool/gossipinfo.html | 4 .../4.2/cassandra/tools/nodetool/gossipinfo.html | 4 .../cassandra/tools/nodetool/gossipinfo.html | 4 .../trunk/cassandra/tools/nodetool/gossipinfo.html | 4 content/search-index.js| 2 +- site-ui/build/ui-bundle.zip| Bin 4746956 -> 4746956 bytes 6 files changed, 17 insertions(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17507) IllegalArgumentException in query code path during 3.11.12 => 4.0.3 rolling upgrade
[
https://issues.apache.org/jira/browse/CASSANDRA-17507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625241#comment-17625241
]
Paul Ayers commented on CASSANDRA-17507:
This exists during an upgrade from 3.11 to Cassandra 4.0.6 as well.
Was hoping that https://issues.apache.org/jira/browse/CASSANDRA-17840 had fixed
it in 4.0.6, but that doesn't appear to be the case.
Selecting the columns individually does work-around the issue when Select *
fails until all nodes are upgraded.
{code:java}
ERROR [Native-Transport-Requests-4] 2022-10-03 10:51:50,178
ErrorMessage.java:457 - Unexpected exception during request
java.lang.IllegalArgumentException: null
at java.nio.Buffer.limit(Buffer.java:275)
at
org.apache.cassandra.db.marshal.ByteBufferAccessor.slice(ByteBufferAccessor.java:107)
at
org.apache.cassandra.db.marshal.ByteBufferAccessor.slice(ByteBufferAccessor.java:39)
at
org.apache.cassandra.db.marshal.ValueAccessor.sliceWithShortLength(ValueAccessor.java:225)
at
org.apache.cassandra.db.marshal.CompositeType.splitName(CompositeType.java:222)
at
org.apache.cassandra.service.pager.PagingState$RowMark.decodeClustering(PagingState.java:434)
at
org.apache.cassandra.service.pager.PagingState$RowMark.clustering(PagingState.java:388)
at
org.apache.cassandra.service.pager.SinglePartitionPager.nextPageReadQuery(SinglePartitionPager.java:88)
at
org.apache.cassandra.service.pager.SinglePartitionPager.nextPageReadQuery(SinglePartitionPager.java:32)
at
org.apache.cassandra.service.pager.AbstractQueryPager.fetchPage(AbstractQueryPager.java:69)
at
org.apache.cassandra.service.pager.SinglePartitionPager.fetchPage(SinglePartitionPager.java:32)
at
org.apache.cassandra.cql3.statements.SelectStatement$Pager$NormalPager.fetchPage(SelectStatement.java:352)
at
org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:400)
at
org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:250)
at
org.apache.cassandra.cql3.statements.SelectStatement.execute(SelectStatement.java:88)
at
org.apache.cassandra.cql3.QueryProcessor.processStatement(QueryProcessor.java:244)
at
org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:723)
at
org.apache.cassandra.cql3.QueryProcessor.processPrepared(QueryProcessor.java:701)
at
org.apache.cassandra.transport.messages.ExecuteMessage.execute(ExecuteMessage.java:159)
at
org.apache.cassandra.transport.Message$Request.execute(Message.java:242)
at
org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:86)
at
org.apache.cassandra.transport.Dispatcher.processRequest(Dispatcher.java:106)
at
org.apache.cassandra.transport.Dispatcher.lambda$dispatch$0(Dispatcher.java:70)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at
org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$FutureTask.run(AbstractLocalAwareExecutorService.java:165)
at
org.apache.cassandra.concurrent.AbstractLocalAwareExecutorService$LocalSessionFutureTask.run(AbstractLocalAwareExecutorService.java:137)
at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:119)
at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
{code}
> IllegalArgumentException in query code path during 3.11.12 => 4.0.3 rolling
> upgrade
> ---
>
> Key: CASSANDRA-17507
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17507
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Coordination
>Reporter: Thomas Steinmaurer
>Priority: Normal
> Fix For: 4.0.x
>
>
> In a 6 node 3.11.12 test cluster - freshly set up, thus no legacy SSTables
> etc. - with ~ 1TB SSTables on disk per node, I have been running a rolling
> upgrade to 4.0.3. On upgraded 4.0.3 nodes I then have seen the following
> exception regularly, which disappeared once all 6 nodes have been on 4.0.3.
> Is this known? Can this be ignored? As said, just a test drive, but not sure
> if we want to have that in production, especially with a larger number of
> nodes, where it could take some time, until all are upgraded. Thanks!
> {code}
> ERROR [Native-Transport-Requests-8] 2022-03-30 11:30:24,057
> ErrorMessage.java:457 - Unexpected exception during request
> java.lang.IllegalArgumentException: newLimit > capacity: (290 > 15)
> at java.base/java.nio.Buffer.createLimitException(Buffer.java:372)
> at java.base/java.nio.Buffer.limit(Buffer.java:346)
> at
[jira] [Assigned] (CASSANDRA-17972) nodetool resetlocalschema does not sync schema
[
https://issues.apache.org/jira/browse/CASSANDRA-17972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic reassigned CASSANDRA-17972:
-
Assignee: Stefan Miklosovic
> nodetool resetlocalschema does not sync schema
> --
>
> Key: CASSANDRA-17972
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17972
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
>Reporter: Cameron Zemek
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 3.0.x, 3.11.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Steps to reproduce:
> {code:java}
> $ ccm create -n 2 -v 3.11.13 -s resettest
> $ ccm node1 cqlsh -e "CREATE KEYSPACE test WITH replication =
> {'class':'NetworkTopologyStrategy', 'datacenter1': 2}"
> $ ccm node1 cqlsh -e "CREATE TABLE test.messages(id int primary key, message
> text)"
> $ ccm node1 nodetool describecluster
> Cluster Information:
> Name: resettest
> Snitch: org.apache.cassandra.locator.SimpleSnitch
> DynamicEndPointSnitch: enabled
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> 5172094b-dee2-3967-b5f0-dfd81d572a74: [127.0.0.1, 127.0.0.2]
> $ ccm node2 nodetool resetlocalschema
> $ ccm node2 cqlsh -e 'describe full schema'
> $ find ~/.ccm/resettest/node2/data0/system_schema/ -maxdepth 2 -type f
> $ ccm node2 nodetool describecluster
> Cluster Information:
> Name: resettest
> Snitch: org.apache.cassandra.locator.SimpleSnitch
> DynamicEndPointSnitch: enabled
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> 5172094b-dee2-3967-b5f0-dfd81d572a74: [127.0.0.1]
> 59adb24e-f3cd-3e02-97f0-5b395827453f: [127.0.0.2]
> $ ccm node2 stop
> $ ccm node2 start
> $ ccm node2 nodetool describecluster
> Cluster Information:
> Name: jpmctest
> Snitch: org.apache.cassandra.locator.SimpleSnitch
> DynamicEndPointSnitch: enabled
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> 5172094b-dee2-3967-b5f0-dfd81d572a74: [127.0.0.1, 127.0.0.2]
> {code}
> Its not resyncing the schema until after restarting the node.
--
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-17972) nodetool resetlocalschema does not sync schema
[
https://issues.apache.org/jira/browse/CASSANDRA-17972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625215#comment-17625215
]
Stefan Miklosovic commented on CASSANDRA-17972:
---
FYI this is branch for 3.0 where I retrofitted the missing PR (1). I have added
awaitility dependency to reproduce the test added in the other ticket too.
I verified, also manually, that it fixes the issue and it is resetting the
schema fine.
I will continue with 3.11 soonish.
(1) https://github.com/apache/cassandra/pull/1956
> nodetool resetlocalschema does not sync schema
> --
>
> Key: CASSANDRA-17972
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17972
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
>Reporter: Cameron Zemek
>Priority: Normal
> Fix For: 3.0.x, 3.11.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Steps to reproduce:
> {code:java}
> $ ccm create -n 2 -v 3.11.13 -s resettest
> $ ccm node1 cqlsh -e "CREATE KEYSPACE test WITH replication =
> {'class':'NetworkTopologyStrategy', 'datacenter1': 2}"
> $ ccm node1 cqlsh -e "CREATE TABLE test.messages(id int primary key, message
> text)"
> $ ccm node1 nodetool describecluster
> Cluster Information:
> Name: resettest
> Snitch: org.apache.cassandra.locator.SimpleSnitch
> DynamicEndPointSnitch: enabled
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> 5172094b-dee2-3967-b5f0-dfd81d572a74: [127.0.0.1, 127.0.0.2]
> $ ccm node2 nodetool resetlocalschema
> $ ccm node2 cqlsh -e 'describe full schema'
> $ find ~/.ccm/resettest/node2/data0/system_schema/ -maxdepth 2 -type f
> $ ccm node2 nodetool describecluster
> Cluster Information:
> Name: resettest
> Snitch: org.apache.cassandra.locator.SimpleSnitch
> DynamicEndPointSnitch: enabled
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> 5172094b-dee2-3967-b5f0-dfd81d572a74: [127.0.0.1]
> 59adb24e-f3cd-3e02-97f0-5b395827453f: [127.0.0.2]
> $ ccm node2 stop
> $ ccm node2 start
> $ ccm node2 nodetool describecluster
> Cluster Information:
> Name: jpmctest
> Snitch: org.apache.cassandra.locator.SimpleSnitch
> DynamicEndPointSnitch: enabled
> Partitioner: org.apache.cassandra.dht.Murmur3Partitioner
> Schema versions:
> 5172094b-dee2-3967-b5f0-dfd81d572a74: [127.0.0.1, 127.0.0.2]
> {code}
> Its not resyncing the schema until after restarting the node.
--
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-18000) CircleCI: Skip checkstyle in the Ant-based repeated tests
[
https://issues.apache.org/jira/browse/CASSANDRA-18000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625207#comment-17625207
]
Brandon Williams edited comment on CASSANDRA-18000 at 10/27/22 4:41 PM:
bq. please check if we are skipping javadocs too
You'd know from the random failures if they weren't :) We disabled them in
CASSANDRA-17712
was (Author: brandon.williams):
bq. please check if we are skipping javadocs too
You'd know from the random failures if weren't :) We disabled them in
CASSANDRA-17712
> CircleCI: Skip checkstyle in the Ant-based repeated tests
> -
>
> Key: CASSANDRA-18000
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18000
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
>
> The CircleCI jobs for repeating Ant-based tests include the {{checkstyle}}
> and {{checkstyle-test}} targets. Those targets are skipped for Java 11 but
> not for Java 8.
> Including those targets on every test iteration produces a significant
> difference in the run times of repeated test jobs for j8 and j11:
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/122d58b9-b454-4a99-8c46-fb7ef225/jobs/23225]
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/50f33d9b-c7c6-4aa9-bac9-22ac78ad6b8c/jobs/23224]
> We should use the {{no-checkstyle}} flag in the iterations done by those
> jobs. That should significantly speed up the jobs and save resources.
>
> Thanks to [~bereng] , who detected the difference in the running times
> between j8 and j11.
--
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-18000) CircleCI: Skip checkstyle in the Ant-based repeated tests
[
https://issues.apache.org/jira/browse/CASSANDRA-18000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625207#comment-17625207
]
Brandon Williams commented on CASSANDRA-18000:
--
bq. please check if we are skipping javadocs too
You'd know from the random failures if weren't :) We disabled them in
CASSANDRA-17712
> CircleCI: Skip checkstyle in the Ant-based repeated tests
> -
>
> Key: CASSANDRA-18000
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18000
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
>
> The CircleCI jobs for repeating Ant-based tests include the {{checkstyle}}
> and {{checkstyle-test}} targets. Those targets are skipped for Java 11 but
> not for Java 8.
> Including those targets on every test iteration produces a significant
> difference in the run times of repeated test jobs for j8 and j11:
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/122d58b9-b454-4a99-8c46-fb7ef225/jobs/23225]
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/50f33d9b-c7c6-4aa9-bac9-22ac78ad6b8c/jobs/23224]
> We should use the {{no-checkstyle}} flag in the iterations done by those
> jobs. That should significantly speed up the jobs and save resources.
>
> Thanks to [~bereng] , who detected the difference in the running times
> between j8 and j11.
--
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
]
Caleb Rackliffe updated CASSANDRA-16491:
Test and Documentation Plan: Test locally using ccm, `nodetool bootstrap
resume`, and JConsole, additions to {{BootstrapBinaryDisabledTest}} (was: Test
locally using ccm, `nodetool bootstrap resume`, and JConsole)
> 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: 4.x
>
> Time Spent: 1h
> 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] [Assigned] (CASSANDRA-17773) Incorrect cassandra.logdir on Debian systems
[ https://issues.apache.org/jira/browse/CASSANDRA-17773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh McKenzie reassigned CASSANDRA-17773: - Assignee: Claude Warren > Incorrect cassandra.logdir on Debian systems > > > Key: CASSANDRA-17773 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17773 > Project: Cassandra > Issue Type: Bug > Components: Packaging >Reporter: Eric Evans >Assignee: Claude Warren >Priority: Normal > Labels: lhf > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x > > > The Debian packaging patches bin/cassandra to use /var/log/cassandra for > logs, it does so conditionally however, only if CASSANDRA_LOG_DIR is unset. > This occurs _after_ cassandra-env.sh is sourced though, which also sets > CASSANDRA_LOG_DIR if unset (to $CASSANDRA_HOME/logs). The result is that > -Dcassandra.lodir is set to /usr/share/cassandra/logs on Debian systems. -- 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-18000) CircleCI: Skip checkstyle in the Ant-based repeated tests
[
https://issues.apache.org/jira/browse/CASSANDRA-18000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625194#comment-17625194
]
Stefan Miklosovic commented on CASSANDRA-18000:
---
please check if we are skipping javadocs too
> CircleCI: Skip checkstyle in the Ant-based repeated tests
> -
>
> Key: CASSANDRA-18000
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18000
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
>
> The CircleCI jobs for repeating Ant-based tests include the {{checkstyle}}
> and {{checkstyle-test}} targets. Those targets are skipped for Java 11 but
> not for Java 8.
> Including those targets on every test iteration produces a significant
> difference in the run times of repeated test jobs for j8 and j11:
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/122d58b9-b454-4a99-8c46-fb7ef225/jobs/23225]
> *
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/50f33d9b-c7c6-4aa9-bac9-22ac78ad6b8c/jobs/23224]
> We should use the {{no-checkstyle}} flag in the iterations done by those
> jobs. That should significantly speed up the jobs and save resources.
>
> Thanks to [~bereng] , who detected the difference in the running times
> between j8 and j11.
--
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-18000) CircleCI: Skip checkstyle in the Ant-based repeated tests
Andres de la Peña created CASSANDRA-18000:
-
Summary: CircleCI: Skip checkstyle in the Ant-based repeated tests
Key: CASSANDRA-18000
URL: https://issues.apache.org/jira/browse/CASSANDRA-18000
Project: Cassandra
Issue Type: Task
Components: CI
Reporter: Andres de la Peña
Assignee: Andres de la Peña
The CircleCI jobs for repeating Ant-based tests include the {{checkstyle}} and
{{checkstyle-test}} targets. Those targets are skipped for Java 11 but not for
Java 8.
Including those targets on every test iteration produces a significant
difference in the run times of repeated test jobs for j8 and j11:
*
[https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/122d58b9-b454-4a99-8c46-fb7ef225/jobs/23225]
*
[https://app.circleci.com/pipelines/github/adelapena/cassandra/2328/workflows/50f33d9b-c7c6-4aa9-bac9-22ac78ad6b8c/jobs/23224]
We should use the {{no-checkstyle}} flag in the iterations done by those jobs.
That should significantly speed up the jobs and save resources.
Thanks to [~bereng] , who detected the difference in the running times between
j8 and j11.
--
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-17588) "Total TrueDiskSpaceUsed" computation does not include manifest and schema files
[
https://issues.apache.org/jira/browse/CASSANDRA-17588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic reassigned CASSANDRA-17588:
-
Assignee: Stefan Miklosovic (was: Stefan Miklosovic)
> "Total TrueDiskSpaceUsed" computation does not include manifest and schema
> files
>
>
> Key: CASSANDRA-17588
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17588
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Snapshots
>Reporter: Paulo Motta
>Assignee: Stefan Miklosovic
>Priority: Normal
>
> This is the output of {{nodetool listsnapshots}}:
> {noformat}
> Snapshot Details:
> Snapshot name Keyspace name Column family name True size
> Size on disk Creation timeExpiration time
> test ksindexed_table 1.1 KiB
> 21.22 KiB2022-04-26T19:13:20.102Z
> test ksmy_table 960 bytes
> 10.76 KiB2022-04-26T19:13:20.102Z
> dropped-1650997415751-my_table ksmy_table 989 bytes 989
> bytes2022-04-26T18:23:35.751Z
> Total TrueDiskSpaceUsed: 0 KiB
> {noformat}
> Total TrueDiskSpaceUsed does not match the sum of "true size on disk" of all
> snapshots.
> The reason for this is because {{Total TrueDiskSpaceUsed}} computation does
> not include the size of snapshot schema and manifest files.
> We should fix the {{Total TrueDiskSpaceUsed}} computation to include the the
> size of snapshot schema and manifest files, so it will look like this:
> {noformat}
> Snapshot Details:
> Snapshot name Keyspace name Column family name True size
> Size on disk Creation timeExpiration time
> test ksindexed_table 1.1 KiB
> 21.22 KiB2022-04-26T19:13:20.102Z
> test ksmy_table 960 bytes
> 10.76 KiB2022-04-26T19:13:20.102Z
> dropped-1650997415751-my_table ksmy_table 989 bytes 989
> bytes2022-04-26T18:23:35.751Z
> Total TrueDiskSpaceUsed: 3 KiB
> {noformat}
--
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-17999) Bug fix for WriteTimeoutException when using Paxos v2 in LWT performance test
Marianne Lyne Manaog created CASSANDRA-17999: Summary: Bug fix for WriteTimeoutException when using Paxos v2 in LWT performance test Key: CASSANDRA-17999 URL: https://issues.apache.org/jira/browse/CASSANDRA-17999 Project: Cassandra Issue Type: Bug Reporter: Marianne Lyne Manaog Assignee: Marianne Lyne Manaog A WriteTimeoutException is encountered when using Paxos v2 in an LWT performance test that only has a single datacenter because Paxos was still waiting for a response from another datacenter during the Commit/Acknowledge phase even though we were running with LOCAL_SERIAL. -- 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-17928) Test Failure: org.apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest.testCommitLogInitWithException-compression
[
https://issues.apache.org/jira/browse/CASSANDRA-17928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625166#comment-17625166
]
Brandon Williams edited comment on CASSANDRA-17928 at 10/27/22 3:14 PM:
I think this is still going to fail due to the awaitTermination call, where
mine NPE'd ultimately in that same spot, but we shouldn't need that or the
sleep if we spin wait.
Like
[this|https://github.com/driftx/cassandra/commit/2d8c09678cb1f18c8103cabce1c07073dd435980]
which is running 30k
[here|https://app.circleci.com/pipelines/github/driftx/cassandra/684/workflows/7de84fef-0c04-49ee-9239-bdf88ddefd47/jobs/7510].
was (Author: brandon.williams):
I think this is still going to fail due to the awaitTermination call, where
mine NPE'd ultimately in that same spot, but we shouldn't need that or the
sleep if we spin wait.
> Test Failure:
> org.apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest.testCommitLogInitWithException-compression
> -
>
> Key: CASSANDRA-17928
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17928
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.1-rc
>
>
> [Link|https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/org.apache.cassandra.db.commitlog/CommitLogInitWithExceptionTest/testCommitLogInitWithException_compression/]
> Failed 1 times in the last 14 runs. Flakiness: 7%, Stability: 92%
> Stacktrace
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest.testCommitLogInitWithException(CommitLogInitWithExceptionTest.java:93)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at java.base/java.lang.Thread.run(Thread.java:829)
> {code}
> {code:java}
> Standard Output
> INFO [main] 2022-09-25 11:43:16,512 Reflections.java:219 - Reflections took
> 1221 ms to scan 8 urls, producing 1756 keys and 6922 values
> INFO [main] 2022-09-25 11:43:17,480 Reflections.java:219 - Reflections took
> 907 ms to scan 8 urls, producing 1756 keys and 6922 values
> INFO [main] 2022-09-25 11:43:17,573 YamlConfigurationLoader.java:104 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2022-09-25 11:43:17,574 YamlConfigurationLoader
> ...[truncated 35568 chars]...
> .apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest$MockCommitLogSegmentMgr.createSegment(CommitLogInitWithExceptionTest.java:106)
> at
> org.apache.cassandra.db.commitlog.AbstractCommitLogSegmentManager$AllocatorRunnable.run(AbstractCommitLogSegmentManager.java:155)
> at
> org.apache.cassandra.concurrent.InfiniteLoopExecutor.loop(InfiniteLoopExecutor.java:121)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
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-17928) Test Failure: org.apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest.testCommitLogInitWithException-compression
[
https://issues.apache.org/jira/browse/CASSANDRA-17928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625166#comment-17625166
]
Brandon Williams commented on CASSANDRA-17928:
--
I think this is still going to fail due to the awaitTermination call, where
mine NPE'd ultimately in that same spot, but we shouldn't need that or the
sleep if we spin wait.
> Test Failure:
> org.apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest.testCommitLogInitWithException-compression
> -
>
> Key: CASSANDRA-17928
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17928
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.1-rc
>
>
> [Link|https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/org.apache.cassandra.db.commitlog/CommitLogInitWithExceptionTest/testCommitLogInitWithException_compression/]
> Failed 1 times in the last 14 runs. Flakiness: 7%, Stability: 92%
> Stacktrace
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest.testCommitLogInitWithException(CommitLogInitWithExceptionTest.java:93)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at java.base/java.lang.Thread.run(Thread.java:829)
> {code}
> {code:java}
> Standard Output
> INFO [main] 2022-09-25 11:43:16,512 Reflections.java:219 - Reflections took
> 1221 ms to scan 8 urls, producing 1756 keys and 6922 values
> INFO [main] 2022-09-25 11:43:17,480 Reflections.java:219 - Reflections took
> 907 ms to scan 8 urls, producing 1756 keys and 6922 values
> INFO [main] 2022-09-25 11:43:17,573 YamlConfigurationLoader.java:104 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2022-09-25 11:43:17,574 YamlConfigurationLoader
> ...[truncated 35568 chars]...
> .apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest$MockCommitLogSegmentMgr.createSegment(CommitLogInitWithExceptionTest.java:106)
> at
> org.apache.cassandra.db.commitlog.AbstractCommitLogSegmentManager$AllocatorRunnable.run(AbstractCommitLogSegmentManager.java:155)
> at
> org.apache.cassandra.concurrent.InfiniteLoopExecutor.loop(InfiniteLoopExecutor.java:121)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
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-17955) Race condition on repair snapshots
[
https://issues.apache.org/jira/browse/CASSANDRA-17955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-17955:
--
Fix Version/s: 4.0.8
4.2
(was: 4.x)
(was: 4.0.x)
Since Version: 4.0
Source Control Link:
https://github.com/apache/cassandra/commit/35ef5b99577ef8b04b8d4b326154775f510ade42
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> 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.8, 4.1-rc, 4.2
>
> 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
[cassandra] branch trunk updated (507db24aad -> d45c4cbcbf)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 507db24aad Merge branch 'cassandra-4.1' into trunk add 35ef5b9957 Fix possible race condition on repair snapshots add 0e21007b4f Merge branch 'cassandra-4.0' into cassandra-4.1 new d45c4cbcbf Merge branch 'cassandra-4.1' into trunk 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: CHANGES.txt| 1 + .../db/repair/CassandraTableRepairManager.java | 26 +++--- .../cassandra/service/ActiveRepairService.java | 13 ++- 3 files changed, 26 insertions(+), 14 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.1 updated (dd53a609c6 -> 0e21007b4f)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from dd53a609c6 Add --resolve-ip option to nodetool gossipinfo add 35ef5b9957 Fix possible race condition on repair snapshots add 0e21007b4f Merge branch 'cassandra-4.0' into cassandra-4.1 No new revisions were added by this update. Summary of changes: CHANGES.txt| 1 + .../db/repair/CassandraTableRepairManager.java | 26 +++--- .../cassandra/service/ActiveRepairService.java | 13 ++- 3 files changed, 26 insertions(+), 14 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.0 updated (ac165325bc -> 35ef5b9957)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from ac165325bc Merge branch 'cassandra-3.11' into cassandra-4.0 add 35ef5b9957 Fix possible race condition on repair snapshots No new revisions were added by this update. Summary of changes: CHANGES.txt| 1 + .../db/repair/CassandraTableRepairManager.java | 27 ++ .../cassandra/service/ActiveRepairService.java | 15 ++-- 3 files changed, 27 insertions(+), 16 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.1' into trunk
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit d45c4cbcbf96afba8d9a2ad4550b8d47db86f648 Merge: 507db24aad 0e21007b4f Author: Stefan Miklosovic AuthorDate: Thu Oct 27 16:07:59 2022 +0200 Merge branch 'cassandra-4.1' into trunk CHANGES.txt| 1 + .../db/repair/CassandraTableRepairManager.java | 26 +++--- .../cassandra/service/ActiveRepairService.java | 13 ++- 3 files changed, 26 insertions(+), 14 deletions(-) diff --cc CHANGES.txt index a8819b354e,ee48fcfa4b..d3f6df4183 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -101,10 -46,6 +101,11 @@@ Merged from 4.1 * Revert removal of withBufferSizeInMB(int size) in CQLSSTableWriter.Builder class and deprecate it in favor of withBufferSizeInMiB(int size) (CASSANDRA-17675) * Remove expired snapshots of dropped tables after restart (CASSANDRA-17619) Merged from 4.0: ++ * Fix possible race condition on repair snapshots (CASSANDRA-17955) + * Fix ASM bytecode version inconsistency (CASSANDRA-17873) + * Remove empty cq4 files in log directory to not fail the startup of BinLog (CASSANDRA-17933) + * Fix multiple BufferPool bugs (CASSANDRA-16681) + * Fix StorageService.getNativeaddress handling of IPv6 addresses (CASSANDRA-17945) * Mitigate direct buffer memory OOM on replacements (CASSANDRA-17895) * Fix repair failure on assertion if two peers have overlapping mismatching ranges (CASSANDRA-17900) * Better handle null state in Gossip schema migration to avoid NPE (CASSANDRA-17864) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17773) Incorrect cassandra.logdir on Debian systems
[ https://issues.apache.org/jira/browse/CASSANDRA-17773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625147#comment-17625147 ] Claude Warren commented on CASSANDRA-17773: --- I have created a pull request as an example of how this could be made better. This is a work in progress and I am looking for comments. https://github.com/apache/cassandra/pull/1950 > Incorrect cassandra.logdir on Debian systems > > > Key: CASSANDRA-17773 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17773 > Project: Cassandra > Issue Type: Bug > Components: Packaging >Reporter: Eric Evans >Priority: Normal > Labels: lhf > Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x > > > The Debian packaging patches bin/cassandra to use /var/log/cassandra for > logs, it does so conditionally however, only if CASSANDRA_LOG_DIR is unset. > This occurs _after_ cassandra-env.sh is sourced though, which also sets > CASSANDRA_LOG_DIR if unset (to $CASSANDRA_HOME/logs). The result is that > -Dcassandra.lodir is set to /usr/share/cassandra/logs on Debian systems. -- 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-17955) Race condition on repair snapshots
[
https://issues.apache.org/jira/browse/CASSANDRA-17955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-17955:
--
Status: Review In Progress (was: Needs Committer)
> 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] [Updated] (CASSANDRA-17955) Race condition on repair snapshots
[
https://issues.apache.org/jira/browse/CASSANDRA-17955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-17955:
--
Status: Needs Committer (was: Patch Available)
> 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] [Updated] (CASSANDRA-17955) Race condition on repair snapshots
[
https://issues.apache.org/jira/browse/CASSANDRA-17955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Miklosovic updated CASSANDRA-17955:
--
Status: Ready to Commit (was: Review In Progress)
> 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] [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=17625113#comment-17625113
]
Stefan Miklosovic commented on CASSANDRA-17955:
---
As mentioned, I tried to run multiplexer on all repair tests, I can use only 20
runners and CI job timeouts after 1 hour so I tried to measure the maximum
amount of repeats over all repair tests. I think I run all repair unit tests
around 120 times and all dtests 20 times it went all fine. This is only the
build of trunk (1).
This patch is not introducing any new test nor it modifies any but I still
tried to run all repair tests in a loop to see if it is stable, which it seems
it is. Due to limited resources and time constraints I consider this kind of
testing enough (on top of regular and mandatory 6 jobs above, 2 per branch (8
and 11 pre-commit)
https://app.circleci.com/pipelines/github/instaclustr/cassandra/1498/workflows/e0f4e61a-cf3b-4ef7-a0c3-d02a25778bb8
> 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] [Commented] (CASSANDRA-17988) WEBSITE - Add a dedicated Events page
[ https://issues.apache.org/jira/browse/CASSANDRA-17988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625106#comment-17625106 ] Stefano Lottini commented on CASSANDRA-17988: - I replied to all points but one (to which I have not the answer tbh). > WEBSITE - Add a dedicated Events page > - > > Key: CASSANDRA-17988 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17988 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Stefano Lottini >Assignee: Stefano Lottini >Priority: Normal > Fix For: NA > > Attachments: c17988-03-events-v3.png, c17988-04-top_menu_option.png, > events-B-1-1.png, events-B-1.png, events-B-2-1.png, events-B-2.png, > 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] [Updated] (CASSANDRA-17934) Add --resolve-ip option on 'nodetool gossipinfo'
[ https://issues.apache.org/jira/browse/CASSANDRA-17934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17934: -- Fix Version/s: 4.2 (was: 4.x) Source Control Link: https://github.com/apache/cassandra/commit/dd53a609c692c12ffb94acf9fcf81343e35723e9 Resolution: Fixed Status: Resolved (was: Ready to Commit) > Add --resolve-ip option on 'nodetool gossipinfo' > > > Key: CASSANDRA-17934 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17934 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Paulo Motta >Assignee: Maxim Chanturiay >Priority: Normal > Labels: lhf > Fix For: 4.1-rc, 4.2 > > Time Spent: 10m > Remaining Estimate: 0h > > Give nodetool gossipinfo the option of either displaying IPs or hostnames for > the nodes in a ring. > Note: this option is already present for "nodetool status" and "nodetool ring" -- 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-17919) Capital P gets confused in the parser for a Duration in places where IDENT are needed
[
https://issues.apache.org/jira/browse/CASSANDRA-17919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625101#comment-17625101
]
Benjamin Lerer commented on CASSANDRA-17919:
@[~maximc] Thanks for working on this problem. :-)
The Duration type was introduced in 3.10 and the bug was there from the start.
You should probably start with the 3.11 branch. The merge should be relatively
simple.
> Capital P gets confused in the parser for a Duration in places where IDENT
> are needed
> -
>
> Key: CASSANDRA-17919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17919
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Syntax
>Reporter: David Capwell
>Assignee: Maxim Chanturiay
>Priority: Normal
> Fix For: 3.11.x, 4.0.x, 4.1.x
>
>
> This was found while adding Accord Transaction syntax into CQL and fuzz
> testing to validate all possible cases… in doing this the following was found
> {code}
> String query = "BEGIN TRANSACTION\n" +
>" LET P = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" LET row2 = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" SELECT v FROM " + keyspace + ".tbl WHERE k=?
> AND c=?;\n" +
>" IF P IS NULL AND row2.v = ? THEN\n" +
>"INSERT INTO " + keyspace + ".tbl (k, c, v)
> VALUES (?, ?, ?);\n" +
>" END IF\n" +
>"COMMIT TRANSACTION";
> {code}
> Fails with
> {code}
> SyntaxException: line 2:6 mismatched input 'P' expecting IDENT (BEGIN
> TRANSACTION LET [P]...)
> {code}
> The new LET syntax found this, but was able to reproduce in other cases
> {code}
> cqlsh:ks> CREATE TABLE P (k INT PRIMARY KEY);
> SyntaxException: line 1:13 no viable alternative at input 'P' (CREATE TABLE
> [P]...)
> cqlsh:ks>
> cqlsh:ks> CREATE TABLE p (k INT PRIMARY KEY);
> cqlsh:ks>
> {code}
--
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-17934) Add --resolve-ip option on 'nodetool gossipinfo'
[ https://issues.apache.org/jira/browse/CASSANDRA-17934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-17934: -- Status: Ready to Commit (was: Review In Progress) > Add --resolve-ip option on 'nodetool gossipinfo' > > > Key: CASSANDRA-17934 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17934 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Paulo Motta >Assignee: Maxim Chanturiay >Priority: Normal > Labels: lhf > Fix For: 4.1-rc, 4.x > > Time Spent: 10m > Remaining Estimate: 0h > > Give nodetool gossipinfo the option of either displaying IPs or hostnames for > the nodes in a ring. > Note: this option is already present for "nodetool status" and "nodetool ring" -- 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] branch trunk updated (230fe8e647 -> 507db24aad)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from 230fe8e647 Include Git SHA in --verbose flag for nodetool version add dd53a609c6 Add --resolve-ip option to nodetool gossipinfo new 507db24aad Merge branch 'cassandra-4.1' into trunk 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: CHANGES.txt| 1 + .../org/apache/cassandra/gms/FailureDetector.java | 21 +++-- .../apache/cassandra/gms/FailureDetectorMBean.java | 2 ++ .../cassandra/locator/InetAddressAndPort.java | 5 src/java/org/apache/cassandra/tools/NodeProbe.java | 10 ++- .../cassandra/tools/nodetool/GossipInfo.java | 6 +++- .../cassandra/locator/InetAddressAndPortTest.java | 35 ++ .../cassandra/tools/nodetool/GossipInfoTest.java | 31 +++ 8 files changed, 106 insertions(+), 5 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.1' into trunk
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 507db24aadd614c105d2ff916ffb3878ebb4f890 Merge: 230fe8e647 dd53a609c6 Author: Stefan Miklosovic AuthorDate: Thu Oct 27 11:19:47 2022 +0200 Merge branch 'cassandra-4.1' into trunk CHANGES.txt| 1 + .../org/apache/cassandra/gms/FailureDetector.java | 21 +++-- .../apache/cassandra/gms/FailureDetectorMBean.java | 2 ++ .../cassandra/locator/InetAddressAndPort.java | 5 src/java/org/apache/cassandra/tools/NodeProbe.java | 10 ++- .../cassandra/tools/nodetool/GossipInfo.java | 6 +++- .../cassandra/locator/InetAddressAndPortTest.java | 35 ++ .../cassandra/tools/nodetool/GossipInfoTest.java | 31 +++ 8 files changed, 106 insertions(+), 5 deletions(-) diff --cc CHANGES.txt index 5a4dcba477,092c6ea15b..a8819b354e --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,76 -1,21 +1,77 @@@ -4.1-beta2 +4.2 + * Include Git SHA in --verbose flag for nodetool version (CASSANDRA-17753) + * Update Byteman to 4.0.20 and Jacoco to 0.8.8 (CASSANDRA-16413) + * Add memtable option among possible tab completions for a table (CASSANDRA-17982) + * Adds a trie-based memtable implementation (CASSANDRA-17240) + * Further improves precision of memtable heap tracking (CASSANDRA-17240) + * Fix formatting of metrics documentation (CASSANDRA-17961) + * Keep sstable level when streaming for decommission and move (CASSANDRA-17969) + * Add Unavailables metric for CASWrite in the docs (CASSANDRA-16357) + * Make Cassandra logs able to be viewed in the virtual table system_views.system_logs (CASSANDRA-17946) + * IllegalArgumentException in Gossiper#order due to concurrent mutations to elements being applied (CASSANDRA-17908) + * Include estimated active compaction remaining write size when starting a new compaction (CASSANDRA-17931) + * Mixed mode support for internode authentication during TLS upgrades (CASSANDRA-17923) + * Revert Mockito downgrade from CASSANDRA-17750 (CASSANDRA-17496) + * Add --older-than and --older-than-timestamp options for nodetool clearsnapshots (CASSANDRA-16860) + * Fix "open RT bound as its last item" exception (CASSANDRA-17810) + * Fix leak of non-standard Java types in JMX MBeans `org.apache.cassandra.db:type=StorageService` + and `org.apache.cassandra.db:type=RepairService` as clients using JMX cannot handle them. More details in NEWS.txt (CASSANDRA-17668) + * Deprecate Throwables.propagate usage (CASSANDRA-14218) + * Allow disabling hotness persistence for high sstable counts (CASSANDRA-17868) + * Prevent NullPointerException when changing neverPurgeTombstones from true to false (CASSANDRA-17897) + * Add metrics around storage usage and compression (CASSANDRA-17898) + * Remove usage of deprecated javax certificate classes (CASSANDRA-17867) + * Make sure preview repairs don't optimise streams unless configured to (CASSANDRA-17865) + * Optionally avoid hint transfer during decommission (CASSANDRA-17808) + * Make disabling auto snapshot on selected tables possible (CASSANDRA-10383) + * Introduce compaction priorities to prevent upgrade compaction inability to finish (CASSANDRA-17851) + * Prevent a user from manually removing ephemeral snapshots (CASSANDRA-17757) + * Remove dependency on Maven Ant Tasks (CASSANDRA-17750) + * Update ASM(9.1 to 9.3), Mockito(1.10.10 to 1.12.13) and ByteBuddy(3.2.4 to 4.7.0) (CASSANDRA-17835) + * Add the ability for operators to loosen the definition of "empty" for edge cases (CASSANDRA-17842) + * Fix potential out of range exception on column index downsampling (CASSANDRA-17839) + * Introduce target directory to vtable output for sstable_tasks and for compactionstats (CASSANDRA-13010) + * Read/Write/Truncate throw RequestFailure in a race condition with callback timeouts, should return Timeout instead (CASSANDRA-17828) + * Add ability to log load profiles at fixed intervals (CASSANDRA-17821) + * Protect against Gossip backing up due to a quarantined endpoint without version information (CASSANDRA-17830) + * NPE in org.apache.cassandra.cql3.Attributes.getTimeToLive (CASSANDRA-17822) + * Add guardrail for column size (CASSANDRA-17151) + * When doing a host replacement, we need to check that the node is a live node before failing with "Cannot replace a live node..." (CASSANDRA-17805) + * Add support to generate a One-Shot heap dump on unhandled exceptions (CASSANDRA-17795) + * Rate-limit new client connection auth setup to avoid overwhelming bcrypt (CASSANDRA-17812) + * DataOutputBuffer#scratchBuffer can use off-heap or on-heap memory as a means to control memory allocations (CASSANDRA-16471) + * Add ability to read the TTLs and write times of the elements of a collection and/or UDT (CASSANDRA-8877) + * Removed Python < 2.7
[jira] [Updated] (CASSANDRA-17919) Capital P gets confused in the parser for a Duration in places where IDENT are needed
[
https://issues.apache.org/jira/browse/CASSANDRA-17919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-17919:
---
Fix Version/s: 3.11.x
4.0.x
4.1.x
Since Version: 3.10
> Capital P gets confused in the parser for a Duration in places where IDENT
> are needed
> -
>
> Key: CASSANDRA-17919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17919
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Syntax
>Reporter: David Capwell
>Assignee: Maxim Chanturiay
>Priority: Normal
> Fix For: 3.11.x, 4.0.x, 4.1.x
>
>
> This was found while adding Accord Transaction syntax into CQL and fuzz
> testing to validate all possible cases… in doing this the following was found
> {code}
> String query = "BEGIN TRANSACTION\n" +
>" LET P = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" LET row2 = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" SELECT v FROM " + keyspace + ".tbl WHERE k=?
> AND c=?;\n" +
>" IF P IS NULL AND row2.v = ? THEN\n" +
>"INSERT INTO " + keyspace + ".tbl (k, c, v)
> VALUES (?, ?, ?);\n" +
>" END IF\n" +
>"COMMIT TRANSACTION";
> {code}
> Fails with
> {code}
> SyntaxException: line 2:6 mismatched input 'P' expecting IDENT (BEGIN
> TRANSACTION LET [P]...)
> {code}
> The new LET syntax found this, but was able to reproduce in other cases
> {code}
> cqlsh:ks> CREATE TABLE P (k INT PRIMARY KEY);
> SyntaxException: line 1:13 no viable alternative at input 'P' (CREATE TABLE
> [P]...)
> cqlsh:ks>
> cqlsh:ks> CREATE TABLE p (k INT PRIMARY KEY);
> cqlsh:ks>
> {code}
--
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] branch cassandra-4.1 updated (50dc696198 -> dd53a609c6)
This is an automated email from the ASF dual-hosted git repository. smiklosovic pushed a change to branch cassandra-4.1 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 50dc696198 Merge branch 'cassandra-4.0' into cassandra-4.1 add dd53a609c6 Add --resolve-ip option to nodetool gossipinfo No new revisions were added by this update. Summary of changes: CHANGES.txt| 1 + .../org/apache/cassandra/gms/FailureDetector.java | 21 +++-- .../apache/cassandra/gms/FailureDetectorMBean.java | 2 ++ .../cassandra/locator/InetAddressAndPort.java | 5 src/java/org/apache/cassandra/tools/NodeProbe.java | 10 ++- .../cassandra/tools/nodetool/GossipInfo.java | 6 +++- .../cassandra/locator/InetAddressAndPortTest.java | 35 ++ .../cassandra/tools/nodetool/GossipInfoTest.java | 31 +++ 8 files changed, 106 insertions(+), 5 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17934) Add --resolve-ip option on 'nodetool gossipinfo'
[ https://issues.apache.org/jira/browse/CASSANDRA-17934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625095#comment-17625095 ] Stefan Miklosovic commented on CASSANDRA-17934: --- trunk https://app.circleci.com/pipelines/github/instaclustr/cassandra/1499/workflows/1083b5cd-07e0-45f8-818b-7e263757d6a1 > Add --resolve-ip option on 'nodetool gossipinfo' > > > Key: CASSANDRA-17934 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17934 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Paulo Motta >Assignee: Maxim Chanturiay >Priority: Normal > Labels: lhf > Fix For: 4.1-rc, 4.x > > Time Spent: 10m > Remaining Estimate: 0h > > Give nodetool gossipinfo the option of either displaying IPs or hostnames for > the nodes in a ring. > Note: this option is already present for "nodetool status" and "nodetool ring" -- 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-17997) Improve git branch handling for CircleCI generate.sh
[ https://issues.apache.org/jira/browse/CASSANDRA-17997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625085#comment-17625085 ] Derek Chen-Becker commented on CASSANDRA-17997: --- CASSANDRA-17939 is the original ticket for using git to determine changed tests > Improve git branch handling for CircleCI generate.sh > > > Key: CASSANDRA-17997 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17997 > Project: Cassandra > Issue Type: Improvement > Components: CI >Reporter: Derek Chen-Becker >Assignee: Derek Chen-Becker >Priority: Normal > > The generate.sh script assumes a base git branch that is local and named > after the official repo branch (e.g. `cassandra-3.11`). This may not be a > local branch if the developer has recently cloned the repo and is creating a > work branch, and will lead to the git commands in generate.sh failing: > > ``` > fatal: ambiguous argument 'cassandra-3.11...HEAD': unknown revision or path > not in the working tree. > Use '--' to separate paths from revisions, like this: > 'git [...] -- [...]' > ``` > We should be able to make some sanity checks to better guide or warn the > developer if things aren't set up properly to check against git. -- 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-17997) Improve git branch handling for CircleCI generate.sh
[ https://issues.apache.org/jira/browse/CASSANDRA-17997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625083#comment-17625083 ] Derek Chen-Becker commented on CASSANDRA-17997: --- That was actually my suggestion when I discussed this with [~e.dimitrova] yesterday. That should be a pretty simple check, and easy to add the logic. I agree that we should only consider the ASF remote as canonical and bail out if the remotes only contain personal forks. > Improve git branch handling for CircleCI generate.sh > > > Key: CASSANDRA-17997 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17997 > Project: Cassandra > Issue Type: Improvement > Components: CI >Reporter: Derek Chen-Becker >Assignee: Derek Chen-Becker >Priority: Normal > > The generate.sh script assumes a base git branch that is local and named > after the official repo branch (e.g. `cassandra-3.11`). This may not be a > local branch if the developer has recently cloned the repo and is creating a > work branch, and will lead to the git commands in generate.sh failing: > > ``` > fatal: ambiguous argument 'cassandra-3.11...HEAD': unknown revision or path > not in the working tree. > Use '--' to separate paths from revisions, like this: > 'git [...] -- [...]' > ``` > We should be able to make some sanity checks to better guide or warn the > developer if things aren't set up properly to check against git. -- 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-17988) WEBSITE - Add a dedicated Events page
[ https://issues.apache.org/jira/browse/CASSANDRA-17988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625075#comment-17625075 ] Josh McKenzie commented on CASSANDRA-17988: --- Left a few comments / questions on the PR. >From an aesthetic perspective looks good to me (though I'm probably the last >person who's opinion on aesthetics you should seek ;) ) > WEBSITE - Add a dedicated Events page > - > > Key: CASSANDRA-17988 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17988 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Stefano Lottini >Assignee: Stefano Lottini >Priority: Normal > Fix For: NA > > Attachments: c17988-03-events-v3.png, c17988-04-top_menu_option.png, > events-B-1-1.png, events-B-1.png, events-B-2-1.png, events-B-2.png, > 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] [Comment Edited] (CASSANDRA-17988) WEBSITE - Add a dedicated Events page
[ https://issues.apache.org/jira/browse/CASSANDRA-17988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17624771#comment-17624771 ] Stefano Lottini edited comment on CASSANDRA-17988 at 10/27/22 12:27 PM: As it turned out, I managed to make the changes (and further adjustments). The PR is now complete for review. Quoting from the last commit: * larger cards (2 per row at most), with square bigger image * adjusted in-card spacing accordingly * added "Cassandra Days" blurb * mouse pointer on card is now 'default' * added Summit 2023 banner at top of page !events-B-1.png|width=360! !events-B-2-1.png|width=360! was (Author: stefano_lottini): As it turned out, I managed to make the changes (and further adjustments). The PR is now complete for review. Quoting from the last commit: * larger cards (2 per row at most), with square bigger image * adjusted in-card spacing accordingly * added "Cassandra Days" blurb * mouse pointer on card is now 'default' * added Summit 2023 banner at top of page !events-B-1.png!!events-B-2-1.png! > WEBSITE - Add a dedicated Events page > - > > Key: CASSANDRA-17988 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17988 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Stefano Lottini >Assignee: Stefano Lottini >Priority: Normal > Fix For: NA > > Attachments: c17988-03-events-v3.png, c17988-04-top_menu_option.png, > events-B-1-1.png, events-B-1.png, events-B-2-1.png, events-B-2.png, > 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] [Comment Edited] (CASSANDRA-17997) Improve git branch handling for CircleCI generate.sh
[
https://issues.apache.org/jira/browse/CASSANDRA-17997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625045#comment-17625045
]
Andres de la Peña edited comment on CASSANDRA-17997 at 10/27/22 11:20 AM:
--
I guess the default for {{BASE_BRANCH}} could also be a bit more clever. If
there isn't a -b option and the local base branch doesn't exist, we could look
into the list of remotes to see if there is a remote for the ASF repo. In that
case, we could use that remote in {{BASE_BRANCH}}. For example,
{{BASE_BRANCH=apache/cassandra-3.11}}, or {{BASE_BRANCH=ASF/cassandra-3.11}},
or however the remote has been named by the user. If there isn't such remote,
nor a local base branch, nor a -b option, then we would graciously fail asking
to either add the remote or use -b option. wdyt?
What I wouldn't do however is trying to get the base branch from the user's
private remote fork. If the project hasn't been recently forked, it is likely
that the remote base branch on the fork is very outdated.
was (Author: adelapena):
I guess the default for {{BASE_BRANCH}} could also be a bit more clever. If
there isn't a -b option and the local base branch doesn't exist, we could look
into the list of remotes to see if there is a remote for the ASF repo. In that
case, we could use that remote in {{BASE_BRANCH}}. For example,
{{BASE_BRANCH=apache/cassandra-3.11}}, or {{BASE_BRANCH=ASF/cassandra-3.11}},
or however the remote has been named by the user. If there isn't such remote,
nor a local base branch, nor a -b option, then we would gracious fail asking to
either add the remote or use -b option. wdyt?
What I wouldn't do however is trying to get the base branch from the user's
private remote fork. If the project hasn't been recently forked, it is likely
that the remote base branch on the fork is very outdated.
> Improve git branch handling for CircleCI generate.sh
>
>
> Key: CASSANDRA-17997
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17997
> Project: Cassandra
> Issue Type: Improvement
> Components: CI
>Reporter: Derek Chen-Becker
>Assignee: Derek Chen-Becker
>Priority: Normal
>
> The generate.sh script assumes a base git branch that is local and named
> after the official repo branch (e.g. `cassandra-3.11`). This may not be a
> local branch if the developer has recently cloned the repo and is creating a
> work branch, and will lead to the git commands in generate.sh failing:
>
> ```
> fatal: ambiguous argument 'cassandra-3.11...HEAD': unknown revision or path
> not in the working tree.
> Use '--' to separate paths from revisions, like this:
> 'git [...] -- [...]'
> ```
> We should be able to make some sanity checks to better guide or warn the
> developer if things aren't set up properly to check against git.
--
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-17997) Improve git branch handling for CircleCI generate.sh
[
https://issues.apache.org/jira/browse/CASSANDRA-17997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625045#comment-17625045
]
Andres de la Peña commented on CASSANDRA-17997:
---
I guess the default for {{BASE_BRANCH}} could also be a bit more clever. If
there isn't a -b option and the local base branch doesn't exist, we could look
into the list of remotes to see if there is a remote for the ASF repo. In that
case, we could use that remote in {{BASE_BRANCH}}. For example,
{{BASE_BRANCH=apache/cassandra-3.11}}, or {{BASE_BRANCH=ASF/cassandra-3.11}},
or however the remote has been named by the user. If there isn't such remote,
nor a local base branch, nor a -b option, then we would gracious fail asking to
either add the remote or use -b option. wdyt?
What I wouldn't do however is trying to get the base branch from the user's
private remote fork. If the project hasn't been recently forked, it is likely
that the remote base branch on the fork is very outdated.
> Improve git branch handling for CircleCI generate.sh
>
>
> Key: CASSANDRA-17997
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17997
> Project: Cassandra
> Issue Type: Improvement
> Components: CI
>Reporter: Derek Chen-Becker
>Assignee: Derek Chen-Becker
>Priority: Normal
>
> The generate.sh script assumes a base git branch that is local and named
> after the official repo branch (e.g. `cassandra-3.11`). This may not be a
> local branch if the developer has recently cloned the repo and is creating a
> work branch, and will lead to the git commands in generate.sh failing:
>
> ```
> fatal: ambiguous argument 'cassandra-3.11...HEAD': unknown revision or path
> not in the working tree.
> Use '--' to separate paths from revisions, like this:
> 'git [...] -- [...]'
> ```
> We should be able to make some sanity checks to better guide or warn the
> developer if things aren't set up properly to check against git.
--
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-17912) Fix CircleCI config for running Python upgrade tests on 3.0 and 3.11
[ https://issues.apache.org/jira/browse/CASSANDRA-17912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625034#comment-17625034 ] Andres de la Peña edited comment on CASSANDRA-17912 at 10/27/22 11:06 AM: -- [~e.dimitrova] thanks for waiting on CASSANDRA-17987. Indeed it's easier to rebase the smaller patch over bigger one. It's very kind of you to wait for that one, please let me know if I can help with the rebase of this one :) was (Author: adelapena): [~e.dimitrova] thanks for that for waiting on CASSANDRA-17987. Indeed it's easier to rebase the smaller patch over bigger one. It's very kind of you to wait for that one, please let me know if I can help with the rebase of this one :) > Fix CircleCI config for running Python upgrade tests on 3.0 and 3.11 > > > Key: CASSANDRA-17912 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17912 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 3.0.x, 3.11.x > > > It was noticed that Circle CI pushes to run irrelevant for 3.0 and 3.11 > Python upgrade tests. Those are properly skipped in Jenkins. > Example runs: > [CircleCI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1931/workflows/39ef5261-a6bf-4e77-a412-e750e322a231/jobs/15293] > - 3.0 run > [Jenkins|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1944/] > - while typing this I actually noticed [one > test|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1944/testReport/junit/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_parallel_upgrade_with_internode_ssl/] > only looking suspicious in Jenkins as it ends the upgrade in 3.11 when we > test 3.0... > This is good to be fixed for two reasons - reduce the noise so we do not miss > legit failures and we should not spend resources to try to run those tests. -- 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-17912) Fix CircleCI config for running Python upgrade tests on 3.0 and 3.11
[ https://issues.apache.org/jira/browse/CASSANDRA-17912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625034#comment-17625034 ] Andres de la Peña commented on CASSANDRA-17912: --- [~e.dimitrova] thanks for that for waiting on CASSANDRA-17987. Indeed it's easier to rebase the smaller patch over bigger one. It's very kind of you to wait for that one, please let me know if I can help with the rebase of this one :) > Fix CircleCI config for running Python upgrade tests on 3.0 and 3.11 > > > Key: CASSANDRA-17912 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17912 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 3.0.x, 3.11.x > > > It was noticed that Circle CI pushes to run irrelevant for 3.0 and 3.11 > Python upgrade tests. Those are properly skipped in Jenkins. > Example runs: > [CircleCI|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1931/workflows/39ef5261-a6bf-4e77-a412-e750e322a231/jobs/15293] > - 3.0 run > [Jenkins|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1944/] > - while typing this I actually noticed [one > test|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1944/testReport/junit/dtest-upgrade.upgrade_tests.upgrade_through_versions_test/TestProtoV3Upgrade_AllVersions_RandomPartitioner_EndsAt_3_11_X_HEAD/test_parallel_upgrade_with_internode_ssl/] > only looking suspicious in Jenkins as it ends the upgrade in 3.11 when we > test 3.0... > This is good to be fixed for two reasons - reduce the noise so we do not miss > legit failures and we should not spend resources to try to run those tests. -- 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-17988) WEBSITE - Add a dedicated Events page
[
https://issues.apache.org/jira/browse/CASSANDRA-17988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625024#comment-17625024
]
Erick Ramirez edited comment on CASSANDRA-17988 at 10/27/22 10:59 AM:
--
I've suggested some changes to the wording of the introduction to make them
newcomer-friendly and discussed with Stefano. The changes have now been
included in the PR.
Updated patch:
||Branch||PR||
|{{trunk}}|[#185|https://github.com/apache/cassandra-website/pull/185]|
!c17988-04-top_menu_option.png|width=300!
!c17988-03-events-v3.png|width=300!
was (Author: JIRAUSER285101):
I've suggested some changes to the wording of the introduction to make them
newcomer-friendly and discussed with Stefano. The changes have now been
included in the PR.
!c17988-04-top_menu_option.png|width=300!
!c17988-03-events-v3.png|width=300!
> WEBSITE - Add a dedicated Events page
> -
>
> Key: CASSANDRA-17988
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17988
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Stefano Lottini
>Assignee: Stefano Lottini
>Priority: Normal
> Fix For: NA
>
> Attachments: c17988-03-events-v3.png, c17988-04-top_menu_option.png,
> events-B-1-1.png, events-B-1.png, events-B-2-1.png, events-B-2.png,
> 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] [Comment Edited] (CASSANDRA-17988) WEBSITE - Add a dedicated Events page
[ https://issues.apache.org/jira/browse/CASSANDRA-17988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625024#comment-17625024 ] Erick Ramirez edited comment on CASSANDRA-17988 at 10/27/22 10:52 AM: -- I've suggested some changes to the wording of the introduction to make them newcomer-friendly and discussed with Stefano. The changes have now been included in the PR. !c17988-04-top_menu_option.png|width=300! !c17988-03-events-v3.png|width=300! was (Author: JIRAUSER285101): I've suggested some changes to the wording of the introduction to make them newcomer-friendly and discussed with Stefano. The changes have now been included in the PR. !c17988-03-events-v3.png|width=300! !c17988-04-top_menu_option.png|width=300! > WEBSITE - Add a dedicated Events page > - > > Key: CASSANDRA-17988 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17988 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Stefano Lottini >Assignee: Stefano Lottini >Priority: Normal > Fix For: NA > > Attachments: c17988-03-events-v3.png, c17988-04-top_menu_option.png, > events-B-1-1.png, events-B-1.png, events-B-2-1.png, events-B-2.png, > 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] [Updated] (CASSANDRA-17988) WEBSITE - Add a dedicated Events page
[ https://issues.apache.org/jira/browse/CASSANDRA-17988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17988: -- Attachment: c17988-03-events-v3.png > WEBSITE - Add a dedicated Events page > - > > Key: CASSANDRA-17988 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17988 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Stefano Lottini >Assignee: Stefano Lottini >Priority: Normal > Fix For: NA > > Attachments: c17988-03-events-v3.png, c17988-04-top_menu_option.png, > events-B-1-1.png, events-B-1.png, events-B-2-1.png, events-B-2.png, > 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-17988) WEBSITE - Add a dedicated Events page
[ https://issues.apache.org/jira/browse/CASSANDRA-17988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625024#comment-17625024 ] Erick Ramirez commented on CASSANDRA-17988: --- I've suggested some changes to the wording of the introduction to make them newcomer-friendly and discussed with Stefano. The changes have now been included in the PR. !c17988-03-events-v3.png|width=300! !c17988-04-top_menu_option.png|width=300! > WEBSITE - Add a dedicated Events page > - > > Key: CASSANDRA-17988 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17988 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Stefano Lottini >Assignee: Stefano Lottini >Priority: Normal > Fix For: NA > > Attachments: c17988-03-events-v3.png, c17988-04-top_menu_option.png, > events-B-1-1.png, events-B-1.png, events-B-2-1.png, events-B-2.png, > 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] [Updated] (CASSANDRA-17988) WEBSITE - Add a dedicated Events page
[ https://issues.apache.org/jira/browse/CASSANDRA-17988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17988: -- Attachment: (was: c17988-03-events-v3.png) > WEBSITE - Add a dedicated Events page > - > > Key: CASSANDRA-17988 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17988 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Stefano Lottini >Assignee: Stefano Lottini >Priority: Normal > Fix For: NA > > Attachments: c17988-04-top_menu_option.png, events-B-1-1.png, > events-B-1.png, events-B-2-1.png, events-B-2.png, 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-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=17625023#comment-17625023
]
Andres de la Peña commented on CASSANDRA-17987:
---
[~e.dimitrova]'s eagle eye has detected that the repeated runs for some
specialized tests aren't actually running the tests. That's because of a
mistake while initializating the {{target}} var in the {{run_repeated_utests}}
command. That makes the Ant targets that are not of the form "testsome" receive
qualified class names, while they are expecting short class names. So the job
doesn't find the tests.
Also, the command was also ignoring the {{testtag}} attribute used by the Ant's
test macro to group the test results and logs. That produces problems while
collecting the run artifacts.
These bugs were introduced during CASSANDRA-17939, and I think we should fix
them here to get the specialized unit tests ready. I have added fixes for both
things, also including 3.0:
||Patch||CI||
|[3.0|https://github.com/adelapena/cassandra/tree/17987-3.0]|[low|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-3.0]
[mid|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-3.0-mid]
[high|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-3.0-high]
[multiplexer|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-3.0-multiplexer]|
|[3.11|https://github.com/adelapena/cassandra/tree/17987-3.11]|[low|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-3.11]
[mid|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-3.11-mid]
[high|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-3.11-high]
[multiplexer|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-3.11-multiplexer]|
|[4.0|https://github.com/adelapena/cassandra/tree/17987-4.0]|[low|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-4.0]
[mid|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-4.0-mid]
[high|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-4.0-high]
[multiplexer|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-4.0-multiplexer]|
|[4.1|https://github.com/adelapena/cassandra/tree/17987-4.1]|[low|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-4.1]
[mid|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-4.1-mid]
[high|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-4.1-high]
[multiplexer|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-4.1-multiplexer]|
|[trunk|https://github.com/apache/cassandra/pull/1947]|[low|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-trunk]
[mid|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-trunk-mid]
[high|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-trunk-high]
[multiplexer|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-trunk-multiplexer]|
> 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-17988) WEBSITE - Add a dedicated Events page
[ https://issues.apache.org/jira/browse/CASSANDRA-17988?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erick Ramirez updated CASSANDRA-17988: -- Attachment: c17988-04-top_menu_option.png c17988-03-events-v3.png > WEBSITE - Add a dedicated Events page > - > > Key: CASSANDRA-17988 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17988 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Stefano Lottini >Assignee: Stefano Lottini >Priority: Normal > Fix For: NA > > Attachments: c17988-03-events-v3.png, c17988-04-top_menu_option.png, > events-B-1-1.png, events-B-1.png, events-B-2-1.png, events-B-2.png, > 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-17928) Test Failure: org.apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest.testCommitLogInitWithException-compression
[
https://issues.apache.org/jira/browse/CASSANDRA-17928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17625008#comment-17625008
]
Berenguer Blasi commented on CASSANDRA-17928:
-
Well
[this|https://github.com/apache/cassandra/compare/trunk...bereng:cassandra:CASSANDRA-17928-4.1]
passes
[10K|https://app.circleci.com/pipelines/github/bereng/cassandra/801/workflows/67a01d5c-5000-485a-9499-30565122afa1].
If we add the previous 10K runs that is 20K runs without a NPE.
The problem is that the static init on exit and the Thread.join should both
warranty a happens-before with a memory barrier that should make all properly
visible across threads. The only exception would be another class loader
triggering the static init a second time. So I still don't understand who is
shuffling things under our feet for the executor to be null.
> Test Failure:
> org.apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest.testCommitLogInitWithException-compression
> -
>
> Key: CASSANDRA-17928
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17928
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Josh McKenzie
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.1-rc
>
>
> [Link|https://ci-cassandra.apache.org/job/Cassandra-4.1/169/testReport/org.apache.cassandra.db.commitlog/CommitLogInitWithExceptionTest/testCommitLogInitWithException_compression/]
> Failed 1 times in the last 14 runs. Flakiness: 7%, Stability: 92%
> Stacktrace
> {code:java}
> java.lang.NullPointerException
> at
> org.apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest.testCommitLogInitWithException(CommitLogInitWithExceptionTest.java:93)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at java.base/java.lang.Thread.run(Thread.java:829)
> {code}
> {code:java}
> Standard Output
> INFO [main] 2022-09-25 11:43:16,512 Reflections.java:219 - Reflections took
> 1221 ms to scan 8 urls, producing 1756 keys and 6922 values
> INFO [main] 2022-09-25 11:43:17,480 Reflections.java:219 - Reflections took
> 907 ms to scan 8 urls, producing 1756 keys and 6922 values
> INFO [main] 2022-09-25 11:43:17,573 YamlConfigurationLoader.java:104 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2022-09-25 11:43:17,574 YamlConfigurationLoader
> ...[truncated 35568 chars]...
> .apache.cassandra.db.commitlog.CommitLogInitWithExceptionTest$MockCommitLogSegmentMgr.createSegment(CommitLogInitWithExceptionTest.java:106)
> at
> org.apache.cassandra.db.commitlog.AbstractCommitLogSegmentManager$AllocatorRunnable.run(AbstractCommitLogSegmentManager.java:155)
> at
> org.apache.cassandra.concurrent.InfiniteLoopExecutor.loop(InfiniteLoopExecutor.java:121)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.lang.Thread.run(Thread.java:748)
> {code}
--
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=17624990#comment-17624990 ] Berenguer Blasi commented on CASSANDRA-17987: - Yep good. Just wanted to confirm they hadn't fell through the cracks > 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] [Assigned] (CASSANDRA-17919) Capital P gets confused in the parser for a Duration in places where IDENT are needed
[
https://issues.apache.org/jira/browse/CASSANDRA-17919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Chanturiay reassigned CASSANDRA-17919:
Assignee: Maxim Chanturiay
> Capital P gets confused in the parser for a Duration in places where IDENT
> are needed
> -
>
> Key: CASSANDRA-17919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17919
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Syntax
>Reporter: David Capwell
>Assignee: Maxim Chanturiay
>Priority: Normal
>
> This was found while adding Accord Transaction syntax into CQL and fuzz
> testing to validate all possible cases… in doing this the following was found
> {code}
> String query = "BEGIN TRANSACTION\n" +
>" LET P = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" LET row2 = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" SELECT v FROM " + keyspace + ".tbl WHERE k=?
> AND c=?;\n" +
>" IF P IS NULL AND row2.v = ? THEN\n" +
>"INSERT INTO " + keyspace + ".tbl (k, c, v)
> VALUES (?, ?, ?);\n" +
>" END IF\n" +
>"COMMIT TRANSACTION";
> {code}
> Fails with
> {code}
> SyntaxException: line 2:6 mismatched input 'P' expecting IDENT (BEGIN
> TRANSACTION LET [P]...)
> {code}
> The new LET syntax found this, but was able to reproduce in other cases
> {code}
> cqlsh:ks> CREATE TABLE P (k INT PRIMARY KEY);
> SyntaxException: line 1:13 no viable alternative at input 'P' (CREATE TABLE
> [P]...)
> cqlsh:ks>
> cqlsh:ks> CREATE TABLE p (k INT PRIMARY KEY);
> cqlsh:ks>
> {code}
--
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-17919) Capital P gets confused in the parser for a Duration in places where IDENT are needed
[
https://issues.apache.org/jira/browse/CASSANDRA-17919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17624988#comment-17624988
]
Maxim Chanturiay commented on CASSANDRA-17919:
--
[~dcapwell] , [~blerer] Hello! I'd like to work on the issue.
I will assign myself - so please remove me if it is already taken. I'll watch
the ticket updates' mail.
+What has been done so far?+
I've checked out a branch from Cassandra 4.1, created a couple of unit tests
that fail because of "DROP TABLE P" and "CREATE TABLE P" with the same error as
in the bug report. In short - there is a functioning local dev environment to
test out code changes.
I'd like to go with [~blerer]'s solution.
I've tried other options, like placing token IDENT above DURATION or trying to
identify P as duration only when it's enclosed by parentheses ().
None of them worked either because of the ambiguity where both IDENT and
DURATION contain a letter and optional digit or too complicated code wise.
And given the thousands of code lines in parser logic - more complication is
the last thing that is needed :D
> Capital P gets confused in the parser for a Duration in places where IDENT
> are needed
> -
>
> Key: CASSANDRA-17919
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17919
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Syntax
>Reporter: David Capwell
>Priority: Normal
>
> This was found while adding Accord Transaction syntax into CQL and fuzz
> testing to validate all possible cases… in doing this the following was found
> {code}
> String query = "BEGIN TRANSACTION\n" +
>" LET P = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" LET row2 = (SELECT v FROM " + keyspace + ".tbl
> WHERE k=? AND c=?);\n" +
>" SELECT v FROM " + keyspace + ".tbl WHERE k=?
> AND c=?;\n" +
>" IF P IS NULL AND row2.v = ? THEN\n" +
>"INSERT INTO " + keyspace + ".tbl (k, c, v)
> VALUES (?, ?, ?);\n" +
>" END IF\n" +
>"COMMIT TRANSACTION";
> {code}
> Fails with
> {code}
> SyntaxException: line 2:6 mismatched input 'P' expecting IDENT (BEGIN
> TRANSACTION LET [P]...)
> {code}
> The new LET syntax found this, but was able to reproduce in other cases
> {code}
> cqlsh:ks> CREATE TABLE P (k INT PRIMARY KEY);
> SyntaxException: line 1:13 no viable alternative at input 'P' (CREATE TABLE
> [P]...)
> cqlsh:ks>
> cqlsh:ks> CREATE TABLE p (k INT PRIMARY KEY);
> cqlsh:ks>
> {code}
--
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=17624984#comment-17624984
]
Andres de la Peña commented on CASSANDRA-17987:
---
Ah, Python dtests. I haven't specified anything on {{REPEATED_DTESTS}} nor
{{REPEATED_UPGRADE_DTESTS}} because this is about unit tests and the command
for repeating Ant targets. Python dtests use other command and don't have
automatic detection.
> 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=17624972#comment-17624972 ] Berenguer Blasi edited comment on CASSANDRA-17987 at 10/27/22 9:12 AM: --- On the trunk [multiplexer|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-trunk-multiplexer] separate tests i.e. You seem to have '_repeat' variations for everything else except upgrade dtests. If that is a consequence of the deletion of the job bc no upgrade tests are present then that is ok. was (Author: bereng): On the trunk [multiplexer|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-trunk-multiplexer] separate tests i.e. You seem to have '_repeat' variation for everything else except upgrade dtests. If that is a consequence of the deletion of the job bc no upgrade tests are present then that is ok. > 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=17624972#comment-17624972 ] Berenguer Blasi commented on CASSANDRA-17987: - On the trunk [multiplexer|https://app.circleci.com/pipelines/github/adelapena/cassandra?branch=17987-trunk-multiplexer] separate tests i.e. You seem to have '_repeat' variation for everything else except upgrade dtests. If that is a consequence of the deletion of the job bc no upgrade tests are present then that is ok. > 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=17624963#comment-17624963
]
Andres de la Peña edited comment on CASSANDRA-17987 at 10/27/22 8:56 AM:
-
[~bereng] In what branch are they missing? Note that the {{generate.sh}} script
deletes the jobs without tests to be repeated,
[here|https://github.com/apache/cassandra/blob/trunk/.circleci/generate.sh#L283-L294],
and there aren't upgrade tests for j11.
was (Author: adelapena):
[~bereng] In what branch are they missing? Note that the {{generate.sh}}
scripts deletes the repeated jobs without tests to be repeated,
[here|https://github.com/apache/cassandra/blob/trunk/.circleci/generate.sh#L283-L294],
and there aren't upgrade tests for j11.
> 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=17624963#comment-17624963
]
Andres de la Peña commented on CASSANDRA-17987:
---
[~bereng] In what branch are they missing? Note that the {{generate.sh}}
scripts deletes the repeated jobs without tests to be repeated,
[here|https://github.com/apache/cassandra/blob/trunk/.circleci/generate.sh#L283-L294],
and there aren't upgrade tests for j11.
> 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-17992) Upgrade Netty on 4.x(current trunk)
[
https://issues.apache.org/jira/browse/CASSANDRA-17992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17624956#comment-17624956
]
Benedict Elliott Smith commented on CASSANDRA-17992:
{{java.lang.ClassCastException: class
org.apache.cassandra.utils.memory.BufferPool$Chunk cannot be cast to class
sun.nio.ch.DirectBuffer}}
Uh oh. I guess I must have seen this before myself but not looked closely. This
looks more pernicious to me, since it’s a {{BufferPool$Chunk}}. Either the JDK
or Netty are probably unhappy at our use of the attachment field in
{{DirectByteBuffer}}. Looking briefly at the JDK, it is unlikely to be to blame
as there is a JNI constructor for {{DirectByteBuffer}} that accepts a plain
object to hold onto, I guess to ensure that whatever native memory pointer the
buffer references is not collected (and freed by a finalizer/reference queue).
So we're not doing anything unacceptable.
This could be more annoying to resolve. We may need to upstream changes to
Netty, or make quite invasive changes to our {{BufferPool}}.
Getting the full stack trace will help inform next steps.
> Upgrade Netty on 4.x(current trunk)
> ---
>
> Key: CASSANDRA-17992
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17992
> Project: Cassandra
> Issue Type: Task
> Components: Dependencies
>Reporter: Ekaterina Dimitrova
>Priority: Low
> Fix For: 4.x
>
>
> I haven't been able to identify from the Netty docs which was the lowest
> version where JDK17 was added but we are about 40 versions behind in netty 4
> so I suspect we better update.
> We need to consider there was an issue with class cast exceptions when
> building with JDK17 with newer versions of netty (the newest available in
> March 2022). For the record, we didn't see those when running CI on JDK8 and
> JDK11. We also need to carefully revise the changes between the netty
> versions.
> Upgrading will cover also a fix in netty that was discussed in
> [this|https://the-asf.slack.com/archives/CK23JSY2K/p1665567660202989] ASF
> Slack thread.
> CC [~benedict] , [~aleksey]
--
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-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:comment-tabpanel=17624903#comment-17624903 ] Leonard Ma commented on CASSANDRA-16491: Thanks [~maedhroz] . I just addressed the comments in the PR. I did have a follow-up question that I left on the PR though. But if that doesn't warrant additional changes then I think we should be good to go. > 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: 4.x > > Time Spent: 50m > 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] [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=17624892#comment-17624892 ] Berenguer Blasi commented on CASSANDRA-17987: - Sorry if I am missing it bc reading so many circle workflows makes me dizzy. Are upgrade dtests repeat missing? > 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=17624892#comment-17624892 ] Berenguer Blasi edited comment on CASSANDRA-17987 at 10/27/22 7:00 AM: --- Sorry if I am missing it bc reading so many circle workflow screens makes me dizzy lol. Are upgrade dtests repeat missing? was (Author: bereng): Sorry if I am missing it bc reading so many circle workflows makes me dizzy. Are upgrade dtests repeat missing? > 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
