[jira] [Comment Edited] (CASSANDRA-19483) Catch InvalidLegacyProtocolMagic exceptions
[
https://issues.apache.org/jira/browse/CASSANDRA-19483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842979#comment-17842979
]
Brad Schoening edited comment on CASSANDRA-19483 at 7/24/24 8:15 PM:
-
[~ilyazr] ok, we can leave it as is, I didn't mean to stall this nice fix with
a open ended question.
was (Author: bschoeni):
[~ilyazr] ok, we can leave it as is, I didn't mean to ask stall this nice fix
with a open ended question.
> Catch InvalidLegacyProtocolMagic exceptions
> ---
>
> Key: CASSANDRA-19483
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19483
> Project: Cassandra
> Issue Type: Improvement
> Components: Observability/Logging
>Reporter: Brad Schoening
>Assignee: Ilya Zakharov
>Priority: Low
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Similar to CASSANDRA-18839, we frequently see the exception
> InvalidLegacyProtocolMagic with full stack traces flooding our logs. These
> are due to Qualys vulnerability scans.
> It seem to be a simple check in Message.java and would be better handled by:
> a) returning a boolean from validateLegacyProtocolMagic() ->
> hasValidLegacyProtocolMagic() instead of creating a custom exception class or
> b) adding a catch block in HandshakeProtocol.java and return null as is done
> for messagingVersion
> {code:java}
> static Initiate maybeDecode(ByteBuf buf) throws IOException
> {
> ...
> try (DataInputBuffer in = new DataInputBuffer(nio, false))
> {
> validateLegacyProtocolMagic(in.readInt()); // throws
> exception
> int flags = in.readInt();
> // legacy pre40 messagingVersion flag
> if (getBits(flags, 8, 8) < VERSION_40)
> return null;
> int minMessagingVersion = getBits(flags, 16, 8);
> int maxMessagingVersion = getBits(flags, 24, 8);
> // 5.0+ does not support pre40
> if (maxMessagingVersion < MessagingService.VERSION_40)
> return null;
>
> }
> catch (EOFException e)
> {
> return null;
> }
> }
> {code}
> {code:java}
> static void validateLegacyProtocolMagic(int magic) throws
> InvalidLegacyProtocolMagic
> {
> if (magic != PROTOCOL_MAGIC)
> throw new InvalidLegacyProtocolMagic(magic);
> }
> {code}
> {code:java}
> {{2024-03-20 03:47:27,380 [ERROR] [Messaging-EventLoop-3-2] cluster_id=9
> ip_address=10.0.0.1 InboundConnectionInitiator.java:360 - Failed to properly
> handshake with peer /10.0.2:33356. Closing the channel.}}
> {{io.netty.handler.codec.DecoderException:
> org.apache.cassandra.net.Message$InvalidLegacyProtocolMagic: Read 1431520594,
> Expected -900387334}}
> {{ at
> io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:478)}}
> {{ at
> io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed(ByteToMessageDecoder.java:404)}}
> {{ at
> io.netty.handler.codec.ByteToMessageDecoder.channelInputClosed(ByteToMessageDecoder.java:371)}}
> {{ at
> io.netty.handler.codec.ByteToMessageDecoder.channelInactive(ByteToMessageDecoder.java:354)}}
> {{ at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)}}
> {{ at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)}}
> {{ at
> io.netty.channel.AbstractChannelHandlerContext.fireChannelInactive(AbstractChannelHandlerContext.java:241)}}
> {{ at
> io.netty.channel.DefaultChannelPipeline$HeadContext.channelInactive(DefaultChannelPipeline.java:1405)}}
> {{ at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:262)}}
> {{ at
> io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:248)}}
> {{ at
> io.netty.channel.DefaultChannelPipeline.fireChannelInactive(DefaultChannelPipeline.java:901)}}
> {{ at
> io.netty.channel.AbstractChannel$AbstractUnsafe$8.run(AbstractChannel.java:819)}}
> {{ at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:164)}}
> {{ at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:472)}}
> {{ at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:384)}}
> {{ at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)}}
> {{ at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)}}
> {{ at
>
[jira] [Commented] (CASSANDRA-19022) Nodetool gcstats correctly displays Direct Memory usage and supports printing in table format
[
https://issues.apache.org/jira/browse/CASSANDRA-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17868476#comment-17868476
]
Brad Schoening commented on CASSANDRA-19022:
[~maoling] is this ready for review? It wasn't in patch submitted status.
> Nodetool gcstats correctly displays Direct Memory usage and supports printing
> in table format
> -
>
> Key: CASSANDRA-19022
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19022
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/nodetool
>Reporter: Brad Schoening
>Assignee: Ling Mao
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If {{io.netty.maxDirectMemory}} is not specified, Netty defaults the limit to
> the max heap size. Thus, direct memory in use can be significant.
> However, trying this on two different platform and the result returned in
> gcstats is always -1:
> {noformat}
> Interval (ms) Max GC Elapsed (ms)Total GC Elapsed (ms)Stdev GC Elapsed (ms)
> GC Reclaimed (MB) Collections Direct Memory Bytes
> 2792770717 274 665186 54
> 412762880890246120 -1{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] [Commented] (CASSANDRA-19671) Nodetool tabestats: add keyspace space used and table r/w ratio
[ https://issues.apache.org/jira/browse/CASSANDRA-19671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17868475#comment-17868475 ] Brad Schoening commented on CASSANDRA-19671: [~arkn98] have you had a chance to review the above comments by [~smiklosovic]? > Nodetool tabestats: add keyspace space used and table r/w ratio > --- > > Key: CASSANDRA-19671 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19671 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Brad Schoening >Assignee: Arun Ganesh >Priority: Low > Attachments: plaintext-humanreadable.txt, plaintext.txt > > Time Spent: 10m > Remaining Estimate: 0h > > Nodetool tabestats reports the space used live and total per table, but not > for the entire keyspace. This would be useful information. > Also, in the table level stats, it would be useful to have the read/write > ratio. This metric is important in choosing compaction strategies such as > LCS. -- 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-19779) Non-existing commitlog dir emits warnings in tools/bin
[
https://issues.apache.org/jira/browse/CASSANDRA-19779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17868471#comment-17868471
]
Brad Schoening commented on CASSANDRA-19779:
[~smiklosovic] LGTM +1
> Non-existing commitlog dir emits warnings in tools/bin
> ---
>
> Key: CASSANDRA-19779
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19779
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Tools
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When I extract the distribution tarball and I want to use tools in tools/bin,
> there is this warn log visible every time for tools when they are started
> (does not happen on "help" command, obviously)
> {code:java}
> WARN 14:25:11,835 Unable to determine block size for commit log directory:
> null {code}
> This is because we introduced this (1) in CASSANDRA-18464
> What that does is that it will go and try to create a temporary file in
> commit log directory to get "block size" for a "file store" that file is in.
> The problem with that is that when we just extract a tarball and run the
> tools - Cassandra was never started - then such commit log directory does not
> exist yet, so it tries to create a temporary file in a non-existing
> directory, which fails, hence the log message.
> The fix is to check if commitlog dir exists and return / skip the resolution
> of block size if it does not.
> Another approach might be to check if this is executed in the context of a
> tool and skip it from resolution altogether. The problem with this is that
> not all tools we have in bin/log call DatabaseDescriptor.
> toolInitialization() so we might combine these two.
> (1)
> [https://github.com/apache/cassandra/blob/cassandra-5.0/src/java/org/apache/cassandra/config/DatabaseDescriptor.java#L1455-L1462]
--
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-19631) Consider autocompletion of in-built functions in CQLSH
[
https://issues.apache.org/jira/browse/CASSANDRA-19631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17845417#comment-17845417
]
Brad Schoening edited comment on CASSANDRA-19631 at 7/23/24 8:11 PM:
-
1. With select I see the following:
{code:java}
cassandra@cqlsh> select
cqlshtests_nbqeqfhnqr.
system_cluster_metadata. true
* DISTINCT
system_distributed. TTL
- false
system_schema. WRITETIME
JSON
system_traces. {
[ NULL
system_views.
CAST system.
system_virtual_schema.
COUNT system_auth.
TOKEN {code}
min, max, sum, avg, abs, exp, log, log10, round
map_keys, map_values,
toDate, toTimestamp, toUnitTimestamp are among those missing.
2. Select with where LHS:
{code:java}
select * from system.peers where
peer TOKEN(
{code}
3. Select with where RHS
{code:java}
select * from system.peers where rack =
false true
- NULL {
[ TOKEN
{code}
was (Author: bschoeni):
1. With select I see the following:
{code:java}
cassandra@cqlsh> select
cqlshtests_nbqeqfhnqr.
system_cluster_metadata. true
* DISTINCT
system_distributed. TTL
- false
system_schema. WRITETIME
JSON
system_traces. {
[ NULL
system_views.
CAST system.
system_virtual_schema.
COUNT system_auth.
TOKEN {code}
MIN, MAX, SUM, AVG are among those missing.
2. With where:
{code:java}
select * from system.peers where
peer TOKEN(
{code}
{code:java}
select * from system.peers where rack =
false true
- NULL {
[ TOKEN
{code}
3. select * from system.peers where t =
> Consider autocompletion of in-built functions in CQLSH
> --
>
> Key: CASSANDRA-19631
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19631
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Interpreter
>Reporter: Stefan Miklosovic
>Assignee: Brad Schoening
>Priority: Normal
>
> Why do we not autocomplete native functions in CQLSH shell? I am pretty lost
> in what functions are there to choose from without consulting the
> documentation.
> Additionally, the documentation on [Blob conversion
> functions|https://github.com/apache/cassandra/blob/trunk/doc/cql3/CQL.textile#blob-conversion-functions]
> could use an example, as done for the other builtins.
--
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-19780) Illegal access warning logs visible on bin/tools invocations
[
https://issues.apache.org/jira/browse/CASSANDRA-19780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867755#comment-17867755
]
Brad Schoening commented on CASSANDRA-19780:
LGTM, then +1
> Illegal access warning logs visible on bin/tools invocations
>
>
> Key: CASSANDRA-19780
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19780
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Tools
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There is discrepancy between what opens we have for tools under Java 17 and
> what we open under Java 11.
> For example this does not emit any warnings when we are on Java 17:
> {code:java}
> ./tools/bin/auditlogviewer /tmp/diagnostics -f {code}
> But it does emit these warnings when we are on Java 11
> {code:java}
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access using Lookup on
> net.openhft.chronicle.core.Jvm
> (file:/tmp/apache-test/apache-cassandra-5.0-rc1-SNAPSHOT/lib/chronicle-core-2.23.36.jar)
> to class java.lang.reflect.AccessibleObject
> WARNING: Please consider reporting this to the maintainers of
> net.openhft.chronicle.core.Jvm
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future
> release{code}
> When I compared what that tool runs with on Java 17 and Java 11, I see this:
>
> Java 17
> {code:java}
> --add-exports java.base/jdk.internal.misc=ALL-UNNAMED
> --add-exports java.management.rmi/com.sun.jmx.remote.internal.rmi=ALL-UNNAMED
> --add-exports java.rmi/sun.rmi.registry=ALL-UNNAMED
> --add-exports java.rmi/sun.rmi.server=ALL-UNNAMED
> --add-exports java.sql/java.sql=ALL-UNNAMED
> --add-exports java.base/java.lang.ref=ALL-UNNAMED
> --add-exports jdk.unsupported/sun.misc=ALL-UNNAMED
> --add-opens java.base/java.lang.module=ALL-UNNAMED
> --add-opens java.base/jdk.internal.loader=ALL-UNNAMED
> --add-opens java.base/jdk.internal.ref=ALL-UNNAMED
> --add-opens java.base/jdk.internal.reflect=ALL-UNNAMED
> --add-opens java.base/jdk.internal.math=ALL-UNNAMED
> --add-opens java.base/jdk.internal.module=ALL-UNNAMED
> --add-opens java.base/jdk.internal.util.jar=ALL-UNNAMED
> --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED
> --add-opens java.base/sun.nio.ch=ALL-UNNAMED
> --add-opens java.base/java.io=ALL-UNNAMED
> --add-opens java.base/java.lang=ALL-UNNAMED
> --add-opens java.base/java.lang.reflect=ALL-UNNAMED
> --add-opens java.base/java.util=ALL-UNNAMED
> --add-opens java.base/java.nio=ALL-UNNAMED
> --add-exports jdk.attach/sun.tools.attach=ALL-UNNAMED
> --add-exports jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED
> --add-opens jdk.compiler/com.sun.tools.javac=ALL-UNNAMED {code}
> For Java 11
> {code:java}
> --add-exports java.base/jdk.internal.misc=ALL-UNNAMED
> --add-exports java.base/jdk.internal.ref=ALL-UNNAMED
> --add-exports java.base/sun.nio.ch=ALL-UNNAMED
> --add-exports java.management.rmi/com.sun.jmx.remote.internal.rmi=ALL-UNNAMED
> --add-exports java.rmi/sun.rmi.registry=ALL-UNNAMED
> --add-exports java.rmi/sun.rmi.server=ALL-UNNAMED
> --add-exports java.sql/java.sql=ALL-UNNAMED
> --add-opens java.base/java.lang.module=ALL-UNNAMED
> --add-opens java.base/jdk.internal.loader=ALL-UNNAMED
> --add-opens java.base/jdk.internal.ref=ALL-UNNAMED
> --add-opens java.base/jdk.internal.reflect=ALL-UNNAMED
> --add-opens java.base/jdk.internal.math=ALL-UNNAMED
> --add-opens java.base/jdk.internal.module=ALL-UNNAMED
> --add-opens java.base/jdk.internal.util.jar=ALL-UNNAMED
> --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED {code}
> The difference is that we are not exporting this for Java 11
> {code:java}
> --add-opens java.base/sun.nio.ch=ALL-UNNAMED
> --add-opens java.base/java.io=ALL-UNNAMED
> --add-opens java.base/java.lang=ALL-UNNAMED
> --add-opens java.base/java.lang.reflect=ALL-UNNAMED
> --add-opens java.base/java.util=ALL-UNNAMED
> --add-opens java.base/java.nio=ALL-UNNAMED
> --add-opens java.base/java.lang.reflect=ALL-UNNAMED {code}
> For Java 17, we explicitly add only these which are not applicable for 11
> (check the end of tools/bin/cassandra.in.sh)
> {code:java}
> --add-exports jdk.attach/sun.tools.attach=ALL-UNNAMED
> --add-exports jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED
> --add-opens jdk.compiler/com.sun.tools.javac=ALL-UNNAMED {code}
>
> So, what I propose is that we add the missing opens to cassandra.in.sh for
> Java 11.
> Even better, I would add this to conf/jvm11-clients.options
--
This message was sent by
[jira] [Commented] (CASSANDRA-19780) Illegal access warning logs visible on bin/tools invocations
[
https://issues.apache.org/jira/browse/CASSANDRA-19780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17867747#comment-17867747
]
Brad Schoening commented on CASSANDRA-19780:
[~smiklosovic] I understand the java.lang.reflect=ALL-UNNAMED change, but how
is the config.yaml parallelism and resource_class related?
> Illegal access warning logs visible on bin/tools invocations
>
>
> Key: CASSANDRA-19780
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19780
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Tools
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There is discrepancy between what opens we have for tools under Java 17 and
> what we open under Java 11.
> For example this does not emit any warnings when we are on Java 17:
> {code:java}
> ./tools/bin/auditlogviewer /tmp/diagnostics -f {code}
> But it does emit these warnings when we are on Java 11
> {code:java}
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access using Lookup on
> net.openhft.chronicle.core.Jvm
> (file:/tmp/apache-test/apache-cassandra-5.0-rc1-SNAPSHOT/lib/chronicle-core-2.23.36.jar)
> to class java.lang.reflect.AccessibleObject
> WARNING: Please consider reporting this to the maintainers of
> net.openhft.chronicle.core.Jvm
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future
> release{code}
> When I compared what that tool runs with on Java 17 and Java 11, I see this:
>
> Java 17
> {code:java}
> --add-exports java.base/jdk.internal.misc=ALL-UNNAMED
> --add-exports java.management.rmi/com.sun.jmx.remote.internal.rmi=ALL-UNNAMED
> --add-exports java.rmi/sun.rmi.registry=ALL-UNNAMED
> --add-exports java.rmi/sun.rmi.server=ALL-UNNAMED
> --add-exports java.sql/java.sql=ALL-UNNAMED
> --add-exports java.base/java.lang.ref=ALL-UNNAMED
> --add-exports jdk.unsupported/sun.misc=ALL-UNNAMED
> --add-opens java.base/java.lang.module=ALL-UNNAMED
> --add-opens java.base/jdk.internal.loader=ALL-UNNAMED
> --add-opens java.base/jdk.internal.ref=ALL-UNNAMED
> --add-opens java.base/jdk.internal.reflect=ALL-UNNAMED
> --add-opens java.base/jdk.internal.math=ALL-UNNAMED
> --add-opens java.base/jdk.internal.module=ALL-UNNAMED
> --add-opens java.base/jdk.internal.util.jar=ALL-UNNAMED
> --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED
> --add-opens java.base/sun.nio.ch=ALL-UNNAMED
> --add-opens java.base/java.io=ALL-UNNAMED
> --add-opens java.base/java.lang=ALL-UNNAMED
> --add-opens java.base/java.lang.reflect=ALL-UNNAMED
> --add-opens java.base/java.util=ALL-UNNAMED
> --add-opens java.base/java.nio=ALL-UNNAMED
> --add-exports jdk.attach/sun.tools.attach=ALL-UNNAMED
> --add-exports jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED
> --add-opens jdk.compiler/com.sun.tools.javac=ALL-UNNAMED {code}
> For Java 11
> {code:java}
> --add-exports java.base/jdk.internal.misc=ALL-UNNAMED
> --add-exports java.base/jdk.internal.ref=ALL-UNNAMED
> --add-exports java.base/sun.nio.ch=ALL-UNNAMED
> --add-exports java.management.rmi/com.sun.jmx.remote.internal.rmi=ALL-UNNAMED
> --add-exports java.rmi/sun.rmi.registry=ALL-UNNAMED
> --add-exports java.rmi/sun.rmi.server=ALL-UNNAMED
> --add-exports java.sql/java.sql=ALL-UNNAMED
> --add-opens java.base/java.lang.module=ALL-UNNAMED
> --add-opens java.base/jdk.internal.loader=ALL-UNNAMED
> --add-opens java.base/jdk.internal.ref=ALL-UNNAMED
> --add-opens java.base/jdk.internal.reflect=ALL-UNNAMED
> --add-opens java.base/jdk.internal.math=ALL-UNNAMED
> --add-opens java.base/jdk.internal.module=ALL-UNNAMED
> --add-opens java.base/jdk.internal.util.jar=ALL-UNNAMED
> --add-opens jdk.management/com.sun.management.internal=ALL-UNNAMED {code}
> The difference is that we are not exporting this for Java 11
> {code:java}
> --add-opens java.base/sun.nio.ch=ALL-UNNAMED
> --add-opens java.base/java.io=ALL-UNNAMED
> --add-opens java.base/java.lang=ALL-UNNAMED
> --add-opens java.base/java.lang.reflect=ALL-UNNAMED
> --add-opens java.base/java.util=ALL-UNNAMED
> --add-opens java.base/java.nio=ALL-UNNAMED
> --add-opens java.base/java.lang.reflect=ALL-UNNAMED {code}
> For Java 17, we explicitly add only these which are not applicable for 11
> (check the end of tools/bin/cassandra.in.sh)
> {code:java}
> --add-exports jdk.attach/sun.tools.attach=ALL-UNNAMED
> --add-exports jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED
> --add-opens jdk.compiler/com.sun.tools.javac=ALL-UNNAMED {code}
>
> So, what I propose is that we add the missing opens to
[jira] [Assigned] (CASSANDRA-19773) Update Docs page for 3rd Party Plugins
[ https://issues.apache.org/jira/browse/CASSANDRA-19773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening reassigned CASSANDRA-19773: -- Assignee: Brad Schoening > Update Docs page for 3rd Party Plugins > --- > > Key: CASSANDRA-19773 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19773 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > > # Stratio's Lucene plugin was maintained by Instaclustr (NetApp) but will be > retired with Cassandra 5.0 in favor of SAI indexing. It should be removed. > # CAPI-Rowcache hasn't been maintained in the last 7 years and might be a > candidate for removal from the docs here on plugins to avoid confusion with > inactive projects. > [integrating/plugins|https://github.com/apache/cassandra/tree/trunk/doc/modules/cassandra/pages/integrating/plugins/index.adoc] -- 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-19777) Update doc page for how-to commit with more intro
[ https://issues.apache.org/jira/browse/CASSANDRA-19777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19777: --- Description: The how-to commit documentation would be more helpful to new committers with some background details on the below. This should not be a git tutorial, but it should inform readers what they need to know or learn to be an effective committer. 0a) Using CLI vs GitHub web UI 0b) Always do your work in a local branch, and never push a branch upsteam. 1) The squash-rebase-merge (best name?) workflow with feature branches used on this repo 2) Basic git commands you should know, including: * *git remote* add & set-url * *squashing* with rebase -i * updating commit with *git commit --amend* * *push upstream --atomic -n* was: The how-to commit documentation would be more helpful to new committers with some background details on the below. This should not be a git tutorial, but it should inform readers what they need to know or learn to be an effective committer. 0) Using CLI vs GitHub web UI 1) The squash-rebase-merge (best name?) workflow with feature branches used on this repo 2) Basic git commands you should know, including: * *git remote* add & set-url * *squashing* with rebase -i * updating commit with *git commit --amend* * *push upstream --atomic -n* > Update doc page for how-to commit with more intro > - > > Key: CASSANDRA-19777 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19777 > Project: Cassandra > Issue Type: Task >Reporter: Brad Schoening >Priority: Normal > > The how-to commit documentation would be more helpful to new committers with > some background details on the below. This should not be a git tutorial, but > it should inform readers what they need to know or learn to be an effective > committer. > 0a) Using CLI vs GitHub web UI > 0b) Always do your work in a local branch, and never push a branch upsteam. > 1) The squash-rebase-merge (best name?) workflow with feature branches used > on this repo > 2) Basic git commands you should know, including: > * *git remote* add & set-url > * *squashing* with rebase -i > * updating commit with *git commit --amend* > * *push upstream --atomic -n* -- 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-19773) Update Docs page for 3rd Party Plugins
[ https://issues.apache.org/jira/browse/CASSANDRA-19773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19773: --- Description: # Stratio's Lucene plugin was maintained by Instaclustr (NetApp) but will be retired with Cassandra 5.0 in favor of SAI indexing. It should be removed. # CAPI-Rowcache hasn't been maintained in the last 7 years and might be a candidate for removal from the docs here on plugins to avoid confusion with inactive projects. [integrating/plugins|https://github.com/apache/cassandra/tree/trunk/doc/modules/cassandra/pages/integrating/plugins/index.adoc] was: # Stratio's Lucene plugin is now maintained by Instaclustr (NetApp) and will be retired with Cassandra 5.0 in favor of SAI indexing. Names and links should be updated accordingly. # CAPI-Rowcache hasn't been maintained in the last 7 years and might be a candidate for removal from the docs here on plugins to avoid confusion with inactive projects. [integrating/plugins|https://github.com/apache/cassandra/tree/trunk/doc/modules/cassandra/pages/integrating/plugins/index.adoc] > Update Docs page for 3rd Party Plugins > --- > > Key: CASSANDRA-19773 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19773 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Brad Schoening >Priority: Normal > > # Stratio's Lucene plugin was maintained by Instaclustr (NetApp) but will be > retired with Cassandra 5.0 in favor of SAI indexing. It should be removed. > # CAPI-Rowcache hasn't been maintained in the last 7 years and might be a > candidate for removal from the docs here on plugins to avoid confusion with > inactive projects. > [integrating/plugins|https://github.com/apache/cassandra/tree/trunk/doc/modules/cassandra/pages/integrating/plugins/index.adoc] -- 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-19773) Update Docs page for 3rd Party Plugins
[ https://issues.apache.org/jira/browse/CASSANDRA-19773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19773: --- Change Category: Semantic Complexity: Low Hanging Fruit Component/s: Documentation/Website Status: Open (was: Triage Needed) > Update Docs page for 3rd Party Plugins > --- > > Key: CASSANDRA-19773 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19773 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Brad Schoening >Priority: Normal > > # Stratio's Lucene plugin is now maintained by Instaclustr (NetApp) and will > be retired with Cassandra 5.0 in favor of SAI indexing. Names and links > should be updated accordingly. > # CAPI-Rowcache hasn't been maintained in the last 7 years and might be a > candidate for removal from the docs here on plugins to avoid confusion with > inactive projects. > [integrating/plugins|https://github.com/apache/cassandra/tree/trunk/doc/modules/cassandra/pages/integrating/plugins/index.adoc] -- 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-19777) Update doc page for how-to commit with more intro
[ https://issues.apache.org/jira/browse/CASSANDRA-19777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19777: --- Description: The how-to commit documentation would be more helpful to new committers with some background details on the below. This should not be a git tutorial, but it should inform readers what they need to know or learn to be an effective committer. 0) Using CLI vs GitHub web UI 1) The squash-rebase-merge (best name?) workflow with feature branches used on this repo 2) Basic git commands you should know, including: * *git remote* add & set-url * *squashing* with rebase -i * updating commit with *git commit --amend* * *push upstream --atomic -n* was: The how-to commit documentation would be more helpful to new committers with some background details on the below. This should not be a git tutorial, but it should inform readers what they need to know or learn to be an effective committer. 0) Using CLI vs GitHub web UI 1) The squash-rebase-merge (best name?) workflow used on this repo 2) Basic git commands you should know, including: * *git remote* add & set-url * *squashing* with rebase -i * updating commit with *git commit --amend* * *push upstream --atomic -n* > Update doc page for how-to commit with more intro > - > > Key: CASSANDRA-19777 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19777 > Project: Cassandra > Issue Type: Task >Reporter: Brad Schoening >Priority: Normal > > The how-to commit documentation would be more helpful to new committers with > some background details on the below. This should not be a git tutorial, but > it should inform readers what they need to know or learn to be an effective > committer. > 0) Using CLI vs GitHub web UI > 1) The squash-rebase-merge (best name?) workflow with feature branches used > on this repo > 2) Basic git commands you should know, including: > * *git remote* add & set-url > * *squashing* with rebase -i > * updating commit with *git commit --amend* > * *push upstream --atomic -n* -- 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-19777) Update doc page for how-to commit with more intro
Brad Schoening created CASSANDRA-19777: -- Summary: Update doc page for how-to commit with more intro Key: CASSANDRA-19777 URL: https://issues.apache.org/jira/browse/CASSANDRA-19777 Project: Cassandra Issue Type: Task Reporter: Brad Schoening The how-to commit documentation would be more helpful to new committers with some background details on the below. This should not be a git tutorial, but it should inform readers what they need to know or learn to be an effective committer. 0) Using CLI vs GitHub web UI 1) The squash-rebase-merge (best name?) workflow used on this repo 2) Basic git commands you should know, including: * *git remote* add & set-url * *squashing* with rebase -i * updating commit with *git commit --amend* * *push upstream --atomic -n* -- 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-19773) Update Docs page for 3rd Party Plugins
[ https://issues.apache.org/jira/browse/CASSANDRA-19773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866761#comment-17866761 ] Brad Schoening commented on CASSANDRA-19773: [~stefan.miklosovic] would you have thoughts on this, particularly the Lucene plugin? > Update Docs page for 3rd Party Plugins > --- > > Key: CASSANDRA-19773 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19773 > Project: Cassandra > Issue Type: Task >Reporter: Brad Schoening >Priority: Normal > > # Stratio's Lucene plugin is now maintained by Instaclustr (NetApp) and will > be retired with Cassandra 5.0 in favor of SAI indexing. Names and links > should be updated accordingly. > # CAPI-Rowcache hasn't been maintained in the last 7 years and might be a > candidate for removal from the docs here on plugins to avoid confusion with > inactive projects. > [integrating/plugins|https://github.com/apache/cassandra/tree/trunk/doc/modules/cassandra/pages/integrating/plugins/index.adoc] -- 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-19773) Update Docs page for 3rd Party Plugins
[ https://issues.apache.org/jira/browse/CASSANDRA-19773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19773: --- Description: # Stratio's Lucene plugin is now maintained by Instaclustr (NetApp) and will be retired with Cassandra 5.0 in favor of SAI indexing. Names and links should be updated accordingly. # CAPI-Rowcache hasn't been maintained in the last 7 years and might be a candidate for removal from the docs here on plugins to avoid confusion with inactive projects. [integrating/plugins|https://github.com/apache/cassandra/tree/trunk/doc/modules/cassandra/pages/integrating/plugins/index.adoc] was: # Stratio's Lucene plugin is now maintained by Instaclustr (NetApp). Names and links should be updated accordingly. # CAPI-Rowcache hasn't been maintained in the last 7 years and might be a candidate for removal from the docs here on plugins to avoid confusion with inactive projects. [integrating/plugins|https://github.com/apache/cassandra/tree/trunk/doc/modules/cassandra/pages/integrating/plugins/index.adoc] > Update Docs page for 3rd Party Plugins > --- > > Key: CASSANDRA-19773 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19773 > Project: Cassandra > Issue Type: Task >Reporter: Brad Schoening >Priority: Normal > > # Stratio's Lucene plugin is now maintained by Instaclustr (NetApp) and will > be retired with Cassandra 5.0 in favor of SAI indexing. Names and links > should be updated accordingly. > # CAPI-Rowcache hasn't been maintained in the last 7 years and might be a > candidate for removal from the docs here on plugins to avoid confusion with > inactive projects. > [integrating/plugins|https://github.com/apache/cassandra/tree/trunk/doc/modules/cassandra/pages/integrating/plugins/index.adoc] -- 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-19584) Glossary labeled as DataStax glossary
[ https://issues.apache.org/jira/browse/CASSANDRA-19584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19584: --- Fix Version/s: NA Since Version: NA Source Control Link: https://github.com/apache/cassandra-website/commit/505fbcbd7f358732c1069fda8dc4fdf6faebd6f8 Resolution: Fixed Status: Resolved (was: Ready to Commit) > Glossary labeled as DataStax glossary > - > > Key: CASSANDRA-19584 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19584 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Jon Haddad >Assignee: Brad Schoening >Priority: Normal > Fix For: NA > > Attachments: screenshot-1.png > > > Should be Cassandra glossary > https://cassandra.apache.org/_/glossary.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19773) Update Docs page for 3rd Party Plugins
[ https://issues.apache.org/jira/browse/CASSANDRA-19773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19773: --- Description: # Stratio's Lucene plugin is now maintained by Instaclustr (NetApp). Names and links should be updated accordingly. # CAPI-Rowcache hasn't been maintained in the last 7 years and might be a candidate for removal from the docs here on plugins to avoid confusion with inactive projects. [integrating/plugins|https://github.com/apache/cassandra/tree/trunk/doc/modules/cassandra/pages/integrating/plugins/index.adoc] was: # Stratio's Lucene plugin is now maintained by Instaclustr (NetApp). Names and links should be updated accordingly. # CAPI-Rowcache hasn't been maintained in the last 7 years and might be a candidate for removal from the docs here on plugins to avoid confusion with inactive projects. [integrating/plugins|https://github.com/apache/cassandra/tree/trunk/doc/modules/cassandra/pages/integrating/plugins] > Update Docs page for 3rd Party Plugins > --- > > Key: CASSANDRA-19773 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19773 > Project: Cassandra > Issue Type: Task >Reporter: Brad Schoening >Priority: Normal > > # Stratio's Lucene plugin is now maintained by Instaclustr (NetApp). Names > and links should be updated accordingly. > # CAPI-Rowcache hasn't been maintained in the last 7 years and might be a > candidate for removal from the docs here on plugins to avoid confusion with > inactive projects. > [integrating/plugins|https://github.com/apache/cassandra/tree/trunk/doc/modules/cassandra/pages/integrating/plugins/index.adoc] -- 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-19584) Glossary labeled as DataStax glossary
[ https://issues.apache.org/jira/browse/CASSANDRA-19584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19584: --- Status: Ready to Commit (was: Review In Progress) > Glossary labeled as DataStax glossary > - > > Key: CASSANDRA-19584 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19584 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Jon Haddad >Assignee: Brad Schoening >Priority: Normal > Attachments: screenshot-1.png > > > Should be Cassandra glossary > https://cassandra.apache.org/_/glossary.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19584) Glossary labeled as DataStax glossary
[ https://issues.apache.org/jira/browse/CASSANDRA-19584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19584: --- Reviewers: Bret McGuire, Jon Haddad, Brad Schoening Bret McGuire, Jon Haddad, Brad Schoening (was: Brad Schoening, Bret McGuire, Jon Haddad) Status: Review In Progress (was: Patch Available) > Glossary labeled as DataStax glossary > - > > Key: CASSANDRA-19584 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19584 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Jon Haddad >Assignee: Brad Schoening >Priority: Normal > Attachments: screenshot-1.png > > > Should be Cassandra glossary > https://cassandra.apache.org/_/glossary.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19584) Glossary labeled as DataStax glossary
[ https://issues.apache.org/jira/browse/CASSANDRA-19584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866417#comment-17866417 ] Brad Schoening commented on CASSANDRA-19584: [~absurdfarce] could you review this PR? > Glossary labeled as DataStax glossary > - > > Key: CASSANDRA-19584 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19584 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Jon Haddad >Assignee: Brad Schoening >Priority: Normal > Attachments: screenshot-1.png > > > Should be Cassandra glossary > https://cassandra.apache.org/_/glossary.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-19773) Update Docs page for 3rd Party Plugins
Brad Schoening created CASSANDRA-19773: -- Summary: Update Docs page for 3rd Party Plugins Key: CASSANDRA-19773 URL: https://issues.apache.org/jira/browse/CASSANDRA-19773 Project: Cassandra Issue Type: Task Reporter: Brad Schoening # Stratio's Lucene plugin is now maintained by Instaclustr (NetApp). Names and links should be updated accordingly. # CAPI-Rowcache hasn't been maintained in the last 7 years and might be a candidate for removal from the docs here on plugins to avoid confusion with inactive projects. [integrating/plugins|https://github.com/apache/cassandra/tree/trunk/doc/modules/cassandra/pages/integrating/plugins] -- 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-19771) NodeTool gcstats should have JSON output option
[
https://issues.apache.org/jira/browse/CASSANDRA-19771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening updated CASSANDRA-19771:
---
Status: Open (was: Triage Needed)
> NodeTool gcstats should have JSON output option
> ---
>
> Key: CASSANDRA-19771
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19771
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
>Reporter: Dhanush Ananthkar
>Priority: Normal
>
> *nodetool help gcstats* does not show a JSON option
>
> {noformat}
> nodetool [(-h | --host )] [(-p | --port )]
> [(-pp | --print-port)] [(-pw | --password
> )]
> [(-pwf | --password-file
> )]
> [(-u | --username )] gcstats
> {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] [Updated] (CASSANDRA-19771) NodeTool gcstats should have JSON output option
[
https://issues.apache.org/jira/browse/CASSANDRA-19771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening updated CASSANDRA-19771:
---
Change Category: Operability
Complexity: Low Hanging Fruit
Component/s: Tool/nodetool
> NodeTool gcstats should have JSON output option
> ---
>
> Key: CASSANDRA-19771
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19771
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
>Reporter: Dhanush Ananthkar
>Priority: Normal
>
> *nodetool help gcstats* does not show a JSON option
>
> {noformat}
> nodetool [(-h | --host )] [(-p | --port )]
> [(-pp | --print-port)] [(-pw | --password
> )]
> [(-pwf | --password-file
> )]
> [(-u | --username )] gcstats
> {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] [Commented] (CASSANDRA-19105) Using Capture to save results in CQLSH with Tracing on incorrectly saves the trace details
[
https://issues.apache.org/jira/browse/CASSANDRA-19105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866159#comment-17866159
]
Brad Schoening commented on CASSANDRA-19105:
[~gautamg] the PR was closed, and I don't see any changes in it anymore -- it
says files change 0. Wondering if you still have the branch
GautamGottipati:cassandra-5.0-capture-trace?
> Using Capture to save results in CQLSH with Tracing on incorrectly saves the
> trace details
> --
>
> Key: CASSANDRA-19105
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19105
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Brad Schoening
>Assignee: Gautam G
>Priority: Normal
>
> When using *Tracing* in CQLSH, it's sometimes helpful to use *Capture* to
> avoid paging through output when you want to see the trace results. However,
> the trace results are also incorrectly captured to the output file.
> According to *Help Capture* (below), only the query result should be saved.
> The correct behavior should display the trace results and only capture the
> query results.
> {_}Help capture message{_}: Only query result output is captured.
> Errors and output from cqlsh-only commands will still be shown in the cqlsh
> session.
>
--
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-19105) Using Capture to save results in CQLSH with Tracing on incorrectly saves the trace details
[
https://issues.apache.org/jira/browse/CASSANDRA-19105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866150#comment-17866150
]
Brad Schoening commented on CASSANDRA-19105:
[~gautamg] Hi, just wanted to check if you're able to make progress here.
> Using Capture to save results in CQLSH with Tracing on incorrectly saves the
> trace details
> --
>
> Key: CASSANDRA-19105
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19105
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Brad Schoening
>Assignee: Gautam G
>Priority: Normal
>
> When using *Tracing* in CQLSH, it's sometimes helpful to use *Capture* to
> avoid paging through output when you want to see the trace results. However,
> the trace results are also incorrectly captured to the output file.
> According to *Help Capture* (below), only the query result should be saved.
> The correct behavior should display the trace results and only capture the
> query results.
> {_}Help capture message{_}: Only query result output is captured.
> Errors and output from cqlsh-only commands will still be shown in the cqlsh
> session.
>
--
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-19584) Glossary labeled as DataStax glossary
[ https://issues.apache.org/jira/browse/CASSANDRA-19584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866138#comment-17866138 ] Brad Schoening commented on CASSANDRA-19584: [~rustyrazorblade] could you review this PR? > Glossary labeled as DataStax glossary > - > > Key: CASSANDRA-19584 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19584 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Jon Haddad >Assignee: Brad Schoening >Priority: Normal > Attachments: screenshot-1.png > > > Should be Cassandra glossary > https://cassandra.apache.org/_/glossary.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-19771) NodeTool gcstats should have JSON output option
[
https://issues.apache.org/jira/browse/CASSANDRA-19771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17866109#comment-17866109
]
Brad Schoening commented on CASSANDRA-19771:
[~rtib] [~mmuzaf] This will change the output of help message and user docs, so
probably best to be worked separately.
> NodeTool gcstats should have JSON output option
> ---
>
> Key: CASSANDRA-19771
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19771
> Project: Cassandra
> Issue Type: Improvement
>Reporter: Dhanush Ananthkar
>Priority: Normal
>
> *nodetool help gcstats* does not show a JSON option
>
> {noformat}
> nodetool [(-h | --host )] [(-p | --port )]
> [(-pp | --print-port)] [(-pw | --password
> )]
> [(-pwf | --password-file
> )]
> [(-u | --username )] gcstats
> {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] [Commented] (CASSANDRA-19584) Glossary labeled as DataStax glossary
[ https://issues.apache.org/jira/browse/CASSANDRA-19584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17865618#comment-17865618 ] Brad Schoening commented on CASSANDRA-19584: !screenshot-1.png! > Glossary labeled as DataStax glossary > - > > Key: CASSANDRA-19584 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19584 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Jon Haddad >Assignee: Brad Schoening >Priority: Normal > Attachments: screenshot-1.png > > > Should be Cassandra glossary > https://cassandra.apache.org/_/glossary.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19584) Glossary labeled as DataStax glossary
[ https://issues.apache.org/jira/browse/CASSANDRA-19584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19584: --- Attachment: screenshot-1.png > Glossary labeled as DataStax glossary > - > > Key: CASSANDRA-19584 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19584 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Jon Haddad >Assignee: Brad Schoening >Priority: Normal > Attachments: screenshot-1.png > > > Should be Cassandra glossary > https://cassandra.apache.org/_/glossary.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19584) Glossary labeled as DataStax glossary
[ https://issues.apache.org/jira/browse/CASSANDRA-19584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19584: --- Test and Documentation Plan: Building website locally Status: Patch Available (was: In Progress) > Glossary labeled as DataStax glossary > - > > Key: CASSANDRA-19584 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19584 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Jon Haddad >Assignee: Brad Schoening >Priority: Normal > > Should be Cassandra glossary > https://cassandra.apache.org/_/glossary.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19665) Add download link for Java drivers from download page
[ https://issues.apache.org/jira/browse/CASSANDRA-19665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19665: --- Fix Version/s: NA Source Control Link: https://github.com/apache/cassandra-website/commit/e343b2d54ddbcfc9416d04b9c67a928eab06c314 Resolution: Fixed Status: Resolved (was: Ready to Commit) > Add download link for Java drivers from download page > - > > Key: CASSANDRA-19665 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19665 > Project: Cassandra > Issue Type: Task > Components: Client/java-driver, Documentation/Website >Reporter: Bret McGuire >Assignee: Brad Schoening >Priority: Normal > Labels: pull-request-available > Fix For: NA > > > Seems like we should have a link to download Java drivers from the [download > page|https://cassandra.apache.org/_/download.html] on the Website -- 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-17655) Prevent JVM Humongous allocations
[
https://issues.apache.org/jira/browse/CASSANDRA-17655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17865486#comment-17865486
]
Brad Schoening edited comment on CASSANDRA-17655 at 7/12/24 1:59 PM:
-
The below code can be used to cause humongous allocations in a generic Java JVM.
{code:java}
public class HumongousAllocation {
public static void main(String[] args {
// Define the size of the allocation
// For example, to allocate a 1GB byte array
int size = 1024 * 1024 * 1024; // 1 GB
// Allocate the humongous object
byte[] humongousArray = new byte[size];
// Fill the array to ensure allocation
for (int i = 0; i < size; i++) {
humongousArray[i] = 1;
}
System.out.println("Humongous allocation done!");
}
}
{code}
{code:java}
java -Xmx2G HumongousAllocation
{code}
Looking to see if the memory pools available in JMX will report on humongous
allocations. The only way to see it currently is enable and look at gc.log.
was (Author: bschoeni):
The below code can be used to cause humongous allocations in a Java JVM.
{code:java}
public class HumongousAllocation {
public static void main(String[] args {
// Define the size of the allocation
// For example, to allocate a 1GB byte array
int size = 1024 * 1024 * 1024; // 1 GB
// Allocate the humongous object
byte[] humongousArray = new byte[size];
// Fill the array to ensure allocation
for (int i = 0; i < size; i++) {
humongousArray[i] = 1;
}
System.out.println("Humongous allocation done!");
}
}
{code}
{code:java}
java -Xmx2G HumongousAllocation
{code}
> Prevent JVM Humongous allocations
> -
>
> Key: CASSANDRA-17655
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17655
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Other
>Reporter: Brad Schoening
>Priority: Normal
>
> Several articles on Cassandra note that certain workloads, especially large
> partitions, can cause humongous allocations in Java, which can be reduced,
> but not always eliminated by increasing RegionSize. RegionSize max is 32MB.
> Humongous allocations are an undesirable performance issue because new
> objects get directly allocated in old space.
> Below is a sample message seen in the gc.log
> 2022-05-23T18:46:58.743+0800: 3758624.170: [GC pause (G1 Humongous
> Allocation) (young) (initial-mark) 3758624.171: [G1Ergonomics (CSet
> Construction) start choosing CSet, _pending_cards: 56725, predicted base
> time: 39.83 ms, remaining time: 160.17 ms, target pause time: 200.00 ms]
> Instead of Cassandra users tuning RegionSize manually, a better solution
> would be for Cassandra to limit the size of allocations, or consider moving
> humongous allocations off heap.
>
> References
> [https://docs.oracle.com/en/java/javase/11/gctuning/garbage-first-g1-garbage-collector1.html#GUID-D74F3CC7-CC9F-45B5-B03D-510AEEAC2DAC]
> [https://stevenlacerda.medium.com/identifying-and-fixing-humongous-allocations-in-cassandra-bf46444cec41]
> https://krzysztofslusarski.github.io/2020/11/10/humongous.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17655) Prevent JVM Humongous allocations
[ https://issues.apache.org/jira/browse/CASSANDRA-17655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-17655: --- Bug Category: Parent values: Degradation(12984) Complexity: Normal Component/s: Local/Other Discovered By: User Report Severity: Low Status: Open (was: Triage Needed) > Prevent JVM Humongous allocations > - > > Key: CASSANDRA-17655 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17655 > Project: Cassandra > Issue Type: Bug > Components: Local/Other >Reporter: Brad Schoening >Priority: Normal > > Several articles on Cassandra note that certain workloads, especially large > partitions, can cause humongous allocations in Java, which can be reduced, > but not always eliminated by increasing RegionSize. RegionSize max is 32MB. > Humongous allocations are an undesirable performance issue because new > objects get directly allocated in old space. > Below is a sample message seen in the gc.log > 2022-05-23T18:46:58.743+0800: 3758624.170: [GC pause (G1 Humongous > Allocation) (young) (initial-mark) 3758624.171: [G1Ergonomics (CSet > Construction) start choosing CSet, _pending_cards: 56725, predicted base > time: 39.83 ms, remaining time: 160.17 ms, target pause time: 200.00 ms] > Instead of Cassandra users tuning RegionSize manually, a better solution > would be for Cassandra to limit the size of allocations, or consider moving > humongous allocations off heap. > > References > [https://docs.oracle.com/en/java/javase/11/gctuning/garbage-first-g1-garbage-collector1.html#GUID-D74F3CC7-CC9F-45B5-B03D-510AEEAC2DAC] > [https://stevenlacerda.medium.com/identifying-and-fixing-humongous-allocations-in-cassandra-bf46444cec41] > https://krzysztofslusarski.github.io/2020/11/10/humongous.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17655) Prevent JVM Humongous allocations
[
https://issues.apache.org/jira/browse/CASSANDRA-17655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17865486#comment-17865486
]
Brad Schoening commented on CASSANDRA-17655:
The below code can be used to cause humongous allocations in a Java JVM.
{code:java}
public class HumongousAllocation {
public static void main(String[] args {
// Define the size of the allocation
// For example, to allocate a 1GB byte array
int size = 1024 * 1024 * 1024; // 1 GB
// Allocate the humongous object
byte[] humongousArray = new byte[size];
// Fill the array to ensure allocation
for (int i = 0; i < size; i++) {
humongousArray[i] = 1;
}
System.out.println("Humongous allocation done!");
}
}
{code}
{code:java}
java -Xmx2G HumongousAllocation
{code}
> Prevent JVM Humongous allocations
> -
>
> Key: CASSANDRA-17655
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17655
> Project: Cassandra
> Issue Type: Bug
>Reporter: Brad Schoening
>Priority: Normal
>
> Several articles on Cassandra note that certain workloads, especially large
> partitions, can cause humongous allocations in Java, which can be reduced,
> but not always eliminated by increasing RegionSize. RegionSize max is 32MB.
> Humongous allocations are an undesirable performance issue because new
> objects get directly allocated in old space.
> Below is a sample message seen in the gc.log
> 2022-05-23T18:46:58.743+0800: 3758624.170: [GC pause (G1 Humongous
> Allocation) (young) (initial-mark) 3758624.171: [G1Ergonomics (CSet
> Construction) start choosing CSet, _pending_cards: 56725, predicted base
> time: 39.83 ms, remaining time: 160.17 ms, target pause time: 200.00 ms]
> Instead of Cassandra users tuning RegionSize manually, a better solution
> would be for Cassandra to limit the size of allocations, or consider moving
> humongous allocations off heap.
>
> References
> [https://docs.oracle.com/en/java/javase/11/gctuning/garbage-first-g1-garbage-collector1.html#GUID-D74F3CC7-CC9F-45B5-B03D-510AEEAC2DAC]
> [https://stevenlacerda.medium.com/identifying-and-fixing-humongous-allocations-in-cassandra-bf46444cec41]
> https://krzysztofslusarski.github.io/2020/11/10/humongous.html
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18263) Update gc settings in build.xml
[ https://issues.apache.org/jira/browse/CASSANDRA-18263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17865178#comment-17865178 ] Brad Schoening commented on CASSANDRA-18263: [~jlewandowski] was switching to G1GC completed? I ask in part because [Operating: Hardware |https://cassandra.apache.org/doc/trunk/cassandra/managing/operating/hardware.html] still mentions ParNew/ConcurrentMarkSweep garbage collection. > Update gc settings in build.xml > --- > > Key: CASSANDRA-18263 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18263 > Project: Cassandra > Issue Type: Task > Components: Local/Config >Reporter: Ekaterina Dimitrova >Assignee: Jacek Lewandowski >Priority: Normal > Fix For: 5.x > > > As part of CASSANDRA-18027 we switched trunk to default to G1GC. We need to > update also our test settings in build.xml to test with what we default to in > trunk > CC [~mck] -- 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-19746) Update CQLSH website documentation to remove Python 2.7 reference
[ https://issues.apache.org/jira/browse/CASSANDRA-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19746: --- Resolution: Won't Fix Status: Resolved (was: Open) This was corrected for trunk, so it doesn't seem necessary to correct it for 4.1, esp once 5.0 is GA. > Update CQLSH website documentation to remove Python 2.7 reference > - > > Key: CASSANDRA-19746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Brad Schoening >Assignee: Mohammad Suhel >Priority: Low > Time Spent: 1h > Remaining Estimate: 0h > > The CQLSH [Compatibility > (4.1)|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] > section mentions Python 2.7 but this should be Python 3 now. > Note: it seems to be only an issue only with 4.1. > The trunk link here is correct: [Compatibility > (trunk)|https://cassandra.apache.org/doc/trunk/cassandra/managing/tools/cqlsh.html] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19746) Update CQLSH website documentation to remove Python 2.7 reference
[ https://issues.apache.org/jira/browse/CASSANDRA-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19746: --- Description: The CQLSH [Compatibility (4.1)|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] section mentions Python 2.7 but this should be Python 3 now. Note: it seems to be only an issue only with 4.1. The trunk link here is correct: [Compatibility (trunk)|https://cassandra.apache.org/doc/trunk/cassandra/managing/tools/cqlsh.html] was: The CQLSH [Compatibility (4.1)|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] section mentions Python 2.7 but this should be Python 3 now. Note: it seems to be only an issue only with 4.1. The link here is correct [Compatibility (trunk)|https://cassandra.apache.org/doc/trunk/cassandra/managing/tools/cqlsh.html] > Update CQLSH website documentation to remove Python 2.7 reference > - > > Key: CASSANDRA-19746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Brad Schoening >Assignee: Mohammad Suhel >Priority: Low > Time Spent: 1h > Remaining Estimate: 0h > > The CQLSH [Compatibility > (4.1)|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] > section mentions Python 2.7 but this should be Python 3 now. > Note: it seems to be only an issue only with 4.1. > The trunk link here is correct: [Compatibility > (trunk)|https://cassandra.apache.org/doc/trunk/cassandra/managing/tools/cqlsh.html] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19746) Update CQLSH website documentation to remove Python 2.7 reference
[ https://issues.apache.org/jira/browse/CASSANDRA-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19746: --- Description: The CQLSH [Compatibility (4.1)|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] section mentions Python 2.7 but this should be Python 3 now. Note: it seems to be only an issue only with 4.1. The link here is correct [Compatibility (trunk)|https://cassandra.apache.org/doc/trunk/cassandra/managing/tools/cqlsh.html] was:The CQLSH [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] section mentions Python 2.7 but this should be Python 3 now. > Update CQLSH website documentation to remove Python 2.7 reference > - > > Key: CASSANDRA-19746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Brad Schoening >Assignee: Mohammad Suhel >Priority: Low > Time Spent: 40m > Remaining Estimate: 0h > > The CQLSH [Compatibility > (4.1)|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] > section mentions Python 2.7 but this should be Python 3 now. > Note: it seems to be only an issue only with 4.1. > The link here is correct [Compatibility > (trunk)|https://cassandra.apache.org/doc/trunk/cassandra/managing/tools/cqlsh.html] -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19746) Update CQLSH website documentation to remove Python 2.7 reference
[ https://issues.apache.org/jira/browse/CASSANDRA-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19746: --- Fix Version/s: (was: 4.1.x) > Update CQLSH website documentation to remove Python 2.7 reference > - > > Key: CASSANDRA-19746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Brad Schoening >Assignee: Mohammad Suhel >Priority: Low > Time Spent: 40m > Remaining Estimate: 0h > > The CQLSH > [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] > section mentions Python 2.7 but this should be Python 3 now. -- 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-19746) Update CQLSH website documentation to remove Python 2.7 reference
[ https://issues.apache.org/jira/browse/CASSANDRA-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19746: --- Fix Version/s: 4.1.x > Update CQLSH website documentation to remove Python 2.7 reference > - > > Key: CASSANDRA-19746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Brad Schoening >Assignee: Mohammad Suhel >Priority: Low > Fix For: 4.1.x > > Time Spent: 40m > Remaining Estimate: 0h > > The CQLSH > [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] > section mentions Python 2.7 but this should be Python 3 now. -- 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-19746) Update CQLSH website documentation to remove Python 2.7 reference
[ https://issues.apache.org/jira/browse/CASSANDRA-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19746: --- Description: The CQLSH [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] section mentions Python 2.7 but this should be Python 3 now. (was: The CQLSH [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] section mentions Python 2.7 but this should be Python 3.x now.) > Update CQLSH website documentation to remove Python 2.7 reference > - > > Key: CASSANDRA-19746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Brad Schoening >Assignee: Mohammad Suhel >Priority: Low > Time Spent: 0.5h > Remaining Estimate: 0h > > The CQLSH > [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] > section mentions Python 2.7 but this should be Python 3 now. -- 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-19584) Glossary labeled as DataStax glossary
[ https://issues.apache.org/jira/browse/CASSANDRA-19584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19584: --- Bug Category: Parent values: Correctness(12982) Complexity: Low Hanging Fruit Discovered By: User Report Severity: Low Assignee: Brad Schoening Status: Open (was: Triage Needed) > Glossary labeled as DataStax glossary > - > > Key: CASSANDRA-19584 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19584 > Project: Cassandra > Issue Type: Bug > Components: Documentation/Website >Reporter: Jon Haddad >Assignee: Brad Schoening >Priority: Normal > > Should be Cassandra glossary > https://cassandra.apache.org/_/glossary.html -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-19665) Add download link for Java drivers from download page
[ https://issues.apache.org/jira/browse/CASSANDRA-19665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19665: --- Status: Ready to Commit (was: Review In Progress) > Add download link for Java drivers from download page > - > > Key: CASSANDRA-19665 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19665 > Project: Cassandra > Issue Type: Task > Components: Client/java-driver, Documentation/Website >Reporter: Bret McGuire >Assignee: Brad Schoening >Priority: Normal > Labels: pull-request-available > > Seems like we should have a link to download Java drivers from the [download > page|https://cassandra.apache.org/_/download.html] on the Website -- 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-19665) Add download link for Java drivers from download page
[ https://issues.apache.org/jira/browse/CASSANDRA-19665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17862871#comment-17862871 ] Brad Schoening commented on CASSANDRA-19665: [~mck] [~absurdfarce] I replaced my original branch with a new one, and the PR-277 has the same changes as 276. If you could just give that a thumbs up pls. > Add download link for Java drivers from download page > - > > Key: CASSANDRA-19665 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19665 > Project: Cassandra > Issue Type: Task > Components: Client/java-driver, Documentation/Website >Reporter: Bret McGuire >Assignee: Brad Schoening >Priority: Normal > Labels: pull-request-available > > Seems like we should have a link to download Java drivers from the [download > page|https://cassandra.apache.org/_/download.html] on the Website -- 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-19746) Update CQLSH documentation to remove Python 2.7 reference
[ https://issues.apache.org/jira/browse/CASSANDRA-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19746: --- Change Category: Code Clarity Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > Update CQLSH documentation to remove Python 2.7 reference > - > > Key: CASSANDRA-19746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Low > > The CQLSH > [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] > section mentions Python 2.7 but this should be Python 3.x now. -- 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-19746) Update CQLSH website documentation to remove Python 2.7 reference
[ https://issues.apache.org/jira/browse/CASSANDRA-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19746: --- Summary: Update CQLSH website documentation to remove Python 2.7 reference (was: Update CQLSH documentation to remove Python 2.7 reference) > Update CQLSH website documentation to remove Python 2.7 reference > - > > Key: CASSANDRA-19746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Low > > The CQLSH > [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] > section mentions Python 2.7 but this should be Python 3.x now. -- 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-19746) Update CQLSH documentation to remove Python 2.7 reference
[ https://issues.apache.org/jira/browse/CASSANDRA-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening reassigned CASSANDRA-19746: -- Assignee: Brad Schoening > Update CQLSH documentation to remove Python 2.7 reference > - > > Key: CASSANDRA-19746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Low > > The CQLSH > [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] > section mentions Python 2.7 but this should be Python 3.x now. -- 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-19746) Update CQLSH documentation to remove Python 2.7 reference
[ https://issues.apache.org/jira/browse/CASSANDRA-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19746: --- Priority: Low (was: Normal) > Update CQLSH documentation to remove Python 2.7 reference > - > > Key: CASSANDRA-19746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Brad Schoening >Priority: Low > > The CQLSH > [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] > section mentions Python 2.7 but this should be Python 3.x now. -- 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-19746) Update CQLSH documentation to remove Python 2.7 reference
[ https://issues.apache.org/jira/browse/CASSANDRA-19746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19746: --- Impacts: Docs (was: None) > Update CQLSH documentation to remove Python 2.7 reference > - > > Key: CASSANDRA-19746 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: Brad Schoening >Priority: Low > > The CQLSH > [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] > section mentions Python 2.7 but this should be Python 3.x now. -- 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-19746) Update CQLSH documentation to remove Python 2.7 reference
Brad Schoening created CASSANDRA-19746: -- Summary: Update CQLSH documentation to remove Python 2.7 reference Key: CASSANDRA-19746 URL: https://issues.apache.org/jira/browse/CASSANDRA-19746 Project: Cassandra Issue Type: Task Components: Documentation Reporter: Brad Schoening The CQLSH [Compatibility|https://cassandra.apache.org/doc/stable/cassandra/tools/cqlsh.html#compatibility] section mentions Python 2.7 but this should be Python 3.x now. -- 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-19665) Add download link for Java drivers from download page
[ https://issues.apache.org/jira/browse/CASSANDRA-19665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19665: --- Test and Documentation Plan: Text only change, ran 'website build' (was: Doc only change, ran 'website build') > Add download link for Java drivers from download page > - > > Key: CASSANDRA-19665 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19665 > Project: Cassandra > Issue Type: Task > Components: Client/java-driver, Documentation/Website >Reporter: Bret McGuire >Assignee: Brad Schoening >Priority: Normal > > Seems like we should have a link to download Java drivers from the [download > page|https://cassandra.apache.org/_/download.html] on the Website -- 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-19665) Add download link for Java drivers from download page
[ https://issues.apache.org/jira/browse/CASSANDRA-19665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19665: --- Test and Documentation Plan: Doc only change, ran 'website build' Status: Patch Available (was: In Progress) > Add download link for Java drivers from download page > - > > Key: CASSANDRA-19665 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19665 > Project: Cassandra > Issue Type: Task > Components: Client/java-driver, Documentation/Website >Reporter: Bret McGuire >Assignee: Brad Schoening >Priority: Normal > > Seems like we should have a link to download Java drivers from the [download > page|https://cassandra.apache.org/_/download.html] on the Website -- 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-19665) Add download link for Java drivers from download page
[ https://issues.apache.org/jira/browse/CASSANDRA-19665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening reassigned CASSANDRA-19665: -- Assignee: Brad Schoening > Add download link for Java drivers from download page > - > > Key: CASSANDRA-19665 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19665 > Project: Cassandra > Issue Type: Task > Components: Client/java-driver, Documentation/Website >Reporter: Bret McGuire >Assignee: Brad Schoening >Priority: Normal > > Seems like we should have a link to download Java drivers from the [download > page|https://cassandra.apache.org/_/download.html] on the Website -- 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-19665) Add download link for Java drivers from download page
[ https://issues.apache.org/jira/browse/CASSANDRA-19665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19665: --- Change Category: Code Clarity Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > Add download link for Java drivers from download page > - > > Key: CASSANDRA-19665 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19665 > Project: Cassandra > Issue Type: Task > Components: Client/java-driver, Documentation/Website >Reporter: Bret McGuire >Priority: Normal > > Seems like we should have a link to download Java drivers from the [download > page|https://cassandra.apache.org/_/download.html] on the Website -- 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-18762) Repair triggers OOM with direct buffer memory
[
https://issues.apache.org/jira/browse/CASSANDRA-18762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening updated CASSANDRA-18762:
---
Resolution: Cannot Reproduce
Status: Resolved (was: Open)
We haven't seen this in a while in our clusters running 4.x and 4.1.3, 4.1.5,
so I'm closing this as can't reproduce.
> Repair triggers OOM with direct buffer memory
> -
>
> Key: CASSANDRA-18762
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18762
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
>Reporter: Brad Schoening
>Priority: Normal
> Labels: OutOfMemoryError
> Attachments: Cluster-dm-metrics-1.PNG,
> image-2023-12-06-15-28-05-459.png, image-2023-12-06-15-29-31-491.png,
> image-2023-12-06-15-58-55-007.png
>
>
> We are seeing repeated failures of nodes with 16GB of heap on a VM with 32GB
> of physical RAM due to direct memory. This seems to be related to
> CASSANDRA-15202 which moved Merkel trees off-heap in 4.0. Using Cassandra
> 4.0.6 with Java 11.
> {noformat}
> 2023-08-09 04:30:57,470 [INFO ] [AntiEntropyStage:1] cluster_id=101
> ip_address=169.0.0.1 RepairSession.java:202 - [repair
> #5e55a3b0-366d-11ee-a644-d91df26add5e] Received merkle tree for table_a from
> /169.102.200.241:7000
> 2023-08-09 04:30:57,567 [INFO ] [AntiEntropyStage:1] cluster_id=101
> ip_address=169.0.0.1 RepairSession.java:202 - [repair
> #5e0d2900-366d-11ee-a644-d91df26add5e] Received merkle tree for table_b from
> /169.93.192.29:7000
> 2023-08-09 04:30:57,568 [INFO ] [AntiEntropyStage:1] cluster_id=101
> ip_address=169.0.0.1 RepairSession.java:202 - [repair
> #5e1dcad0-366d-11ee-a644-d91df26add5e] Received merkle tree for table_c from
> /169.104.171.134:7000
> 2023-08-09 04:30:57,591 [INFO ] [AntiEntropyStage:1] cluster_id=101
> ip_address=169.0.0.1 RepairSession.java:202 - [repair
> #5e69a0e0-366d-11ee-a644-d91df26add5e] Received merkle tree for table_b from
> /169.79.232.67:7000
> 2023-08-09 04:30:57,876 [INFO ] [Service Thread] cluster_id=101
> ip_address=169.0.0.1 GCInspector.java:294 - G1 Old Generation GC in 282ms.
> Compressed Class Space: 8444560 -> 8372152; G1 Eden Space: 7809794048 -> 0;
> G1 Old Gen: 1453478400 -> 820942800; G1 Survivor Space: 419430400 -> 0;
> Metaspace: 80411136 -> 80176528
> 2023-08-09 04:30:58,387 [ERROR] [AntiEntropyStage:1] cluster_id=101
> ip_address=169.0.0.1 JVMStabilityInspector.java:102 - OutOfMemory error
> letting the JVM handle the error:
> java.lang.OutOfMemoryError: Direct buffer memory
> at java.base/java.nio.Bits.reserveMemory(Bits.java:175)
> at java.base/java.nio.DirectByteBuffer.(DirectByteBuffer.java:118)
> at java.base/java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:318)
> at org.apache.cassandra.utils.MerkleTree.allocate(MerkleTree.java:742)
> at
> org.apache.cassandra.utils.MerkleTree.deserializeOffHeap(MerkleTree.java:780)
> at org.apache.cassandra.utils.MerkleTree.deserializeTree(MerkleTree.java:751)
> at org.apache.cassandra.utils.MerkleTree.deserialize(MerkleTree.java:720)
> at org.apache.cassandra.utils.MerkleTree.deserialize(MerkleTree.java:698)
> at
> org.apache.cassandra.utils.MerkleTrees$MerkleTreesSerializer.deserialize(MerkleTrees.java:416)
> at
> org.apache.cassandra.repair.messages.ValidationResponse$1.deserialize(ValidationResponse.java:100)
> at
> org.apache.cassandra.repair.messages.ValidationResponse$1.deserialize(ValidationResponse.java:84)
> at
> org.apache.cassandra.net.Message$Serializer.deserializePost40(Message.java:782)
> at org.apache.cassandra.net.Message$Serializer.deserialize(Message.java:642)
> at
> org.apache.cassandra.net.InboundMessageHandler$LargeMessage.deserialize(InboundMessageHandler.java:364)
> at
> org.apache.cassandra.net.InboundMessageHandler$LargeMessage.access$1100(InboundMessageHandler.java:317)
> at
> org.apache.cassandra.net.InboundMessageHandler$ProcessLargeMessage.provideMessage(InboundMessageHandler.java:504)
> at
> org.apache.cassandra.net.InboundMessageHandler$ProcessMessage.run(InboundMessageHandler.java:429)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:834)no* further _formatting_ is
> done here{noformat}
>
> -XX:+AlwaysPreTouch
> -XX:+CrashOnOutOfMemoryError
> -XX:+ExitOnOutOfMemoryError
> -XX:+HeapDumpOnOutOfMemoryError
> -XX:+ParallelRefProcEnabled
>
[jira] [Updated] (CASSANDRA-19680) Update URL in Java Driver README.md maven badge
[ https://issues.apache.org/jira/browse/CASSANDRA-19680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19680: --- Fix Version/s: NA Impacts: Docs (was: None) Source Control Link: https://github.com/apache/cassandra-java-driver/commit/85bb4065098b887d2dda26eb14423ce4fc687045 Resolution: Fixed Status: Resolved (was: Ready to Commit) > Update URL in Java Driver README.md maven badge > --- > > Key: CASSANDRA-19680 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19680 > Project: Cassandra > Issue Type: Improvement > Components: Client/java-driver >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > Fix For: NA > > > The maven badge needs to be updated from com.datastax.oss to > org.apache.cassandra. Also add a license badge. -- 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-19375) Link in docs to Achilles Java Driver links to malicious site
[ https://issues.apache.org/jira/browse/CASSANDRA-19375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19375: --- Fix Version/s: 5.x Impacts: Docs (was: None) Source Control Link: https://github.com/apache/cassandra/commit/7f1c0e9e76a0bdfc23ef6a655ec7774bc0f77e18 Resolution: Fixed Status: Resolved (was: Ready to Commit) > Link in docs to Achilles Java Driver links to malicious site > > > Key: CASSANDRA-19375 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19375 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: PJ Fanning >Assignee: Brad Schoening >Priority: Normal > Fix For: 5.x > > > https://cassandra.apache.org/doc/4.1/cassandra/getting_started/drivers.html#java > The Achilles link looks dangerous. I tried it and it looked like the link has > been taken over by a malicious user. -- 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-19680) Update URL in Java Driver README.md maven badge
[ https://issues.apache.org/jira/browse/CASSANDRA-19680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19680: --- Status: Ready to Commit (was: Review In Progress) > Update URL in Java Driver README.md maven badge > --- > > Key: CASSANDRA-19680 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19680 > Project: Cassandra > Issue Type: Improvement > Components: Client/java-driver >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > > The maven badge needs to be updated from com.datastax.oss to > org.apache.cassandra. Also add a license badge. -- 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-19680) Update URL in Java Driver README.md maven badge
[ https://issues.apache.org/jira/browse/CASSANDRA-19680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19680: --- Reviewers: Andy Tolbert Status: Review In Progress (was: Needs Committer) > Update URL in Java Driver README.md maven badge > --- > > Key: CASSANDRA-19680 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19680 > Project: Cassandra > Issue Type: Improvement > Components: Client/java-driver >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > > The maven badge needs to be updated from com.datastax.oss to > org.apache.cassandra. Also add a license badge. -- 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-19680) Update URL in Java Driver README.md maven badge
[ https://issues.apache.org/jira/browse/CASSANDRA-19680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19680: --- Status: Needs Committer (was: Patch Available) > Update URL in Java Driver README.md maven badge > --- > > Key: CASSANDRA-19680 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19680 > Project: Cassandra > Issue Type: Improvement > Components: Client/java-driver >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > > The maven badge needs to be updated from com.datastax.oss to > org.apache.cassandra. Also add a license badge. -- 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-19628) Correct testing instructions on the website
[
https://issues.apache.org/jira/browse/CASSANDRA-19628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17853006#comment-17853006
]
Brad Schoening commented on CASSANDRA-19628:
(y)
> Correct testing instructions on the website
> ---
>
> Key: CASSANDRA-19628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19628
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Documentation and Website
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.0.31, 4.0.14, 4.1.6, 5.0-beta2, 5.0, 5.1
>
>
> At https://cassandra.apache.org/_/development/testing.html it says to issue
> these statements for cqlsh tests:
> {noformat}
> ccm updateconf "enable_user_defined_functions: true"
> ccm updateconf "enable_scripted_user_defined_functions: true"
> ccm updateconf "cdc_enabled: true"
> {noformat}
> But these actually break the configuration so it won't start.
--
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-19628) Correct testing instructions on the website
[
https://issues.apache.org/jira/browse/CASSANDRA-19628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852975#comment-17852975
]
Brad Schoening edited comment on CASSANDRA-19628 at 6/7/24 1:04 AM:
[~brandon.williams] there is a lingering mention of Nose tests at the beginning
of testing.adoc:
{quote}*[CQLSH
tests|https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/testing.adoc#cqlsh_tests]*
- CQLSH tests are Python tests written with the Nose test framework.
{quote}
was (Author: bschoeni):
[~brandon.williams] there is a lingering mention of Nose tests here in
testing.adoc:
{quote}*[CQLSH
tests|https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/testing.adoc#cqlsh_tests]*
- CQLSH tests are Python tests written with the Nose test framework.
{quote}
> Correct testing instructions on the website
> ---
>
> Key: CASSANDRA-19628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19628
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Documentation and Website
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.0.31, 4.0.14, 4.1.6, 5.0-beta2, 5.0, 5.1
>
>
> At https://cassandra.apache.org/_/development/testing.html it says to issue
> these statements for cqlsh tests:
> {noformat}
> ccm updateconf "enable_user_defined_functions: true"
> ccm updateconf "enable_scripted_user_defined_functions: true"
> ccm updateconf "cdc_enabled: true"
> {noformat}
> But these actually break the configuration so it won't start.
--
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-19628) Correct testing instructions on the website
[
https://issues.apache.org/jira/browse/CASSANDRA-19628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852975#comment-17852975
]
Brad Schoening commented on CASSANDRA-19628:
[~brandon.williams] there is a lingering mention of Nose tests here in
testing.adoc:
{quote}*[CQLSH
tests|https://github.com/apache/cassandra-website/blob/trunk/site-content/source/modules/ROOT/pages/development/testing.adoc#cqlsh_tests]*
- CQLSH tests are Python tests written with the Nose test framework.
{quote}
> Correct testing instructions on the website
> ---
>
> Key: CASSANDRA-19628
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19628
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Documentation and Website
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 3.0.31, 4.0.14, 4.1.6, 5.0-beta2, 5.0, 5.1
>
>
> At https://cassandra.apache.org/_/development/testing.html it says to issue
> these statements for cqlsh tests:
> {noformat}
> ccm updateconf "enable_user_defined_functions: true"
> ccm updateconf "enable_scripted_user_defined_functions: true"
> ccm updateconf "cdc_enabled: true"
> {noformat}
> But these actually break the configuration so it won't start.
--
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-18762) Repair triggers OOM with direct buffer memory
[
https://issues.apache.org/jira/browse/CASSANDRA-18762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852522#comment-17852522
]
Brad Schoening commented on CASSANDRA-18762:
[~brandon.williams] we haven't deployed 4.1.5 in production yet, which is where
we had seen issues, but it seems promising.
> Repair triggers OOM with direct buffer memory
> -
>
> Key: CASSANDRA-18762
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18762
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
>Reporter: Brad Schoening
>Priority: Normal
> Labels: OutOfMemoryError
> Attachments: Cluster-dm-metrics-1.PNG,
> image-2023-12-06-15-28-05-459.png, image-2023-12-06-15-29-31-491.png,
> image-2023-12-06-15-58-55-007.png
>
>
> We are seeing repeated failures of nodes with 16GB of heap on a VM with 32GB
> of physical RAM due to direct memory. This seems to be related to
> CASSANDRA-15202 which moved Merkel trees off-heap in 4.0. Using Cassandra
> 4.0.6 with Java 11.
> {noformat}
> 2023-08-09 04:30:57,470 [INFO ] [AntiEntropyStage:1] cluster_id=101
> ip_address=169.0.0.1 RepairSession.java:202 - [repair
> #5e55a3b0-366d-11ee-a644-d91df26add5e] Received merkle tree for table_a from
> /169.102.200.241:7000
> 2023-08-09 04:30:57,567 [INFO ] [AntiEntropyStage:1] cluster_id=101
> ip_address=169.0.0.1 RepairSession.java:202 - [repair
> #5e0d2900-366d-11ee-a644-d91df26add5e] Received merkle tree for table_b from
> /169.93.192.29:7000
> 2023-08-09 04:30:57,568 [INFO ] [AntiEntropyStage:1] cluster_id=101
> ip_address=169.0.0.1 RepairSession.java:202 - [repair
> #5e1dcad0-366d-11ee-a644-d91df26add5e] Received merkle tree for table_c from
> /169.104.171.134:7000
> 2023-08-09 04:30:57,591 [INFO ] [AntiEntropyStage:1] cluster_id=101
> ip_address=169.0.0.1 RepairSession.java:202 - [repair
> #5e69a0e0-366d-11ee-a644-d91df26add5e] Received merkle tree for table_b from
> /169.79.232.67:7000
> 2023-08-09 04:30:57,876 [INFO ] [Service Thread] cluster_id=101
> ip_address=169.0.0.1 GCInspector.java:294 - G1 Old Generation GC in 282ms.
> Compressed Class Space: 8444560 -> 8372152; G1 Eden Space: 7809794048 -> 0;
> G1 Old Gen: 1453478400 -> 820942800; G1 Survivor Space: 419430400 -> 0;
> Metaspace: 80411136 -> 80176528
> 2023-08-09 04:30:58,387 [ERROR] [AntiEntropyStage:1] cluster_id=101
> ip_address=169.0.0.1 JVMStabilityInspector.java:102 - OutOfMemory error
> letting the JVM handle the error:
> java.lang.OutOfMemoryError: Direct buffer memory
> at java.base/java.nio.Bits.reserveMemory(Bits.java:175)
> at java.base/java.nio.DirectByteBuffer.(DirectByteBuffer.java:118)
> at java.base/java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:318)
> at org.apache.cassandra.utils.MerkleTree.allocate(MerkleTree.java:742)
> at
> org.apache.cassandra.utils.MerkleTree.deserializeOffHeap(MerkleTree.java:780)
> at org.apache.cassandra.utils.MerkleTree.deserializeTree(MerkleTree.java:751)
> at org.apache.cassandra.utils.MerkleTree.deserialize(MerkleTree.java:720)
> at org.apache.cassandra.utils.MerkleTree.deserialize(MerkleTree.java:698)
> at
> org.apache.cassandra.utils.MerkleTrees$MerkleTreesSerializer.deserialize(MerkleTrees.java:416)
> at
> org.apache.cassandra.repair.messages.ValidationResponse$1.deserialize(ValidationResponse.java:100)
> at
> org.apache.cassandra.repair.messages.ValidationResponse$1.deserialize(ValidationResponse.java:84)
> at
> org.apache.cassandra.net.Message$Serializer.deserializePost40(Message.java:782)
> at org.apache.cassandra.net.Message$Serializer.deserialize(Message.java:642)
> at
> org.apache.cassandra.net.InboundMessageHandler$LargeMessage.deserialize(InboundMessageHandler.java:364)
> at
> org.apache.cassandra.net.InboundMessageHandler$LargeMessage.access$1100(InboundMessageHandler.java:317)
> at
> org.apache.cassandra.net.InboundMessageHandler$ProcessLargeMessage.provideMessage(InboundMessageHandler.java:504)
> at
> org.apache.cassandra.net.InboundMessageHandler$ProcessMessage.run(InboundMessageHandler.java:429)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:834)no* further _formatting_ is
> done here{noformat}
>
> -XX:+AlwaysPreTouch
> -XX:+CrashOnOutOfMemoryError
> -XX:+ExitOnOutOfMemoryError
> -XX:+HeapDumpOnOutOfMemoryError
> -XX:+ParallelRefProcEnabled
> -XX:+PerfDisableSharedMem
> -XX:+ResizeTLAB
[jira] [Commented] (CASSANDRA-18762) Repair triggers OOM with direct buffer memory
[
https://issues.apache.org/jira/browse/CASSANDRA-18762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852270#comment-17852270
]
Brad Schoening commented on CASSANDRA-18762:
Note, using the JVM option
{code:java}
-Dio.netty.leakDetection.level=advanced{code}
might help to diagnose this.
> Repair triggers OOM with direct buffer memory
> -
>
> Key: CASSANDRA-18762
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18762
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Repair
>Reporter: Brad Schoening
>Priority: Normal
> Labels: OutOfMemoryError
> Attachments: Cluster-dm-metrics-1.PNG,
> image-2023-12-06-15-28-05-459.png, image-2023-12-06-15-29-31-491.png,
> image-2023-12-06-15-58-55-007.png
>
>
> We are seeing repeated failures of nodes with 16GB of heap on a VM with 32GB
> of physical RAM due to direct memory. This seems to be related to
> CASSANDRA-15202 which moved Merkel trees off-heap in 4.0. Using Cassandra
> 4.0.6 with Java 11.
> {noformat}
> 2023-08-09 04:30:57,470 [INFO ] [AntiEntropyStage:1] cluster_id=101
> ip_address=169.0.0.1 RepairSession.java:202 - [repair
> #5e55a3b0-366d-11ee-a644-d91df26add5e] Received merkle tree for table_a from
> /169.102.200.241:7000
> 2023-08-09 04:30:57,567 [INFO ] [AntiEntropyStage:1] cluster_id=101
> ip_address=169.0.0.1 RepairSession.java:202 - [repair
> #5e0d2900-366d-11ee-a644-d91df26add5e] Received merkle tree for table_b from
> /169.93.192.29:7000
> 2023-08-09 04:30:57,568 [INFO ] [AntiEntropyStage:1] cluster_id=101
> ip_address=169.0.0.1 RepairSession.java:202 - [repair
> #5e1dcad0-366d-11ee-a644-d91df26add5e] Received merkle tree for table_c from
> /169.104.171.134:7000
> 2023-08-09 04:30:57,591 [INFO ] [AntiEntropyStage:1] cluster_id=101
> ip_address=169.0.0.1 RepairSession.java:202 - [repair
> #5e69a0e0-366d-11ee-a644-d91df26add5e] Received merkle tree for table_b from
> /169.79.232.67:7000
> 2023-08-09 04:30:57,876 [INFO ] [Service Thread] cluster_id=101
> ip_address=169.0.0.1 GCInspector.java:294 - G1 Old Generation GC in 282ms.
> Compressed Class Space: 8444560 -> 8372152; G1 Eden Space: 7809794048 -> 0;
> G1 Old Gen: 1453478400 -> 820942800; G1 Survivor Space: 419430400 -> 0;
> Metaspace: 80411136 -> 80176528
> 2023-08-09 04:30:58,387 [ERROR] [AntiEntropyStage:1] cluster_id=101
> ip_address=169.0.0.1 JVMStabilityInspector.java:102 - OutOfMemory error
> letting the JVM handle the error:
> java.lang.OutOfMemoryError: Direct buffer memory
> at java.base/java.nio.Bits.reserveMemory(Bits.java:175)
> at java.base/java.nio.DirectByteBuffer.(DirectByteBuffer.java:118)
> at java.base/java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:318)
> at org.apache.cassandra.utils.MerkleTree.allocate(MerkleTree.java:742)
> at
> org.apache.cassandra.utils.MerkleTree.deserializeOffHeap(MerkleTree.java:780)
> at org.apache.cassandra.utils.MerkleTree.deserializeTree(MerkleTree.java:751)
> at org.apache.cassandra.utils.MerkleTree.deserialize(MerkleTree.java:720)
> at org.apache.cassandra.utils.MerkleTree.deserialize(MerkleTree.java:698)
> at
> org.apache.cassandra.utils.MerkleTrees$MerkleTreesSerializer.deserialize(MerkleTrees.java:416)
> at
> org.apache.cassandra.repair.messages.ValidationResponse$1.deserialize(ValidationResponse.java:100)
> at
> org.apache.cassandra.repair.messages.ValidationResponse$1.deserialize(ValidationResponse.java:84)
> at
> org.apache.cassandra.net.Message$Serializer.deserializePost40(Message.java:782)
> at org.apache.cassandra.net.Message$Serializer.deserialize(Message.java:642)
> at
> org.apache.cassandra.net.InboundMessageHandler$LargeMessage.deserialize(InboundMessageHandler.java:364)
> at
> org.apache.cassandra.net.InboundMessageHandler$LargeMessage.access$1100(InboundMessageHandler.java:317)
> at
> org.apache.cassandra.net.InboundMessageHandler$ProcessLargeMessage.provideMessage(InboundMessageHandler.java:504)
> at
> org.apache.cassandra.net.InboundMessageHandler$ProcessMessage.run(InboundMessageHandler.java:429)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:834)no* further _formatting_ is
> done here{noformat}
>
> -XX:+AlwaysPreTouch
> -XX:+CrashOnOutOfMemoryError
> -XX:+ExitOnOutOfMemoryError
> -XX:+HeapDumpOnOutOfMemoryError
> -XX:+ParallelRefProcEnabled
> -XX:+PerfDisableSharedMem
> -XX:+ResizeTLAB
>
[jira] [Commented] (CASSANDRA-19022) Nodetool gcstats correctly displays Direct Memory usage and supports printing in table format
[
https://issues.apache.org/jira/browse/CASSANDRA-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852262#comment-17852262
]
Brad Schoening commented on CASSANDRA-19022:
This may be a quirk of Netty when maxDirectMemory() isn't set it doesn't count
it?
{code:java}
public static long usedDirectMemory()
Returns the current memory reserved for direct buffer allocation. This method
returns -1 in case that a value is not available.
{code}
[io.netty.util.internal.PlatformDependent|https://netty.io/4.1/api/io/netty/util/internal/PlatformDependent.html]
See also [Netty issue #11895|https://github.com/netty/netty/issues/11895]
{{Other articles suggest PooledByteBufAllocator.metric()}} and
{{UnpooledByteBufAllocator.metric() may have the actual numbers.}}
> Nodetool gcstats correctly displays Direct Memory usage and supports printing
> in table format
> -
>
> Key: CASSANDRA-19022
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19022
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/nodetool
>Reporter: Brad Schoening
>Assignee: Ling Mao
>Priority: Normal
> Fix For: 5.x
>
>
> If {{io.netty.maxDirectMemory}} is not specified, Netty defaults the limit to
> the max heap size. Thus, direct memory in use can be significant.
> However, trying this on two different platform and the result returned in
> gcstats is always -1:
> {noformat}
> Interval (ms) Max GC Elapsed (ms)Total GC Elapsed (ms)Stdev GC Elapsed (ms)
> GC Reclaimed (MB) Collections Direct Memory Bytes
> 2792770717 274 665186 54
> 412762880890246120 -1{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] [Commented] (CASSANDRA-19022) Nodetool gcstats correctly displays Direct Memory usage and supports printing in table format
[
https://issues.apache.org/jira/browse/CASSANDRA-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852259#comment-17852259
]
Brad Schoening commented on CASSANDRA-19022:
[~maoling] for a bug, shouldn't the description be 'incorrectly' displays?
> Nodetool gcstats correctly displays Direct Memory usage and supports printing
> in table format
> -
>
> Key: CASSANDRA-19022
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19022
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/nodetool
>Reporter: Brad Schoening
>Assignee: Ling Mao
>Priority: Normal
> Fix For: 5.x
>
>
> If {{io.netty.maxDirectMemory}} is not specified, Netty defaults the limit to
> the max heap size. Thus, direct memory in use can be significant.
> However, trying this on two different platform and the result returned in
> gcstats is always -1:
> {noformat}
> Interval (ms) Max GC Elapsed (ms)Total GC Elapsed (ms)Stdev GC Elapsed (ms)
> GC Reclaimed (MB) Collections Direct Memory Bytes
> 2792770717 274 665186 54
> 412762880890246120 -1{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] [Updated] (CASSANDRA-19022) Nodetool gcstats correctly displays Direct Memory usage and supports printing in table format
[
https://issues.apache.org/jira/browse/CASSANDRA-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening updated CASSANDRA-19022:
---
Summary: Nodetool gcstats correctly displays Direct Memory usage and
supports printing in table format (was: Nodetool gcstats correctly displays
Direct Memory usage)
> Nodetool gcstats correctly displays Direct Memory usage and supports printing
> in table format
> -
>
> Key: CASSANDRA-19022
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19022
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/nodetool
>Reporter: Brad Schoening
>Assignee: Ling Mao
>Priority: Normal
> Fix For: 5.x
>
>
> If {{io.netty.maxDirectMemory}} is not specified, Netty defaults the limit to
> the max heap size. Thus, direct memory in use can be significant.
> However, trying this on two different platform and the result returned in
> gcstats is always -1:
> {noformat}
> Interval (ms) Max GC Elapsed (ms)Total GC Elapsed (ms)Stdev GC Elapsed (ms)
> GC Reclaimed (MB) Collections Direct Memory Bytes
> 2792770717 274 665186 54
> 412762880890246120 -1{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] [Updated] (CASSANDRA-19022) Nodetool gcstats correctly displays Direct Memory usage
[
https://issues.apache.org/jira/browse/CASSANDRA-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening updated CASSANDRA-19022:
---
Summary: Nodetool gcstats correctly displays Direct Memory usage (was:
Nodetool gcstats incorrectly displays Direct Memory usage)
> Nodetool gcstats correctly displays Direct Memory usage
> ---
>
> Key: CASSANDRA-19022
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19022
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/nodetool
>Reporter: Brad Schoening
>Assignee: Ling Mao
>Priority: Normal
> Fix For: 5.x
>
>
> If {{io.netty.maxDirectMemory}} is not specified, Netty defaults the limit to
> the max heap size. Thus, direct memory in use can be significant.
> However, trying this on two different platform and the result returned in
> gcstats is always -1:
> {noformat}
> Interval (ms) Max GC Elapsed (ms)Total GC Elapsed (ms)Stdev GC Elapsed (ms)
> GC Reclaimed (MB) Collections Direct Memory Bytes
> 2792770717 274 665186 54
> 412762880890246120 -1{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] [Updated] (CASSANDRA-19022) Nodetool gcstats incorrectly displays Direct Memory usage
[
https://issues.apache.org/jira/browse/CASSANDRA-19022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brad Schoening updated CASSANDRA-19022:
---
Summary: Nodetool gcstats incorrectly displays Direct Memory usage (was:
Nodetool gcstats correctly displays Direct Memory usage and supports printing
in table format)
> Nodetool gcstats incorrectly displays Direct Memory usage
> -
>
> Key: CASSANDRA-19022
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19022
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/nodetool
>Reporter: Brad Schoening
>Assignee: Ling Mao
>Priority: Normal
> Fix For: 5.x
>
>
> If {{io.netty.maxDirectMemory}} is not specified, Netty defaults the limit to
> the max heap size. Thus, direct memory in use can be significant.
> However, trying this on two different platform and the result returned in
> gcstats is always -1:
> {noformat}
> Interval (ms) Max GC Elapsed (ms)Total GC Elapsed (ms)Stdev GC Elapsed (ms)
> GC Reclaimed (MB) Collections Direct Memory Bytes
> 2792770717 274 665186 54
> 412762880890246120 -1{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] [Updated] (CASSANDRA-19680) Update URL in Java Driver README.md maven badge
[ https://issues.apache.org/jira/browse/CASSANDRA-19680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19680: --- Summary: Update URL in Java Driver README.md maven badge (was: Update URL in README.md maven badge) > Update URL in Java Driver README.md maven badge > --- > > Key: CASSANDRA-19680 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19680 > Project: Cassandra > Issue Type: Improvement > Components: Client/java-driver >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > > The maven badge needs to be updated from com.datastax.oss to > org.apache.cassandra. Also add a license badge. -- 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-19680) Update URL in Java Driver README.md maven badge
[ https://issues.apache.org/jira/browse/CASSANDRA-19680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19680: --- Test and Documentation Plan: Documentation only change Status: Patch Available (was: In Progress) > Update URL in Java Driver README.md maven badge > --- > > Key: CASSANDRA-19680 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19680 > Project: Cassandra > Issue Type: Improvement > Components: Client/java-driver >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > > The maven badge needs to be updated from com.datastax.oss to > org.apache.cassandra. Also add a license badge. -- 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-19680) Update URL in README.md maven badge
[ https://issues.apache.org/jira/browse/CASSANDRA-19680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19680: --- Change Category: Code Clarity Complexity: Low Hanging Fruit Status: Open (was: Triage Needed) > Update URL in README.md maven badge > --- > > Key: CASSANDRA-19680 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19680 > Project: Cassandra > Issue Type: Improvement > Components: Client/java-driver >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > > The maven badge needs to be updated from com.datastax.oss to > org.apache.cassandra. Also add a license badge. -- 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-19680) Update URL in README.md maven badge
Brad Schoening created CASSANDRA-19680: -- Summary: Update URL in README.md maven badge Key: CASSANDRA-19680 URL: https://issues.apache.org/jira/browse/CASSANDRA-19680 Project: Cassandra Issue Type: Improvement Components: Client/java-driver Reporter: Brad Schoening The maven badge needs to be updated from com.datastax.oss to org.apache.cassandra. Also add a license badge. -- 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-19680) Update URL in README.md maven badge
[ https://issues.apache.org/jira/browse/CASSANDRA-19680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening reassigned CASSANDRA-19680: -- Assignee: Brad Schoening > Update URL in README.md maven badge > --- > > Key: CASSANDRA-19680 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19680 > Project: Cassandra > Issue Type: Improvement > Components: Client/java-driver >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Normal > > The maven badge needs to be updated from com.datastax.oss to > org.apache.cassandra. Also add a license badge. -- 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-19671) Nodetool tabestats: add keyspace space used and table r/w ratio
[ https://issues.apache.org/jira/browse/CASSANDRA-19671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17852075#comment-17852075 ] Brad Schoening commented on CASSANDRA-19671: [~arkn98] I ran across a [stackoverflow question|https://dba.stackexchange.com/questions/326997/how-do-i-get-the-total-number-of-sstables-with-nodetool/339981#339981] asking about the total count of SSTables. This is relevant to the number of file handles in use. It would be good to add to the rollup keyspace level metrics: * SSTable count * Off heap memory used > Nodetool tabestats: add keyspace space used and table r/w ratio > --- > > Key: CASSANDRA-19671 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19671 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Brad Schoening >Assignee: Arun Ganesh >Priority: Low > Attachments: plaintext-humanreadable.txt, plaintext.txt > > Time Spent: 10m > Remaining Estimate: 0h > > Nodetool tabestats reports the space used live and total per table, but not > for the entire keyspace. This would be useful information. > Also, in the table level stats, it would be useful to have the read/write > ratio. This metric is important in choosing compaction strategies such as > LCS. -- 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-19671) Nodetool tabestats: add keyspace space used and table r/w ratio
[ https://issues.apache.org/jira/browse/CASSANDRA-19671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851846#comment-17851846 ] Brad Schoening edited comment on CASSANDRA-19671 at 6/3/24 11:56 PM: - [~arkn98] could you attach a sample output? I don't know enough about the Nodetool codebase to really review the code. was (Author: bschoeni): [~arkn98] could you attach a sample output? I don't know enough about the Nodetool codebase to really review it. > Nodetool tabestats: add keyspace space used and table r/w ratio > --- > > Key: CASSANDRA-19671 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19671 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Brad Schoening >Assignee: Arun Ganesh >Priority: Low > Attachments: plaintext-humanreadable.txt, plaintext.txt > > Time Spent: 10m > Remaining Estimate: 0h > > Nodetool tabestats reports the space used live and total per table, but not > for the entire keyspace. This would be useful information. > Also, in the table level stats, it would be useful to have the read/write > ratio. This metric is important in choosing compaction strategies such as > LCS. -- 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-19671) Nodetool tabestats: add keyspace space used and table r/w ratio
[ https://issues.apache.org/jira/browse/CASSANDRA-19671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851846#comment-17851846 ] Brad Schoening commented on CASSANDRA-19671: [~arkn98] could you attach a sample output? I don't know enough about the Nodetool codebase to really review it. > Nodetool tabestats: add keyspace space used and table r/w ratio > --- > > Key: CASSANDRA-19671 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19671 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Brad Schoening >Assignee: Arun Ganesh >Priority: Low > Time Spent: 10m > Remaining Estimate: 0h > > Nodetool tabestats reports the space used live and total per table, but not > for the entire keyspace. This would be useful information. > Also, in the table level stats, it would be useful to have the read/write > ratio. This metric is important in choosing compaction strategies such as > LCS. -- 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-19640) Enhance documentation on storage engine with leading summary
[ https://issues.apache.org/jira/browse/CASSANDRA-19640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851844#comment-17851844 ] Brad Schoening commented on CASSANDRA-19640: [~brandon.williams] [~paulo] could you review this doc change also > Enhance documentation on storage engine with leading summary > > > Key: CASSANDRA-19640 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19640 > Project: Cassandra > Issue Type: Improvement > Components: Documentation >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Low > > The storage engine > [documentation|https://github.com/apache/cassandra/blob/trunk/doc/modules/cassandra/pages/architecture/storage-engine.adoc] > would benefit from an abstract or summary which mentions key points that it > uses a Log-structured merge (LSM) tree design, is write-oriented, and relies > upon bloom filters (not B-trees) to optimize the read path. -- 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-19375) Link in docs to Achilles Java Driver links to malicious site
[ https://issues.apache.org/jira/browse/CASSANDRA-19375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851842#comment-17851842 ] Brad Schoening edited comment on CASSANDRA-19375 at 6/3/24 11:09 PM: - [~brandon.williams] [~polandll] I found a lot of the drivers mentioned were unsupported and/or unmaintained for the last 4+ years and removed a bunch. Java * [Achilles|http://achilles.archinnov.info/[Achilles]] * [Astyanax|https://github.com/Netflix/astyanax/wiki/Getting-Started[Astyanax]] * [Casser|https://github.com/noorq/casser[Casser]] * [Datastax|https://github.com/datastax/java-driver[Datastax] Java driver] --> updated URL and renamed Java Driver for Apache Cassandra * [Kundera|https://github.com/Impetus/kundera] C# * [Cassandra Sharp|https://github.com/pchalamet/cassandra-sharp] * [Fluent|https://github.com/managedfusion/fluentcassandra] PHP * [CQL|http://code.google.com/a/apache-extras.org/p/cassandra-pdo] * [PHP-Cassandra|https://github.com/aparkhomenko/php-cassandra] * [PHP Library for PHP|https://github.com/duoshuo/php-cassandra] C# * [libQTCassandra|http://sourceforge.net/projects/libqtcassandra] Go * [CQLc|https://github.com/relops/cqlc] * [Gocassa|https://github.com/hailocab/gocassa] was (Author: bschoeni): [~brandon.williams] [~polandll] I found a lot of the drivers mentioned were unsupported and/or unmaintained for the last 4+ years and removed a bunch. Java * [http://achilles.archinnov.info/ [Achilles|http://achilles.archinnov.info/[Achilles]] * [https://github.com/Netflix/astyanax/wiki/Getting-Started [Astyanax|https://github.com/Netflix/astyanax/wiki/Getting-Started[Astyanax]] * [https://github.com/noorq/casser [Casser|https://github.com/noorq/casser[Casser]] * [https://github.com/datastax/java-driver [Datastax|https://github.com/datastax/java-driver[Datastax] Java driver] --> updated URL and renamed Java Driver for Apache Cassandra * [https://github.com/Impetus/kundera [Kundera|https://github.com/Impetus/kundera[Kundera]] C# * [https://github.com/pchalamet/cassandra-sharp [Cassandra|https://github.com/pchalamet/cassandra-sharp[Cassandra] Sharp] * [https://github.com/managedfusion/fluentcassandra [Fluent|https://github.com/managedfusion/fluentcassandra[Fluent] Cassandra PHP * [http://code.google.com/a/apache-extras.org/p/cassandra-pdo [CQL|http://code.google.com/a/apache-extras.org/p/cassandra-pdo[CQL] | PHP] * [https://github.com/aparkhomenko/php-cassandra [PHP-Cassandra|https://github.com/aparkhomenko/php-cassandra[PHP-Cassandra]] * [https://github.com/duoshuo/php-cassandra [PHP|https://github.com/duoshuo/php-cassandra[PHP] Library for Cassandra] C# [http://sourceforge.net/projects/libqtcassandra [libQTCassandra]|http://sourceforge.net/projects/libqtcassandra[libQTCassandra]] Go * [https://github.com/relops/cqlc [CQLc|https://github.com/relops/cqlc[CQLc]] * [https://github.com/hailocab/gocassa [Gocassa]|https://github.com/hailocab/gocassa[Gocassa]*] > Link in docs to Achilles Java Driver links to malicious site > > > Key: CASSANDRA-19375 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19375 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: PJ Fanning >Assignee: Brad Schoening >Priority: Normal > > https://cassandra.apache.org/doc/4.1/cassandra/getting_started/drivers.html#java > The Achilles link looks dangerous. I tried it and it looked like the link has > been taken over by a malicious user. -- 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-19375) Link in docs to Achilles Java Driver links to malicious site
[ https://issues.apache.org/jira/browse/CASSANDRA-19375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851842#comment-17851842 ] Brad Schoening edited comment on CASSANDRA-19375 at 6/3/24 11:01 PM: - [~brandon.williams] [~polandll] I found a lot of the drivers mentioned were unsupported and/or unmaintained for the last 4+ years and removed a bunch. Java * [http://achilles.archinnov.info/ [Achilles|http://achilles.archinnov.info/[Achilles]] * [https://github.com/Netflix/astyanax/wiki/Getting-Started [Astyanax|https://github.com/Netflix/astyanax/wiki/Getting-Started[Astyanax]] * [https://github.com/noorq/casser [Casser|https://github.com/noorq/casser[Casser]] * [https://github.com/datastax/java-driver [Datastax|https://github.com/datastax/java-driver[Datastax] Java driver] --> updated URL and renamed Java Driver for Apache Cassandra * [https://github.com/Impetus/kundera [Kundera|https://github.com/Impetus/kundera[Kundera]] C# * [https://github.com/pchalamet/cassandra-sharp [Cassandra|https://github.com/pchalamet/cassandra-sharp[Cassandra] Sharp] * [https://github.com/managedfusion/fluentcassandra [Fluent|https://github.com/managedfusion/fluentcassandra[Fluent] Cassandra PHP * [http://code.google.com/a/apache-extras.org/p/cassandra-pdo [CQL|http://code.google.com/a/apache-extras.org/p/cassandra-pdo[CQL] | PHP] * [https://github.com/aparkhomenko/php-cassandra [PHP-Cassandra|https://github.com/aparkhomenko/php-cassandra[PHP-Cassandra]] * [https://github.com/duoshuo/php-cassandra [PHP|https://github.com/duoshuo/php-cassandra[PHP] Library for Cassandra] C# [http://sourceforge.net/projects/libqtcassandra [libQTCassandra]|http://sourceforge.net/projects/libqtcassandra[libQTCassandra]] Go * [https://github.com/relops/cqlc [CQLc|https://github.com/relops/cqlc[CQLc]] * [https://github.com/hailocab/gocassa [Gocassa]|https://github.com/hailocab/gocassa[Gocassa]*] was (Author: bschoeni): [~brandon.williams] [~polandll] I found a lot of the drivers mentioned were unsupported and/or unmaintained for the last 4+ years and removed a bunch. Java * http://achilles.archinnov.info/[Achilles] * https://github.com/Netflix/astyanax/wiki/Getting-Started[Astyanax] * https://github.com/noorq/casser[Casser] * https://github.com/datastax/java-driver[Datastax Java driver] --> updated URL and renamed Java Driver for Apache Cassandra * https://github.com/Impetus/kundera[Kundera] C# * https://github.com/pchalamet/cassandra-sharp[Cassandra Sharp] * https://github.com/managedfusion/fluentcassandra[Fluent Cassandra PHP * http://code.google.com/a/apache-extras.org/p/cassandra-pdo[CQL | PHP] * https://github.com/aparkhomenko/php-cassandra[PHP-Cassandra] * https://github.com/duoshuo/php-cassandra[PHP Library for Cassandra] C# [http://sourceforge.net/projects/libqtcassandra[libQTCassandra]] Go * https://github.com/relops/cqlc[CQLc] * https://github.com/hailocab/gocassa[Gocassa]* https://github.com/relops/cqlc[CQLc] > Link in docs to Achilles Java Driver links to malicious site > > > Key: CASSANDRA-19375 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19375 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: PJ Fanning >Assignee: Brad Schoening >Priority: Normal > > https://cassandra.apache.org/doc/4.1/cassandra/getting_started/drivers.html#java > The Achilles link looks dangerous. I tried it and it looked like the link has > been taken over by a malicious user. -- 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-19375) Link in docs to Achilles Java Driver links to malicious site
[ https://issues.apache.org/jira/browse/CASSANDRA-19375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19375: --- Test and Documentation Plan: documentation only change Status: Patch Available (was: In Progress) > Link in docs to Achilles Java Driver links to malicious site > > > Key: CASSANDRA-19375 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19375 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: PJ Fanning >Assignee: Brad Schoening >Priority: Normal > > https://cassandra.apache.org/doc/4.1/cassandra/getting_started/drivers.html#java > The Achilles link looks dangerous. I tried it and it looked like the link has > been taken over by a malicious user. -- 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-19375) Link in docs to Achilles Java Driver links to malicious site
[ https://issues.apache.org/jira/browse/CASSANDRA-19375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851842#comment-17851842 ] Brad Schoening commented on CASSANDRA-19375: [~brandon.williams] [~polandll] I found a lot of the drivers mentioned were unsupported and/or unmaintained for the last 4+ years and removed a bunch. Java * http://achilles.archinnov.info/[Achilles] * https://github.com/Netflix/astyanax/wiki/Getting-Started[Astyanax] * https://github.com/noorq/casser[Casser] * https://github.com/datastax/java-driver[Datastax Java driver] --> updated URL and renamed Java Driver for Apache Cassandra * https://github.com/Impetus/kundera[Kundera] C# * https://github.com/pchalamet/cassandra-sharp[Cassandra Sharp] * https://github.com/managedfusion/fluentcassandra[Fluent Cassandra PHP * http://code.google.com/a/apache-extras.org/p/cassandra-pdo[CQL | PHP] * https://github.com/aparkhomenko/php-cassandra[PHP-Cassandra] * https://github.com/duoshuo/php-cassandra[PHP Library for Cassandra] C# [http://sourceforge.net/projects/libqtcassandra[libQTCassandra]] Go * https://github.com/relops/cqlc[CQLc] * https://github.com/hailocab/gocassa[Gocassa]* https://github.com/relops/cqlc[CQLc] > Link in docs to Achilles Java Driver links to malicious site > > > Key: CASSANDRA-19375 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19375 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: PJ Fanning >Assignee: Brad Schoening >Priority: Normal > > https://cassandra.apache.org/doc/4.1/cassandra/getting_started/drivers.html#java > The Achilles link looks dangerous. I tried it and it looked like the link has > been taken over by a malicious user. -- 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-19375) Link in docs to Achilles Java Driver links to malicious site
[ https://issues.apache.org/jira/browse/CASSANDRA-19375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening reassigned CASSANDRA-19375: -- Assignee: Brad Schoening (was: Lorina Poland) > Link in docs to Achilles Java Driver links to malicious site > > > Key: CASSANDRA-19375 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19375 > Project: Cassandra > Issue Type: Task > Components: Documentation >Reporter: PJ Fanning >Assignee: Brad Schoening >Priority: Normal > > https://cassandra.apache.org/doc/4.1/cassandra/getting_started/drivers.html#java > The Achilles link looks dangerous. I tried it and it looked like the link has > been taken over by a malicious user. -- 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-15873) Update Netty 4.0.44 -> 4.1.50 (fix security/performance issues)
[ https://issues.apache.org/jira/browse/CASSANDRA-15873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-15873: --- Resolution: Fixed Status: Resolved (was: Open) > Update Netty 4.0.44 -> 4.1.50 (fix security/performance issues) > --- > > Key: CASSANDRA-15873 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15873 > Project: Cassandra > Issue Type: Task > Components: Dependencies >Reporter: Matt Davis >Priority: Normal > Fix For: 3.11.x > > Attachments: dependency-check-report.html, unittest_netty.log > > > See https://issues.apache.org/jira/browse/CASSANDRA-15868 for the same issue > on 4.0 / trunk. Attached is an OWASP dependency report for Netty 4.0.44, > which identifies 3 of the same vulnerabilities as above. > > Additionally, 4.1.50 contains aarch64 native libraries which can improve > performance on ARM processors. > -- 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-19462) cqlsh does not autocomplete table names in MacOS
[
https://issues.apache.org/jira/browse/CASSANDRA-19462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846453#comment-17846453
]
Brad Schoening edited comment on CASSANDRA-19462 at 6/3/24 8:47 PM:
[~smiklosovic] I've not been able to reproduce this.
was (Author: bschoeni):
@stefanI've not been able to reproduce this.
> cqlsh does not autocomplete table names in MacOS
>
>
> Key: CASSANDRA-19462
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19462
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Stefan Miklosovic
>Assignee: Brad Schoening
>Priority: Normal
>
> I am on MacBook with Sonoma
> {code}
> $ uname -a
> Darwin stefanm-mac-0 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:59
> PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6030 arm64
> {code}
> What is interesting is that ./bin/cqlsh works but when I am tabbing like
> {code}
> select * from system_auth.
> {code}
> This does not work.
> It does work when I install cqlsh from pip though.
> I have pyreadline installed,
> I have two pythons 3.10 and 3.9.6. I installed 3.10 from brew and 3.9.6 is
> from Sonoma itself.
> Could somebody with Mac verify that tab completion works (or does not) when
> invoking ./bin/cqlsh from Cassandra?
--
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-19462) cqlsh does not autocomplete table names in MacOS
[
https://issues.apache.org/jira/browse/CASSANDRA-19462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846453#comment-17846453
]
Brad Schoening edited comment on CASSANDRA-19462 at 6/3/24 8:47 PM:
@stefanI've not been able to reproduce this.
was (Author: bschoeni):
[~smiklosovic] I've not been able to reproduce this.
> cqlsh does not autocomplete table names in MacOS
>
>
> Key: CASSANDRA-19462
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19462
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: Stefan Miklosovic
>Assignee: Brad Schoening
>Priority: Normal
>
> I am on MacBook with Sonoma
> {code}
> $ uname -a
> Darwin stefanm-mac-0 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:59
> PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6030 arm64
> {code}
> What is interesting is that ./bin/cqlsh works but when I am tabbing like
> {code}
> select * from system_auth.
> {code}
> This does not work.
> It does work when I install cqlsh from pip though.
> I have pyreadline installed,
> I have two pythons 3.10 and 3.9.6. I installed 3.10 from brew and 3.9.6 is
> from Sonoma itself.
> Could somebody with Mac verify that tab completion works (or does not) when
> invoking ./bin/cqlsh from Cassandra?
--
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-19671) Nodetool tabestats: add keyspace space used and table r/w ratio
[ https://issues.apache.org/jira/browse/CASSANDRA-19671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851602#comment-17851602 ] Brad Schoening commented on CASSANDRA-19671: [~arkn98] Yes, just the sum of the space used rolled-up to the keyspace level. And yes, if there is already a ratio calculated that's fine, it should match (local read count) / (local write count). > Nodetool tabestats: add keyspace space used and table r/w ratio > --- > > Key: CASSANDRA-19671 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19671 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Brad Schoening >Priority: Low > > Nodetool tabestats reports the space used live and total per table, but not > for the entire keyspace. This would be useful information. > Also, in the table level stats, it would be useful to have the read/write > ratio. This metric is important in choosing compaction strategies such as > LCS. -- 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-19671) Nodetool tabestats: add keyspace space used and table r/w ratio
[ https://issues.apache.org/jira/browse/CASSANDRA-19671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19671: --- Change Category: Operability Complexity: Low Hanging Fruit Priority: Low (was: Normal) Status: Open (was: Triage Needed) > Nodetool tabestats: add keyspace space used and table r/w ratio > --- > > Key: CASSANDRA-19671 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19671 > Project: Cassandra > Issue Type: Improvement > Components: Tool/nodetool >Reporter: Brad Schoening >Priority: Low > > Nodetool tabestats reports the space used live and total per table, but not > for the entire keyspace. This would be useful information. > Also, in the table level stats, it would be useful to have the read/write > ratio. This metric is important in choosing compaction strategies such as > LCS. -- 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-19150) Align values in rows in CQLSH right for numbers, left for text
[
https://issues.apache.org/jira/browse/CASSANDRA-19150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17833950#comment-17833950
]
Brad Schoening edited comment on CASSANDRA-19150 at 6/3/24 12:06 PM:
-
[~arkn98] Ok, I see your point.
Reviewing the code and you're question #1, I wonder if it would be tidier to
consolidate the formatting into a map like DEFAULT_VALUE_COLORS which maps
types to color formats. This could be generalized to a multi-value map for
types -> ( color, alignment).
For example:
{code:java}
TYPE_FORMATS = { 'default': (YELLOW, 'left'), 'text': (YELLOW, 'left'), 'int':
(GREEN, 'right')}
color, algn = TYPE_FORMATS['int']{code}
Since Python uses strings 'right' and 'left' in formatting, it might be more
consistent to use raw strings here instead of an enum.
#2 align by the type of the field sounds right. I checked psql and it simply
displays nulls as blanks.
#3 If default is normally left, user types and collections should probably be
left.
#4 how many tests are broken by this change?
was (Author: bschoeni):
[~arkn98] Ok, I see your point.
Reviewing the code and you're question #1, I wonder if it would be tidier to
consolidate the formatting into a map like DEFAULT_VALUE_COLORS which maps
types to color formats. This could be generalized to a multi-value map for
types -> ( color, alignment).
For example:
{code:java}
TYPE_FORMATS = { 'default': (YELLOW, 'left'), 'text': (YELLOW, 'left'), 'int':
(GREEN, 'right')}
color, algn = TYPE_FORMATS['int']{code}
Since Python uses 'right' and 'left', it might be more consistent to use raw
strings here instead of an enum.
#2 align by the type of the field sounds right. I checked psql and it simply
displays nulls as blanks.
#3 If default is normally left, user types and collections should probably be
left.
#4 how many tests are broken by this change?
> Align values in rows in CQLSH right for numbers, left for text
> --
>
> Key: CASSANDRA-19150
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19150
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Interpreter
>Reporter: Stefan Miklosovic
>Assignee: Arun Ganesh
>Priority: Low
> Fix For: 5.x
>
> Attachments: Screenshot 2023-12-04 at 00.38.16.png, Screenshot
> 2023-12-09 at 16.58.25.png, signature.asc, test_output.txt,
> test_output_old.txt
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *Updated* Jan 17 2024 after dev discussion
> Change CQLSH to left-align text while continue to right-align numbers. This
> will match how Postgres shell and Excel treat alignment of text and number.
> -
> *Original*
> We need to make this
> [https://github.com/apache/cassandra/blob/trunk/pylib/cqlshlib/cqlshmain.py#L1101]
> configurable so values in columns are either all on left or on right side of
> the column (basically change col.rjust to col.ljust).
> By default, it would be like it is now but there would be configuration
> property in cqlsh for that as well as a corresponding CQLSH command
> (optional), something like
> {code:java}
> ALIGNMENT LEFT|RIGHT
> {code}
> cc [~bschoeni]
--
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-19671) Nodetool tabestats: add keyspace space used and table r/w ratio
Brad Schoening created CASSANDRA-19671: -- Summary: Nodetool tabestats: add keyspace space used and table r/w ratio Key: CASSANDRA-19671 URL: https://issues.apache.org/jira/browse/CASSANDRA-19671 Project: Cassandra Issue Type: Improvement Components: Tool/nodetool Reporter: Brad Schoening Nodetool tabestats reports the space used live and total per table, but not for the entire keyspace. This would be useful information. Also, in the table level stats, it would be useful to have the read/write ratio. This metric is important in choosing compaction strategies such as LCS. -- 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-17667) Text value containing "/*" interpreted as multiline comment in cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850181#comment-17850181
]
Brad Schoening commented on CASSANDRA-17667:
I'd assume it was running nosetest because it generates the nosetest.xml
artifact.
{code:java}
- generated xml file:
/private/var/tmp/cassandra/pylib/cqlshlib/nosetests.xml
-
23
passed, 1 warning in 0.80s
{code}
The tests ran, so I've added the 4.0 PR as well.
> Text value containing "/*" interpreted as multiline comment in cqlsh
>
>
> Key: CASSANDRA-17667
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17667
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: ANOOP THOMAS
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>
> I use CQLSH command line utility to load some DDLs. The version of utility I
> use is this:
> {noformat}
> [cqlsh 6.0.0 | Cassandra 4.0.0.47 | CQL spec 3.4.5 | Native protocol
> v5]{noformat}
> Command that loads DDL.cql:
> {noformat}
> cqlsh -u username -p password cassandra.example.com 65503 --ssl -f DDL.cql
> {noformat}
> I have a line in CQL script that breaks the syntax.
> {noformat}
> INSERT into tablename (key,columnname1,columnname2) VALUES
> ('keyName','value1','/value2/*/value3');{noformat}
> {{/*}} here is interpreted as start of multi-line comment. It used to work on
> older versions of cqlsh. The error I see looks like this:
> {noformat}
> SyntaxException: line 4:2 mismatched input 'Update' expecting ')'
> (...,'value1','/value2INSERT into tablename(INSERT into tablename
> (key,columnname1,columnname2)) VALUES ('[Update]-...) SyntaxException: line
> 1:0 no viable alternative at input '(' ([(]...)
> {noformat}
> Same behavior while running in interactive mode too. {{/*}} inside a CQL
> statement should not be interpreted as start of multi-line comment.
> With schema:
> {code:java}
> CREATE TABLE tablename ( key text primary key, columnname1 text, columnname2
> text);{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-17667) Text value containing "/*" interpreted as multiline comment in cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850140#comment-17850140
]
Brad Schoening edited comment on CASSANDRA-17667 at 5/28/24 6:53 PM:
-
https://github.com/apache/cassandra/blob/cassandra-4.0/pylib/cassandra-cqlsh-tests.sh
which was changed with CASSANDRA-17293
was (Author: bschoeni):
[https://github.com/apache/cassandra/blob/trunk/pylib/cassandra-cqlsh-tests.sh]
which was changed with
[CASSANDRA-17293|https://issues.apache.org/jira/browse/CASSANDRA-17293]
> Text value containing "/*" interpreted as multiline comment in cqlsh
>
>
> Key: CASSANDRA-17667
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17667
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: ANOOP THOMAS
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>
> I use CQLSH command line utility to load some DDLs. The version of utility I
> use is this:
> {noformat}
> [cqlsh 6.0.0 | Cassandra 4.0.0.47 | CQL spec 3.4.5 | Native protocol
> v5]{noformat}
> Command that loads DDL.cql:
> {noformat}
> cqlsh -u username -p password cassandra.example.com 65503 --ssl -f DDL.cql
> {noformat}
> I have a line in CQL script that breaks the syntax.
> {noformat}
> INSERT into tablename (key,columnname1,columnname2) VALUES
> ('keyName','value1','/value2/*/value3');{noformat}
> {{/*}} here is interpreted as start of multi-line comment. It used to work on
> older versions of cqlsh. The error I see looks like this:
> {noformat}
> SyntaxException: line 4:2 mismatched input 'Update' expecting ')'
> (...,'value1','/value2INSERT into tablename(INSERT into tablename
> (key,columnname1,columnname2)) VALUES ('[Update]-...) SyntaxException: line
> 1:0 no viable alternative at input '(' ([(]...)
> {noformat}
> Same behavior while running in interactive mode too. {{/*}} inside a CQL
> statement should not be interpreted as start of multi-line comment.
> With schema:
> {code:java}
> CREATE TABLE tablename ( key text primary key, columnname1 text, columnname2
> text);{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-17667) Text value containing "/*" interpreted as multiline comment in cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850127#comment-17850127
]
Brad Schoening edited comment on CASSANDRA-17667 at 5/28/24 6:40 PM:
-
[~brandon.williams] [~smiklosovic] [~bereng] CQLSH 4.1.x and 5.x all use the
pytest framework and test_cql_parsing.py runs successfully. But 4.0.x uses
nosetests which I was never able to run.
IDK if 4.0.x is worth the effort, but the 4.1 PR should cherry-pick easily if
someone can run the nose tests including the updated unit tests added here for
unclosed productions. Or consider it safest to just fix it where pytest is
running.
PR's for 4.1.x, 5.0.x, 5.1.x are linked here.
was (Author: bschoeni):
[~brandon.williams] [~smiklosovic] [~bereng] CQLSH 4.1.x and 5.x all use the
pytest framework and test_cql_parsing.py runs successfully. But 4.0.x uses
nosetests which I was never able to run.
IDK if 4.0.x is worth the effort, but the 4.1 PR should cherry-pick easily if
someone can run the nose tests including the updated unit tests added here for
unclosed productions.
PR's for 4.1.x, 5.0.x, 5.1.x are linked here.
> Text value containing "/*" interpreted as multiline comment in cqlsh
>
>
> Key: CASSANDRA-17667
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17667
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: ANOOP THOMAS
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>
> I use CQLSH command line utility to load some DDLs. The version of utility I
> use is this:
> {noformat}
> [cqlsh 6.0.0 | Cassandra 4.0.0.47 | CQL spec 3.4.5 | Native protocol
> v5]{noformat}
> Command that loads DDL.cql:
> {noformat}
> cqlsh -u username -p password cassandra.example.com 65503 --ssl -f DDL.cql
> {noformat}
> I have a line in CQL script that breaks the syntax.
> {noformat}
> INSERT into tablename (key,columnname1,columnname2) VALUES
> ('keyName','value1','/value2/*/value3');{noformat}
> {{/*}} here is interpreted as start of multi-line comment. It used to work on
> older versions of cqlsh. The error I see looks like this:
> {noformat}
> SyntaxException: line 4:2 mismatched input 'Update' expecting ')'
> (...,'value1','/value2INSERT into tablename(INSERT into tablename
> (key,columnname1,columnname2)) VALUES ('[Update]-...) SyntaxException: line
> 1:0 no viable alternative at input '(' ([(]...)
> {noformat}
> Same behavior while running in interactive mode too. {{/*}} inside a CQL
> statement should not be interpreted as start of multi-line comment.
> With schema:
> {code:java}
> CREATE TABLE tablename ( key text primary key, columnname1 text, columnname2
> text);{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-17667) Text value containing "/*" interpreted as multiline comment in cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850127#comment-17850127
]
Brad Schoening edited comment on CASSANDRA-17667 at 5/28/24 6:16 PM:
-
[~brandon.williams] [~smiklosovic] [~bereng] CQLSH 4.1.x and 5.x all use the
pytest framework and test_cql_parsing.py runs successfully. But 4.0.x uses
nosetests which I was never able to run.
IDK if 4.0.x is worth the effort, but the 4.1 PR should cherry-pick easily if
someone can run the nose tests including the updated unit tests added here for
unclosed productions.
PR's for 4.1.x, 5.0.x, 5.1.x are linked here.
was (Author: bschoeni):
[~brandon.williams] [~smiklosovic] [~bereng] CQLSH 4.1.x and 5.x all use the
pytest framework and test_cql_parsing.py runs successfully. But 4.0.x uses
nosetests which I was never able to run.
IDK if 4.0.x is worth the effort, but the 4.1 PR should cherry-pick easily if
someone can run the nose tests including the updated unit tests here for
unclosed productions.
PR's for 4.1.x, 5.0.x, 5.1.x are linked here.
> Text value containing "/*" interpreted as multiline comment in cqlsh
>
>
> Key: CASSANDRA-17667
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17667
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: ANOOP THOMAS
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>
> I use CQLSH command line utility to load some DDLs. The version of utility I
> use is this:
> {noformat}
> [cqlsh 6.0.0 | Cassandra 4.0.0.47 | CQL spec 3.4.5 | Native protocol
> v5]{noformat}
> Command that loads DDL.cql:
> {noformat}
> cqlsh -u username -p password cassandra.example.com 65503 --ssl -f DDL.cql
> {noformat}
> I have a line in CQL script that breaks the syntax.
> {noformat}
> INSERT into tablename (key,columnname1,columnname2) VALUES
> ('keyName','value1','/value2/*/value3');{noformat}
> {{/*}} here is interpreted as start of multi-line comment. It used to work on
> older versions of cqlsh. The error I see looks like this:
> {noformat}
> SyntaxException: line 4:2 mismatched input 'Update' expecting ')'
> (...,'value1','/value2INSERT into tablename(INSERT into tablename
> (key,columnname1,columnname2)) VALUES ('[Update]-...) SyntaxException: line
> 1:0 no viable alternative at input '(' ([(]...)
> {noformat}
> Same behavior while running in interactive mode too. {{/*}} inside a CQL
> statement should not be interpreted as start of multi-line comment.
> With schema:
> {code:java}
> CREATE TABLE tablename ( key text primary key, columnname1 text, columnname2
> text);{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-17667) Text value containing "/*" interpreted as multiline comment in cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850127#comment-17850127
]
Brad Schoening edited comment on CASSANDRA-17667 at 5/28/24 6:16 PM:
-
[~brandon.williams] [~smiklosovic] [~bereng] CQLSH 4.1.x and 5.x all use the
pytest framework and test_cql_parsing.py runs successfully. But 4.0.x uses
nosetests which I was never able to run.
IDK if 4.0.x is worth the effort, but the 4.1 PR should cherry-pick easily if
someone can run the nose tests including the updated unit tests here for
unclosed productions.
PR's for 4.1.x, 5.0.x, 5.1.x are linked here.
was (Author: bschoeni):
[~brandon.williams] [~smiklosovic] [~bereng] CQLSH 4.1.x and 5.x all use the
pytest framework and test_cql_parsing.py runs successfully. But 4.0.x uses
nosetests which I was never able to run.
PR's for 4.1.x, 5.0.x, 5.1.x are linked here.
> Text value containing "/*" interpreted as multiline comment in cqlsh
>
>
> Key: CASSANDRA-17667
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17667
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: ANOOP THOMAS
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>
> I use CQLSH command line utility to load some DDLs. The version of utility I
> use is this:
> {noformat}
> [cqlsh 6.0.0 | Cassandra 4.0.0.47 | CQL spec 3.4.5 | Native protocol
> v5]{noformat}
> Command that loads DDL.cql:
> {noformat}
> cqlsh -u username -p password cassandra.example.com 65503 --ssl -f DDL.cql
> {noformat}
> I have a line in CQL script that breaks the syntax.
> {noformat}
> INSERT into tablename (key,columnname1,columnname2) VALUES
> ('keyName','value1','/value2/*/value3');{noformat}
> {{/*}} here is interpreted as start of multi-line comment. It used to work on
> older versions of cqlsh. The error I see looks like this:
> {noformat}
> SyntaxException: line 4:2 mismatched input 'Update' expecting ')'
> (...,'value1','/value2INSERT into tablename(INSERT into tablename
> (key,columnname1,columnname2)) VALUES ('[Update]-...) SyntaxException: line
> 1:0 no viable alternative at input '(' ([(]...)
> {noformat}
> Same behavior while running in interactive mode too. {{/*}} inside a CQL
> statement should not be interpreted as start of multi-line comment.
> With schema:
> {code:java}
> CREATE TABLE tablename ( key text primary key, columnname1 text, columnname2
> text);{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-17667) Text value containing "/*" interpreted as multiline comment in cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850127#comment-17850127
]
Brad Schoening edited comment on CASSANDRA-17667 at 5/28/24 6:10 PM:
-
[~brandon.williams] [~smiklosovic] [~bereng] CQLSH 4.1.x and 5.x all use the
pytest framework and test_cql_parsing.py runs successfully. But 4.0.x uses
nosetests which I was never able to run.
PR's for 4.1.x, 5.0.x, 5.1.x are linked here.
was (Author: bschoeni):
[~brandon.williams] [~smiklosovic] [~bereng] CQLSH 4.1.x and 5.x all use the
pytest framework and test_cql_parsing.py run successfully. But 4.0.x uses
nosetests which I was never able to run.
PR's for 4.1.x, 5.0.x, 5.1.x are linked here.
> Text value containing "/*" interpreted as multiline comment in cqlsh
>
>
> Key: CASSANDRA-17667
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17667
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: ANOOP THOMAS
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>
> I use CQLSH command line utility to load some DDLs. The version of utility I
> use is this:
> {noformat}
> [cqlsh 6.0.0 | Cassandra 4.0.0.47 | CQL spec 3.4.5 | Native protocol
> v5]{noformat}
> Command that loads DDL.cql:
> {noformat}
> cqlsh -u username -p password cassandra.example.com 65503 --ssl -f DDL.cql
> {noformat}
> I have a line in CQL script that breaks the syntax.
> {noformat}
> INSERT into tablename (key,columnname1,columnname2) VALUES
> ('keyName','value1','/value2/*/value3');{noformat}
> {{/*}} here is interpreted as start of multi-line comment. It used to work on
> older versions of cqlsh. The error I see looks like this:
> {noformat}
> SyntaxException: line 4:2 mismatched input 'Update' expecting ')'
> (...,'value1','/value2INSERT into tablename(INSERT into tablename
> (key,columnname1,columnname2)) VALUES ('[Update]-...) SyntaxException: line
> 1:0 no viable alternative at input '(' ([(]...)
> {noformat}
> Same behavior while running in interactive mode too. {{/*}} inside a CQL
> statement should not be interpreted as start of multi-line comment.
> With schema:
> {code:java}
> CREATE TABLE tablename ( key text primary key, columnname1 text, columnname2
> text);{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-17667) Text value containing "/*" interpreted as multiline comment in cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17850127#comment-17850127
]
Brad Schoening commented on CASSANDRA-17667:
[~brandon.williams] [~smiklosovic] [~bereng] CQLSH 4.1.x and 5.x all use the
pytest framework and test_cql_parsing.py run successfully. But 4.0.x uses
nosetests which I was never able to run.
PR's for 4.1.x, 5.0.x, 5.1.x are linked here.
> Text value containing "/*" interpreted as multiline comment in cqlsh
>
>
> Key: CASSANDRA-17667
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17667
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: ANOOP THOMAS
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>
> I use CQLSH command line utility to load some DDLs. The version of utility I
> use is this:
> {noformat}
> [cqlsh 6.0.0 | Cassandra 4.0.0.47 | CQL spec 3.4.5 | Native protocol
> v5]{noformat}
> Command that loads DDL.cql:
> {noformat}
> cqlsh -u username -p password cassandra.example.com 65503 --ssl -f DDL.cql
> {noformat}
> I have a line in CQL script that breaks the syntax.
> {noformat}
> INSERT into tablename (key,columnname1,columnname2) VALUES
> ('keyName','value1','/value2/*/value3');{noformat}
> {{/*}} here is interpreted as start of multi-line comment. It used to work on
> older versions of cqlsh. The error I see looks like this:
> {noformat}
> SyntaxException: line 4:2 mismatched input 'Update' expecting ')'
> (...,'value1','/value2INSERT into tablename(INSERT into tablename
> (key,columnname1,columnname2)) VALUES ('[Update]-...) SyntaxException: line
> 1:0 no viable alternative at input '(' ([(]...)
> {noformat}
> Same behavior while running in interactive mode too. {{/*}} inside a CQL
> statement should not be interpreted as start of multi-line comment.
> With schema:
> {code:java}
> CREATE TABLE tablename ( key text primary key, columnname1 text, columnname2
> text);{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-19640) Enhance documentation on storage engine with leading summary
[ https://issues.apache.org/jira/browse/CASSANDRA-19640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brad Schoening updated CASSANDRA-19640: --- Test and Documentation Plan: n/a for documentation Status: Patch Available (was: In Progress) > Enhance documentation on storage engine with leading summary > > > Key: CASSANDRA-19640 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19640 > Project: Cassandra > Issue Type: Improvement > Components: Documentation >Reporter: Brad Schoening >Assignee: Brad Schoening >Priority: Low > > The storage engine > [documentation|https://github.com/apache/cassandra/blob/trunk/doc/modules/cassandra/pages/architecture/storage-engine.adoc] > would benefit from an abstract or summary which mentions key points that it > uses a Log-structured merge (LSM) tree design, is write-oriented, and relies > upon bloom filters (not B-trees) to optimize the read path. -- 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-17667) Text value containing "/*" interpreted as multiline comment in cqlsh
[
https://issues.apache.org/jira/browse/CASSANDRA-17667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846493#comment-17846493
]
Brad Schoening edited comment on CASSANDRA-17667 at 5/24/24 6:31 PM:
-
[~bereng] I have updated the PR with a test string for */. There already exists
{code:java}
'SELECT FROM "/*MyTable*/";'
'SELECT FROM /*
comment block starts here;
and continues here
*/ "MyTable';
' /* comment block */
/* another comment */ SELECT FROM /*
comment block starts here;
and continues here
*/ "MyTable';
' '
'SELECT FROM /* \n comment block starts here; \n and continues here \n */
"MyTable";'
{code}
I looked up pg-style quoted equivalents means, and see that was added in
CASSANDRA-7769
was (Author: bschoeni):
[~bereng] I have updated the PR with a test string for */. There already exists
{code:java}
'SELECT FROM "/*MyTable*/";'
'SELECT FROM /*
comment block starts here;
and continues here
*/ "MyTable';
' /* comment block */
/* another comment */ SELECT FROM /*
comment block starts here;
and continues here
*/ "MyTable';
' '
'SELECT FROM /* \n comment block starts here; \n and continues here \n */
"MyTable";'
{code}
I looked up pg-style quoted equivalents means, and see that was added in [link
CASSANDRA-7769|https://issues.apache.org/jira/browse/CASSANDRA-7769]
> Text value containing "/*" interpreted as multiline comment in cqlsh
>
>
> Key: CASSANDRA-17667
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17667
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
>Reporter: ANOOP THOMAS
>Assignee: Brad Schoening
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>
> I use CQLSH command line utility to load some DDLs. The version of utility I
> use is this:
> {noformat}
> [cqlsh 6.0.0 | Cassandra 4.0.0.47 | CQL spec 3.4.5 | Native protocol
> v5]{noformat}
> Command that loads DDL.cql:
> {noformat}
> cqlsh -u username -p password cassandra.example.com 65503 --ssl -f DDL.cql
> {noformat}
> I have a line in CQL script that breaks the syntax.
> {noformat}
> INSERT into tablename (key,columnname1,columnname2) VALUES
> ('keyName','value1','/value2/*/value3');{noformat}
> {{/*}} here is interpreted as start of multi-line comment. It used to work on
> older versions of cqlsh. The error I see looks like this:
> {noformat}
> SyntaxException: line 4:2 mismatched input 'Update' expecting ')'
> (...,'value1','/value2INSERT into tablename(INSERT into tablename
> (key,columnname1,columnname2)) VALUES ('[Update]-...) SyntaxException: line
> 1:0 no viable alternative at input '(' ([(]...)
> {noformat}
> Same behavior while running in interactive mode too. {{/*}} inside a CQL
> statement should not be interpreted as start of multi-line comment.
> With schema:
> {code:java}
> CREATE TABLE tablename ( key text primary key, columnname1 text, columnname2
> text);{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
