[jira] [Updated] (CASSANDRASC-132) Add restore job progress endpoint and consistency check on restore ranges
[ https://issues.apache.org/jira/browse/CASSANDRASC-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-132: --- Labels: pull-request-available (was: ) > Add restore job progress endpoint and consistency check on restore ranges > - > > Key: CASSANDRASC-132 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-132 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > > In order to support the sidecar-managed restore jobs (sidecar counterpart of > Cassandra analytics bulk write via S3), it is required to have the capability > to perform consistency check for the individual restore ranges and have a new > endpoint for the spark job to query the restore progress. > The consistency check should be responsive to cluster topology changes. For > example, if there is a new node joining the cluster, the write replica set of > the affected ranges are changed. The joining node should be able to discover > the restore ranges that it owns and restore the data. -- 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-19642) IndexOutOfBoundsException while serializing CommandsForKey
[ https://issues.apache.org/jira/browse/CASSANDRA-19642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-19642: --- Labels: pull-request-available (was: ) > IndexOutOfBoundsException while serializing CommandsForKey > -- > > Key: CASSANDRA-19642 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19642 > Project: Cassandra > Issue Type: Bug > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Fix For: NA > > > When serializing CommandsForKey we have a concept of “unmanaged” but tests > didn’t cover this… when we have anything unmanaged we fail to serialize with > a IndexOutOfBounds due to using the ValueAccessor API incorrectly -- 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-18732) Baseline Diagnostic vtables for Accord
[
https://issues.apache.org/jira/browse/CASSANDRA-18732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRA-18732:
---
Labels: pull-request-available (was: )
> Baseline Diagnostic vtables for Accord
> --
>
> Key: CASSANDRA-18732
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18732
> Project: Cassandra
> Issue Type: Improvement
> Components: Accord, Observability/Metrics
>Reporter: Caleb Rackliffe
>Assignee: Caleb Rackliffe
>Priority: Normal
> Labels: pull-request-available
> Fix For: 5.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In addition to JMX-based metrics, there are bits of diagnostic information
> for Accord that we should consider exposing through vtables:
> 1.) We should ensure that coordinator-level CQL transactions and the local
> reads and writes they spawn are visible to the existing {{QueriesTable}}
> vtable.
> The first may already just work. We may need to make some tweaks to
> {{TxnNamedRead}} and {{TxnWrite}} for the local operations though.
> ({{CommandStore}} tasks are out of scope here, as they would probably be more
> confusing than useful in {{QueriesTable}}?)
> 2.) A new vtable for pending commands for a key.
> - Disable SELECT */require a partition key
> - Might require partial back-port of stringifying table/partition key from
> Accord to be correct
> - ex. {{SELECT timestamps FROM myawesometable where ks=? and table=? and
> partition_key=?}}
> - Clustering can be the Accord timestamp elements, no further normal columns.
> 3.) A new vtable for command store-specific cache stats
> - Gather via {{Store.execute()}} for correctness.
> - Store id should be partition key (see {{AccordCommandStore}})
> - hits, misses, total (maybe just throw out the keyspaces and coalesce
> ranges?)
> 4.) (Requires [~aweisberg]'s outstanding work) A new vtable for live
> migration state
> - {{TableMigrationState}} could be flattened into a row
> - Is this already persisted? If so, why a new vtable?
> 5.) A vtable to expose {{accord.local.Node#coordinating()}} as a map
> - ex. {{SELECT txn_id, type}}
--
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] (CASSANDRASC-131) Reset system properties on test completion to avoid population from prior integration test
[ https://issues.apache.org/jira/browse/CASSANDRASC-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-131: --- Labels: pull-request-available (was: ) > Reset system properties on test completion to avoid population from prior > integration test > -- > > Key: CASSANDRASC-131 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-131 > Project: Sidecar for Apache Cassandra > Issue Type: Task > Components: Rest API >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > > Some integration test alters the System properties in order to start > operations like replacement. Due to the test specific setup, there is a race > condition on rolling back the system properties and causing population for > the next test run and failure. > The patch is to have a common solution for integration test that records the > initial system properties and restores on completion. -- 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] (CASSANDRASC-129) Remove tableId from list snapshot response
[
https://issues.apache.org/jira/browse/CASSANDRASC-129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-129:
---
Labels: pull-request-available (was: )
> Remove tableId from list snapshot response
> --
>
> Key: CASSANDRASC-129
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-129
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
> Components: Rest API
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Labels: pull-request-available
>
> In CASSANDRASC-94, a new field {{tableId}} was added to the payload of the
> list snapshots endpoint. Old Sidecar clients are compatible with new fields
> added from the server side. However, other clients can potentially break and
> for that reason we should remove the {{tableId}} field from the response and
> make any potential breaking changes with an API version change instead. As an
> alternative, we can add the {{tableId}} as part of the {{tableName}} field
> instead.
--
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] (CASSANDRASC-128) Integrate Cassandra Sidecar with SonarQube
[ https://issues.apache.org/jira/browse/CASSANDRASC-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-128: --- Labels: pull-request-available (was: ) > Integrate Cassandra Sidecar with SonarQube > -- > > Key: CASSANDRASC-128 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-128 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Yuriy Semchyshyn >Priority: Normal > Labels: pull-request-available > > Introduce the initial Gradle configuration for integration of Cassandra > Sidecar with SonarCube for code analysis -- 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] (CASSANDRASC-125) Import Queue pendingImports metrics is reporting an incorrect value
[ https://issues.apache.org/jira/browse/CASSANDRASC-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-125: --- Labels: pull-request-available (was: ) > Import Queue pendingImports metrics is reporting an incorrect value > --- > > Key: CASSANDRASC-125 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-125 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > The pending imports metrics is reporting the unaggregated value across all > keyspaces and tables. Additionally this metric does not report correctly when > the queue is drained. -- 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] (CASSANDRASC-126) Make RestoreJobDiscoverer less verbose
[ https://issues.apache.org/jira/browse/CASSANDRASC-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-126: --- Labels: pull-request-available (was: ) > Make RestoreJobDiscoverer less verbose > -- > > Key: CASSANDRASC-126 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-126 > Project: Sidecar for Apache Cassandra > Issue Type: Task >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > > RestoreJobDiscoverer print the job summary of all recent run jobs every a few > minutes. The verboseness creates noise especially most of the jobs have no > update. Proposing a patch to skip logging those jobs w/o update. -- 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] (CASSANDRASC-124) Fix wait time acquired in SidecarRateLimiter
[ https://issues.apache.org/jira/browse/CASSANDRASC-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-124: --- Labels: pull-request-available (was: ) > Fix wait time acquired in SidecarRateLimiter > > > Key: CASSANDRASC-124 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-124 > Project: Sidecar for Apache Cassandra > Issue Type: Bug >Reporter: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > Currently the wait time retrieved is a future timestamp instead of exact > micros to wait. Hence wait time header is never sent from `FileStreamer` and > only 429s are sent when throttled. In this patch, we calculate the wait time > separately. -- 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] (CASSANDRASC-119) Fix flaky test due to port conflicts
[
https://issues.apache.org/jira/browse/CASSANDRASC-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-119:
---
Labels: pull-request-available (was: )
> Fix flaky test due to port conflicts
>
>
> Key: CASSANDRASC-119
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-119
> Project: Sidecar for Apache Cassandra
> Issue Type: Task
>Reporter: Yifan Cai
>Assignee: Yifan Cai
>Priority: Normal
> Labels: pull-request-available
>
> There are still tests are binding to fixed port number and fail to start
> sidecar server. Proposing a patch to always start test server that binds to
> port 0 with TestServiceConfiguration.
> {code:java}
> ERROR [vert.x-eventloop-thread-2] 2024-04-13 14:17:57,490
> ServerVerticle.java:93 - Failed to deploy Cassandra Sidecar verticle failed
> on socket addresses=[0.0.0.0:9043]
> java.net.BindException: Address already in use
> at java.base/sun.nio.ch.Net.bind0(Native Method)
> at java.base/sun.nio.ch.Net.bind(Net.java:459)
> at java.base/sun.nio.ch.Net.bind(Net.java:448)
> at
> java.base/sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:227)
> at
> io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:141)
> at
> io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:562)
> at
> io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:1334)
> at
> io.netty.channel.AbstractChannelHandlerContext.invokeBind(AbstractChannelHandlerContext.java:600)
> at
> io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:579)
> at
> io.netty.channel.DefaultChannelPipeline.bind(DefaultChannelPipeline.java:973)
> at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:260)
> at
> io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:380)
> at
> io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173)
> at
> io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasksFrom(SingleThreadEventExecutor.java:426)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:375)
> at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:557)
> at
> io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997)
> at
> io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
> at
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
> at java.base/java.lang.Thread.run(Thread.java:829)
> {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] (CASSANDRASC-118) Support sending json request
[ https://issues.apache.org/jira/browse/CASSANDRASC-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-118: --- Labels: pull-request-available (was: ) > Support sending json request > > > Key: CASSANDRASC-118 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-118 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > > The current sidecar client does not allow sending requests that have payload. > Proposing the patch to support it. -- 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] (CASSANDRASC-117) Record additional metrics for improved observability
[ https://issues.apache.org/jira/browse/CASSANDRASC-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-117: --- Labels: pull-request-available (was: ) > Record additional metrics for improved observability > > > Key: CASSANDRASC-117 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-117 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > With this patch increasing the number of metrics captured on sidecar side for > improved observability. This includes, capturing resource level metrics, > Cassandra instance health metrics, SSTable import metrics etc. Also as part > of this patch, migrating existing metrics to Dropwizard registry. -- 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-19527) Typo in Cassandra Testing Webpage
[
https://issues.apache.org/jira/browse/CASSANDRA-19527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRA-19527:
---
Labels: pull-request-available (was: )
> Typo in Cassandra Testing Webpage
> -
>
> Key: CASSANDRA-19527
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19527
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation/Website
>Reporter: ConfX
>Priority: Normal
> Labels: pull-request-available
>
> In `Stress and FQLTool tests` Section:
> {code:java}
> To run the tests for those tools, first, build jar artifacts for them but
> calling: {code}
> "but" -> "by".
--
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] (CASSANDRASC-116) Allow for JmxClient to be extensible
[
https://issues.apache.org/jira/browse/CASSANDRASC-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-116:
---
Labels: pull-request-available (was: )
> Allow for JmxClient to be extensible
>
>
> Key: CASSANDRASC-116
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-116
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Labels: pull-request-available
>
> We need to allow {{JmxClient}} to be extensible for better testing
> flexibility. Currently, the {{JmxClient}} constructor is private and does not
> allow extending it and providing any flexibility.
--
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-19110) apt-key deprecation, replace with gpg --dearmor in the docs.
[
https://issues.apache.org/jira/browse/CASSANDRA-19110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRA-19110:
---
Labels: pull-request-available (was: )
> apt-key deprecation, replace with gpg --dearmor in the docs.
>
>
> Key: CASSANDRA-19110
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19110
> Project: Cassandra
> Issue Type: Improvement
> Components: Documentation/Website
>Reporter: Simon K
>Assignee: Simon K
>Priority: Normal
> Labels: pull-request-available
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 5.0.x, 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> the command `apt-key` is deprecated and soon to be removed, especially on
> Ubuntu.
> the directory `/usr/share/keyrings` for shared keys are also being removed.
> I suggest to convert the docs from
> {code:java}
> curl https://downloads.apache.org/cassandra/KEYS | sudo apt-key add - {code}
> to a simpler command:
> {code:java}
> curl https://downloads.apache.org/cassandra/KEYS | sudo gpg --dearmor -o
> /etc/apt/keyrings/cassandra-archive-keyring.gpg {code}
> The path `/etc/apt/keyrings` doesn't exists by default on Ubuntu 20.04 but it
> does on 22.04.
> I also suggest to add the source.list.d text from
> {code:java}
> $ echo "deb https://debian.cassandra.apache.org 42x main" | sudo tee -a
> /etc/apt/sources.list.d/cassandra.sources.list
> deb https://debian.cassandra.apache.org 42x main{code}
> to
> {code:java}
> $ echo "deb [signed-by=/etc/apt/keyrings/cassandra-archive-keyring.gpg]
> https://debian.cassandra.apache.org 42x main" | sudo tee -a
> /etc/apt/sources.list.d/cassandra.sources.list
> deb [signed-by=/etc/apt/keyrings/cassandra-archive-keyring.gpg]
> https://debian.cassandra.apache.org 42x main {code}
> I have made a [PR|https://github.com/apache/cassandra/pull/2936]
> I have tested the gpg --dearmor on a VM with Ubuntu 22.04 myself recently and
> it works just fine.
--
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] (CASSANDRASC-115) Add FilteringMetricRegistry to allow filtering of metrics
[ https://issues.apache.org/jira/browse/CASSANDRASC-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-115: --- Labels: pull-request-available (was: ) > Add FilteringMetricRegistry to allow filtering of metrics > - > > Key: CASSANDRASC-115 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-115 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > This patch is to add FilteringMetricRegistry to filter out metrics by adding > filters to sidecar.yaml file. This is useful in cases when metrics recorded > by sidecar are high is number and for fine grain control over metrics exposed > from sidecar -- 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] (CASSANDRASC-107) Improve logging for slice restore task
[ https://issues.apache.org/jira/browse/CASSANDRASC-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-107: --- Labels: low-hanging-fruit pull-request-available (was: low-hanging-fruit) > Improve logging for slice restore task > -- > > Key: CASSANDRASC-107 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-107 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Yifan Cai >Assignee: Francisco Guerrero >Priority: Normal > Labels: low-hanging-fruit, pull-request-available > > I want to propose logging improvements. > Add more logs to the individual steps during the restore task, i.e. > RestoreSliceTask and StorageClient. > In other places like retrying to poll the object existence, the stack trace > can be omitted, as it provides no additional knowledge than object not found. -- 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] (CASSANDRASC-105) RestoreSliceTask could be stuck due to missing exception handling
[ https://issues.apache.org/jira/browse/CASSANDRASC-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-105: --- Labels: pull-request-available (was: ) > RestoreSliceTask could be stuck due to missing exception handling > - > > Key: CASSANDRASC-105 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-105 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Yifan Cai >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > In RestoreSliceTask, there are a few places could throw exceptions but > missing exception handling in call-sites. As a result, the RetoreSliceTask > never fulfill the promise, i.e. the task is stuck. > For example, downloadObjectIfAbsent could throw instead of returning a > future, in such case, the task will never fail or complete. -- 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] (CASSANDRASC-111) Improve observability in Sidecar
[ https://issues.apache.org/jira/browse/CASSANDRASC-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-111: --- Labels: pull-request-available (was: ) > Improve observability in Sidecar > - > > Key: CASSANDRASC-111 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-111 > Project: Sidecar for Apache Cassandra > Issue Type: Task > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > Currently we capture minimal metrics in Sidecar, through this patch we want > to improve observability in Sidecar. > For this we want to record more metrics in Sidecar with Dropwizard. Introduce > setup changes needed for capturing sidecar metrics through Dropwizard. Remove > existing metric interfaces with default methods, in place capture metrics > with Dropwizard APIs. > Some of the metric kinds we will capture through this patch are, HTTP metrics > like number of requests created per route, response time taken endpoint wise. > Capture metrics per Cassandra instance maintained by Sidecar, such as, > instance specific restore metrics, instance specific stream and upload > metrics. We will also turn on registering, server route specific metrics > emitted by Vert.x. -- 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] (CASSANDRASC-114) Make hash algorithm implementation pluggable
[ https://issues.apache.org/jira/browse/CASSANDRASC-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-114: --- Labels: pull-request-available (was: ) > Make hash algorithm implementation pluggable > > > Key: CASSANDRASC-114 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-114 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > > I would like to propose to make the hash algorithm implementation in sidecar > pluggable. -- 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] (CASSANDRASC-113) Fix flaky JmxClientTest
[ https://issues.apache.org/jira/browse/CASSANDRASC-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-113: --- Labels: pull-request-available (was: ) > Fix flaky JmxClientTest > --- > > Key: CASSANDRASC-113 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-113 > Project: Sidecar for Apache Cassandra > Issue Type: Bug >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > JmxClientTests can fail when there is a race between registry port assignment > and the test starting to use the port. -- 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] (CASSANDRASC-106) Add restore task watcher to report long running tasks
[ https://issues.apache.org/jira/browse/CASSANDRASC-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-106: --- Labels: pull-request-available (was: ) > Add restore task watcher to report long running tasks > - > > Key: CASSANDRASC-106 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-106 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Yifan Cai >Assignee: Doug Rohrer >Priority: Normal > Labels: pull-request-available > > Having a watcher to report the long running restore slice task can provide > better insights. > The watcher can live inside the RestoreProcessor and periodically examine the > futures of the running tasks. > Ideally, it signals the task to log the current stack trace. -- 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] (CASSANDRASC-112) ClosedChannelException when downloading from S3
[
https://issues.apache.org/jira/browse/CASSANDRASC-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-112:
---
Labels: pull-request-available (was: )
> ClosedChannelException when downloading from S3
> ---
>
> Key: CASSANDRASC-112
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-112
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
>Reporter: Yifan Cai
>Assignee: Yifan Cai
>Priority: Normal
> Labels: pull-request-available
>
> {code:java}
> org.apache.cassandra.sidecar.exceptions.RestoreJobFatalException:
> Unrecoverable error when downloading object.
> Caused by: java.nio.channels.ClosedChannelException
> at
> java.base/sun.nio.ch.FileChannelImpl.ensureOpen(FileChannelImpl.java:150)
> at java.base/sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:266)
> at
> org.apache.cassandra.sidecar.restore.StorageClient.lambda$subscribeRateLimitedWrite$6(StorageClient.java:271)
> ... 22 more
> {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-19355) Accord: PreLoadContext must properly and consistently support ranges
[ https://issues.apache.org/jira/browse/CASSANDRA-19355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-19355: --- Labels: pull-request-available (was: ) > Accord: PreLoadContext must properly and consistently support ranges > > > Key: CASSANDRA-19355 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19355 > Project: Cassandra > Issue Type: Improvement > Components: Accord >Reporter: Benedict Elliott Smith >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Fix For: 5.x > > Time Spent: 10m > Remaining Estimate: 0h > > There are some mechanisms for ensuring range transactions are loaded for > range transactions, but they do not currently work properly (having several > race conditions), are potentially costly in terms of memory consumption, and > are inconsistent with how they work for key transactions. -- 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] (CASSANDRASC-110) NPE throws when getting StorageClient from pool
[
https://issues.apache.org/jira/browse/CASSANDRASC-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-110:
---
Labels: pull-request-available (was: )
> NPE throws when getting StorageClient from pool
> ---
>
> Key: CASSANDRASC-110
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-110
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
> Components: Rest API
>Reporter: Yifan Cai
>Assignee: Yifan Cai
>Priority: Normal
> Labels: pull-request-available
>
> {code:java}
> Caused by: java.lang.NullPointerException
> at
> org.apache.cassandra.sidecar.restore.StorageClientPool.storageClient(StorageClientPool.java:118)
> at
> org.apache.cassandra.sidecar.db.RestoreSlice.toAsyncTask(RestoreSlice.java:244)
> at
> org.apache.cassandra.sidecar.restore.RestoreProcessor.execute(RestoreProcessor.java:132)
> at
> org.apache.cassandra.sidecar.tasks.PeriodicTaskExecutor.executeInternal(PeriodicTaskExecutor.java:142)
> at
> org.apache.cassandra.sidecar.tasks.PeriodicTaskExecutor.lambda$schedule$0(PeriodicTaskExecutor.java:66)
> at
> org.apache.cassandra.sidecar.concurrent.ExecutorPools$TaskExecutorPool.lambda$setPeriodic$0(ExecutorPools.java:156)
> {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-19423) WEBSITE - Catalysts and community page udpates
[ https://issues.apache.org/jira/browse/CASSANDRA-19423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-19423: --- Labels: pull-request-available (was: ) > WEBSITE - Catalysts and community page udpates > -- > > Key: CASSANDRA-19423 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19423 > Project: Cassandra > Issue Type: Task >Reporter: Paul Au >Priority: Normal > Labels: pull-request-available > > * Updating the PMC list on the community page. > * Adding Catalyst bios and images to the Apache Cassandra Catalysts page > Previews available: > https://raw.githack.com/Paul-TT/cassandra-website/CASSANDRA-19423_generated/content/_/cassandra-catalyst-program.html > https://raw.githack.com/Paul-TT/cassandra-website/CASSANDRA-19423_generated/content/_/community.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-19420) WEBSITE - Link fix for mathematical functions on 5.0 landing page
[ https://issues.apache.org/jira/browse/CASSANDRA-19420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-19420: --- Labels: pull-request-available (was: ) > WEBSITE - Link fix for mathematical functions on 5.0 landing page > - > > Key: CASSANDRA-19420 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19420 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > > link fix for mathematical functions on 5.0 landing page -- 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] (CASSANDRASC-104) Relocate Sidecar common classes in vertx-client-shaded
[
https://issues.apache.org/jira/browse/CASSANDRASC-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-104:
---
Labels: pull-request-available (was: )
> Relocate Sidecar common classes in vertx-client-shaded
> --
>
> Key: CASSANDRASC-104
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-104
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Labels: pull-request-available
>
> It is desirable to relocate the common classes
> {{org.apache.cassandra.sidecar.common.*}} in the {{vertx-client-shaded}}
> subproject. The benefits are the following:
> - Better isolation of the shared classes when loading them in downstream
> projects (i.e Analytics)
> - Avoids having two classes loaded in the same classpath, but with different
> internal definition (for example when annotations are relocated but the class
> itself is not)
--
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] (CASSANDRASC-101) Upgrade Vert.x version in Sidecar to 4.5
[ https://issues.apache.org/jira/browse/CASSANDRASC-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-101: --- Labels: pull-request-available (was: ) > Upgrade Vert.x version in Sidecar to 4.5 > > > Key: CASSANDRASC-101 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-101 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > Labels: pull-request-available > > There was a memory leak identified in 4.4 branch in Vert.x > [https://github.com/eclipse-vertx/vert.x/pull/5082]. This leak is caused when > connection pools are recreated for vert.x HttpClient. This was fixed in 4.5 > branch, and a release was out 10 days ago. Sidecar is on 4.4.6 Vert.x > version, hence we need to upgrade to 4.5.3 Vert.x version. As part of this we > will also pick up dynamic update capability added for read and write > thresholds set for servers > [https://github.com/eclipse-vertx/vert.x/pull/5088]. -- 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] (CASSANDRASC-103) Sidecar does not start up due to injection error
[
https://issues.apache.org/jira/browse/CASSANDRASC-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-103:
---
Labels: pull-request-available (was: )
> Sidecar does not start up due to injection error
>
>
> Key: CASSANDRASC-103
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-103
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
>Reporter: Yifan Cai
>Assignee: Yifan Cai
>Priority: Normal
> Labels: pull-request-available
>
> `./gradlew run` gives
> {code:java}
> Exception in thread "main" com.google.inject.ProvisionException: Unable to
> provision, see the following errors:
> 1) Error in custom provider,
> com.fasterxml.jackson.databind.exc.InvalidDefinitionException: Cannot
> construct instance of
> `org.apache.cassandra.sidecar.config.SchemaKeyspaceConfiguration` (no
> Creators, like default constructor, exist): abstract types either need to be
> mapped to concrete types, have custom deserializer, or contain additional
> type information
> at [Source: (File); line: 108, column: 5] (through reference chain:
> org.apache.cassandra.sidecar.config.yaml.SidecarConfigurationImpl["sidecar"]->org.apache.cassandra.sidecar.config.yaml.ServiceConfigurationImpl["schema"])
> at
> org.apache.cassandra.sidecar.server.MainModule.sidecarConfiguration(MainModule.java:310)
> while locating org.apache.cassandra.sidecar.config.SidecarConfiguration
> for the 2nd parameter of
> org.apache.cassandra.sidecar.server.Server.(Server.java:89)
> at org.apache.cassandra.sidecar.server.Server.class(Server.java:69)
> while locating org.apache.cassandra.sidecar.server.Server
> 1 error
> {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] (CASSANDRASC-100) Fix flaky SSTableImportHandlerTest
[ https://issues.apache.org/jira/browse/CASSANDRASC-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-100: --- Labels: pull-request-available (was: ) > Fix flaky SSTableImportHandlerTest > -- > > Key: CASSANDRASC-100 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-100 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > Few of SSTableImportHandlerTest are flaky, causing multiple re-triggers for > PR green: > - testSucceeds > - testSucceedsWithClearRepaired > - testSucceedsWithExtendedVerify > They are failing with error: > org.mockito.exceptions.misusing.CannotStubVoidMethodWithReturnValue: > 'healthCheck' is a *void method* and it *cannot* be stubbed with a *return > value*! -- 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-19305) Accord: Fast single-partition reads
[ https://issues.apache.org/jira/browse/CASSANDRA-19305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-19305: --- Labels: pull-request-available (was: ) > Accord: Fast single-partition reads > --- > > Key: CASSANDRA-19305 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19305 > Project: Cassandra > Issue Type: Improvement > Components: Accord >Reporter: Benedict Elliott Smith >Priority: Normal > Labels: pull-request-available > > Introduce guaranteed 1RT single-partition reads with no transaction metadata -- 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] (CASSANDRASC-99) Break restore job into stage and import phases and persist restore slice status on phase completion
[ https://issues.apache.org/jira/browse/CASSANDRASC-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-99: -- Labels: pull-request-available (was: ) > Break restore job into stage and import phases and persist restore slice > status on phase completion > --- > > Key: CASSANDRASC-99 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-99 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > > In order to improve resilience of the restore sstables from s3 tasks, we want > to break the task into multiple phases and persist the status of each slice. -- 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] (CASSANDRASC-98) Improve logging for traffic shaping / rate limiting configuration
[ https://issues.apache.org/jira/browse/CASSANDRASC-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-98: -- Labels: pull-request-available (was: ) > Improve logging for traffic shaping / rate limiting configuration > - > > Key: CASSANDRASC-98 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-98 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > We need better visibility into the configured values for the traffic shaping > options and different rate limiters used by Cassandra Sidecar to understand > the configuration while running the application. -- 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-18365) CEP-15: Accord Protocol Correctness issue
[ https://issues.apache.org/jira/browse/CASSANDRA-18365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-18365: --- Labels: pull-request-available (was: ) > CEP-15: Accord Protocol Correctness issue > - > > Key: CASSANDRA-18365 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18365 > Project: Cassandra > Issue Type: Bug > Components: Accord >Reporter: Pierre Sutra >Priority: Normal > Labels: pull-request-available > Fix For: 5.x > > Attachments: bug.pdf > > > There is a bug in the Accord protocol which might break linearizability, even > in the single partition case. > The file in attachment details this issue following the pseudo-code in the > white paper describing Accord [1]. If the Java implementation follows this > pseudo-code, it should be subject to the very same problem. > This bug was found by Fedor Ryabinin, Alexey Gotsman and Pierre Sutra. > [1] > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-15%3A+General+Purpose+Transactions?preview=/188744725/188744736/Accord.pdf -- 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] (CASSANDRASC-96) Typo in foundation package under common org.apache.cassandra.sidecar
[
https://issues.apache.org/jira/browse/CASSANDRASC-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-96:
--
Labels: pull-request-available (was: )
> Typo in foundation package under common org.apache.cassandra.sidecar
>
>
> Key: CASSANDRASC-96
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-96
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Labels: pull-request-available
>
> There's a typo in the foundation package spelled {{foundataion}}
--
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] (CASSANDRASC-95) Adding sidecar client changes for restore from S3
[ https://issues.apache.org/jira/browse/CASSANDRASC-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-95: -- Labels: pull-request-available (was: ) > Adding sidecar client changes for restore from S3 > - > > Key: CASSANDRASC-95 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-95 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > > Adding sidecar client changes so that clients can interact with the sidecar > server to restore from S3. -- 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] (CASSANDRASC-92) Add restore SSTables from S3 into Cassandra feature to Cassandra Sidecar
[ https://issues.apache.org/jira/browse/CASSANDRASC-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-92: -- Labels: pull-request-available (was: ) > Add restore SSTables from S3 into Cassandra feature to Cassandra Sidecar > > > Key: CASSANDRASC-92 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-92 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: Normal > Labels: pull-request-available > > Through this proposal we want to add restore capability to Sidecar, for > Sidecar to allow restoring data from S3. As part of this patch we want to add > APIs for creating, updating and getting information about the restore jobs. > We also want to add background tasks for managing these restore jobs. -- 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] (CASSANDRASC-94) Reduce filesystem calls while streaming SSTables
[ https://issues.apache.org/jira/browse/CASSANDRASC-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-94: -- Labels: pull-request-available (was: ) > Reduce filesystem calls while streaming SSTables > > > Key: CASSANDRASC-94 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-94 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > When streaming snapshotted SSTables from Cassandra Sidecar, Sidecar will > perform multiple filesystem calls: > - Traverse the data directories to determine the keyspace / table path > - Once found determine if the SSTable file exists under the snapshots > directory > - Read the filesystem to obtain the file type and file size > - Read the requested range of the file and stream it > The amount of filesystem calls is manageable for streaming a single SSTable, > but when a client(s) read multiple SSTables, for example in the case of > Cassandra Analytics bulk reads, hundred to thousand of requests are performed > requiring every request to perform the above system calls. > In this improvement, it is proposed introducing several caches to reduce the > amount of system calls while streaming SSTables. > - *snapshot list cache*: to maintain a cache of recently listed snapshot > files under a snapshot directory. This cache avoids having to access the > filesystem every time a bulk read client list the snapshot directory. > - *table dir cache*: to maintain a cache of recently streamed table directory > paths. This cache helps avoiding having to traverse the filesystem searching > for the table directory while running bulk reads for example. Since bulk > reads can stream tens to hundreds of SSTable components from a snapshot > directory, this cache helps avoid having to resolve the table directory each > time. > - *snapshot path cache*: to maintain a cache of recently streamed snapshot > SSTable components. This cache avoids having to resolve the snapshot SSTable > component path during bulk reads. Since bulk reads streams sub-ranges of an > SSTable component, the resolution can happen multiple times during bulk reads > for a single SSTable component. > - *file props cache*: to maintain a cache of FileProps of recently streamed > files. This cache avoids having to validate file properties during bulk reads > for example where sub-ranges of an SSTable component are streamed, therefore > reading the file properties can occur multiple times during bulk reads of the > same file. -- 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-19277) WEBSITE - Add Privacy Link to Feather Footer
[ https://issues.apache.org/jira/browse/CASSANDRA-19277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-19277: --- Labels: pull-request-available (was: ) > WEBSITE - Add Privacy Link to Feather Footer > > > Key: CASSANDRA-19277 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19277 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Paul Au >Priority: Normal > Labels: pull-request-available > Attachments: image-2024-01-18-09-11-23-156.png, > image-2024-01-18-09-11-44-762.png > > > The website footer was missing the ASF required privacy link. I have updated > the bundle to include the link -- 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] (CASSANDRASC-93) Define routing order for http routes
[ https://issues.apache.org/jira/browse/CASSANDRASC-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-93: -- Labels: pull-request-available (was: ) > Define routing order for http routes > > > Key: CASSANDRASC-93 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-93 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > > Proposing a patch to control the routing order when the precise ordering is > desired. > For example, the auth handler should be evaluated the first, regardless of > the declaration order. -- 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] (CASSANDRASC-91) AbstractHandler is handling the request even when it fails to extract params
[ https://issues.apache.org/jira/browse/CASSANDRASC-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-91: -- Labels: pull-request-available (was: ) > AbstractHandler is handling the request even when it fails to extract params > > > Key: CASSANDRASC-91 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-91 > Project: Sidecar for Apache Cassandra > Issue Type: Bug >Reporter: n.v.harikrishna >Assignee: n.v.harikrishna >Priority: Normal > Labels: pull-request-available > > AbstractHandler’s handle method is calling extractParamsOrThrow method to > parse the request which can fail with HttpException (a runtime exception). > When extraction fails, then AbstractHandler is processing the failure using > processFailure method and continued to call handleInternal method. Calling > handlerInternal even when failed to extract params resulting unwanted > results. If the extraction of parameters failes, then AbstractHandler should > not call handleInternal. > > Example: > Passing an invalid character for ring route per keysapce endpoint (handled by > RingHandler which is extending AbstractHandler) something like : > [localhost1:9043/api/v1/cassandra/ring/keyspaces/keysapce%60] is resulting to > _Bad Request_ response, but also resulting NPE from the > RingHandler.handleInternal method > > java.lang.NullPointerException: null > at > org.apache.cassandra.sidecar.routes.RingHandler.lambda$handleInternal$0(RingHandler.java:83) > at > io.vertx.core.impl.ContextBase.lambda$executeBlocking$1(ContextBase.java:180) > at > io.vertx.core.impl.ContextInternal.dispatch(ContextInternal.java:277) > at > io.vertx.core.impl.ContextBase.lambda$internalExecuteBlocking$2(ContextBase.java:199) > at io.vertx.core.impl.TaskQueue.run(TaskQueue.java:76) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at > io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) > at java.lang.Thread.run(Thread.java:748) > > It should terminate processing the request when it could not parse the > keyspace. -- 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] (CASSANDRASC-90) Fix Sidecar TokenRangeReplicas endpoint to unwrap the token-range by partitioner's range for a single node clusters
[ https://issues.apache.org/jira/browse/CASSANDRASC-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-90: -- Labels: pull-request-available (was: ) > Fix Sidecar TokenRangeReplicas endpoint to unwrap the token-range by > partitioner's range for a single node clusters > --- > > Key: CASSANDRASC-90 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-90 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Labels: pull-request-available > > The sidecar token-range-replicas endpoint returns an empty range for the > write replicas for single node clusters, due to a bug that fails to unwrap > such ranges returned from Cassandra around the partitioner's token boundary. -- 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] (CASSANDRASC-89) Consider updating guice to 5+
[
https://issues.apache.org/jira/browse/CASSANDRASC-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-89:
--
Labels: pull-request-available (was: )
> Consider updating guice to 5+
> -
>
> Key: CASSANDRASC-89
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-89
> Project: Sidecar for Apache Cassandra
> Issue Type: Task
> Components: Configuration
>Reporter: Stefan Miklosovic
>Assignee: Stefan Miklosovic
>Priority: Normal
> Labels: pull-request-available
> Fix For: 1.0
>
>
> I am getting this when I run sidecar
> {code}
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> (file:/home/fermat/.gradle/caches/modules-2/files-2.1/com.google.inject/guice/4.2.2/6dacbe18e5eaa7f6c9c36db33b42e7985e94ce77/guice-4.2.2.jar)
> to method
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> 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}
> Sidecar is currently running guice of version 4.2.2. Mere bumping to guice
> 5.1.0 solves this and it goes away. I run integration tests as well as units
> and all seems to be passing just fine. I will need to double check though and
> run a formal build.
--
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] (CASSANDRASC-85) Expose TTL option for the create snapshot endpoint
[ https://issues.apache.org/jira/browse/CASSANDRASC-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-85: -- Labels: pull-request-available (was: ) > Expose TTL option for the create snapshot endpoint > -- > > Key: CASSANDRASC-85 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-85 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > Cassandra 4.1 introduced the [TTL > option|https://github.com/apache/cassandra/blob/cassandra-4.1/src/java/org/apache/cassandra/tools/nodetool/Snapshot.java#L57] > for snapshots. If specified, Cassandra will cleanup snapshots after the TTL > has expired. > This option can be leveraged by external clients such as the Cassandra > Analytics library to automatically clean up snapshots created during bulk > reads. -- 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-19200) BLOG - Inaugural Catalysts
[ https://issues.apache.org/jira/browse/CASSANDRA-19200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-19200: --- Labels: pull-request-available (was: ) > BLOG - Inaugural Catalysts > --- > > Key: CASSANDRA-19200 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19200 > Project: Cassandra > Issue Type: Task >Reporter: Paul Au >Assignee: Paul Au >Priority: Normal > Labels: pull-request-available > Attachments: Screenshot 2023-12-15 at 16-53-40 Apache Cassandra > Apache Cassandra Documentation.png > > > Adding a blog posts announcing the inaugural Catalysts. -- 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] (CASSANDRASC-88) Allow DriverUtils to be pluggable
[ https://issues.apache.org/jira/browse/CASSANDRASC-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-88: -- Labels: pull-request-available (was: ) > Allow DriverUtils to be pluggable > - > > Key: CASSANDRASC-88 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-88 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > Sidecar provides a class to provide utilities to access package private > methods in the datastax driver. However, the nature of the static methods is > that it doesn't allow for plugging a custom implementation. For example, if > we plug a new driver version, these methods might not necessarily work as > APIs might change between version changes. For that reason, we need to > provide a shim layer to access these utilities, and allow pluggability when > needed. -- 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] (CASSANDRASC-87) JMX connectivity is enough to consider host “up” for most endpoints
[ https://issues.apache.org/jira/browse/CASSANDRASC-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-87: -- Labels: pull-request-available (was: ) > JMX connectivity is enough to consider host “up” for most endpoints > - > > Key: CASSANDRASC-87 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-87 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Doug Rohrer >Assignee: Doug Rohrer >Priority: Normal > Labels: pull-request-available > > Today, the Sidecar health check is tied to Native Transport availability for > the instance in question. However, many operations can be successfully > performed without native transport. > Therefore, we should instead use JMX to check for instance availability and > perhaps expose a different endpoint for native transport availability. -- 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-18275) Harry model and in-JVM test for partition-restricted 2i queries
[ https://issues.apache.org/jira/browse/CASSANDRA-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-18275: --- Labels: pull-request-available (was: ) > Harry model and in-JVM test for partition-restricted 2i queries > --- > > Key: CASSANDRA-18275 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18275 > Project: Cassandra > Issue Type: Task > Components: Feature/2i Index, Test/fuzz >Reporter: Caleb Rackliffe >Assignee: Caleb Rackliffe >Priority: Normal > Labels: pull-request-available > Fix For: 5.x > > > The smallest useful scope for Harry testing w/ 2i would be to cover queries > within large partitions. Creating a model to do this should also be easier > than it would be for the “global” query case, so it seems like a good place > to start. The goal here should be to create something that can simply be run > for a specified amount of time as an in-JVM test and be run going forward as > part of our normal CI process. -- 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] (CASSANDRASC-86) Startup Validation Failures when Checking Sidecar Connectivity
[ https://issues.apache.org/jira/browse/CASSANDRASC-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-86: -- Labels: pull-request-available (was: ) > Startup Validation Failures when Checking Sidecar Connectivity > -- > > Key: CASSANDRASC-86 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-86 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Yuriy Semchyshyn >Priority: Normal > Labels: pull-request-available > > We have experienced repeated startup validation failures caused by Sidecar > health checks for some jobs with a large number of Spark executors. > These failures are likely caused by the thundering herd problem, and have > been so far worked around by disabling startup validations altogether. > In order to prevent them going forward, a random delay needs to be added > between retries of health checks in Sidecar client. > It is also worth increasing the overall timeout for Sidecar health checks > from current 30 seconds to 60 seconds. -- 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-18888) Implement CommandStore state reloading on startup
[ https://issues.apache.org/jira/browse/CASSANDRA-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-1: --- Labels: pull-request-available (was: ) > Implement CommandStore state reloading on startup > - > > Key: CASSANDRA-1 > URL: https://issues.apache.org/jira/browse/CASSANDRA-1 > Project: Cassandra > Issue Type: New Feature > Components: Accord >Reporter: Aleksey Yeschenko >Assignee: Aleksey Yeschenko >Priority: Normal > Labels: pull-request-available > > Implement CommandStore state reloading on startup. Selectively replay message > log to restore any missing rows in accord system tables that hadn't made it > to disk due to abnormal node termination, and rehydrate the progress log. -- 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-19054) WEBSITE - Add Cassandra Catalyst page and blog
[ https://issues.apache.org/jira/browse/CASSANDRA-19054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-19054: --- Labels: pull-request-available (was: ) > WEBSITE - Add Cassandra Catalyst page and blog > -- > > Key: CASSANDRA-19054 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19054 > Project: Cassandra > Issue Type: Task > Components: Documentation/Blog, Documentation/Website >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > > This ticket is to capture the work associated with creating a new page for > the Cassandra Catalyst program and it's associated blog. > > Preferably, the blog and page are live as of *November 27.* Please contact > me, suggest changes, or correct the date when possible in the pull request > for the appropriate time that the blog will go live (on both the blog.adoc > and the blog post's file). -- 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-19041) BLOG - 3 Cassandra website blogs
[ https://issues.apache.org/jira/browse/CASSANDRA-19041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-19041: --- Labels: pull-request-available (was: ) > BLOG - 3 Cassandra website blogs > > > Key: CASSANDRA-19041 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19041 > Project: Cassandra > Issue Type: Task >Reporter: Diogenese Topper >Priority: Normal > Labels: pull-request-available > -- 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] (CASSANDRASC-84) Expose additional node settings
[
https://issues.apache.org/jira/browse/CASSANDRASC-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-84:
--
Labels: pull-request-available (was: )
> Expose additional node settings
> ---
>
> Key: CASSANDRASC-84
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-84
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Rest API
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Labels: pull-request-available
>
> Sidecar exposes settings from the Cassandra node via the node settings API
> endpoint. The information exposed is limited, and we need to start exposing
> additional information from the {{system.local}} table, for example
> {{datacenter}} information, owned token ranges, and the local address and
> port for the native protocol. This information can be consumed by Sidecar
> itself, as well as the Cassandra Analytics library.
--
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] (CASSANDRASC-82) Expose additional SSL configuration options for the Sidecar Service
[
https://issues.apache.org/jira/browse/CASSANDRASC-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-82:
--
Labels: low-hanging-fruit lowhanging-fruit pull-request-available (was:
low-hanging-fruit lowhanging-fruit)
> Expose additional SSL configuration options for the Sidecar Service
> ---
>
> Key: CASSANDRASC-82
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-82
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
>Reporter: Francisco Guerrero
>Priority: Normal
> Labels: low-hanging-fruit, lowhanging-fruit,
> pull-request-available
>
> Sidecar exposes some SSL configuration options, but there are additional
> options that Sidecar should be exposing for users. Similar to what Cassandra
> offers in terms of configurations, we should be able to configure
> {{cipher_suites}} as well as {{accepted_protocols}} under SSL configuration.
> Additionally, we should explore if there are any other SSL knobs that
> Cassandra exposes that Sidecar doesn't and add it as part of this jira.
--
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] (CASSANDRASC-83) Require gossip to be enabled for ring and token ranges mapping endpoints
[ https://issues.apache.org/jira/browse/CASSANDRASC-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-83: -- Labels: pull-request-available (was: ) > Require gossip to be enabled for ring and token ranges mapping endpoints > > > Key: CASSANDRASC-83 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-83 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > The ring and token ranges mapping endpoints leverage JMX to produce the > payload. Ring and token ranges mapping information is derived from gossip > information available to the Cassandra instance. If gossip has been disabled, > the information might provide an inconsistent view of the cluster which is > undesirable. We should instead return a 503 (Service Unavailable) to the > client whenever the client tries to access these endpoints and gossip has > been disabled. -- 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] (CASSANDRASC-75) Shaded Sidecar client should shade Jackson completely to avoid incompatibility issues
[ https://issues.apache.org/jira/browse/CASSANDRASC-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-75: -- Labels: pull-request-available (was: ) > Shaded Sidecar client should shade Jackson completely to avoid > incompatibility issues > - > > Key: CASSANDRASC-75 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-75 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Doug Rohrer >Assignee: Doug Rohrer >Priority: Normal > Labels: pull-request-available > Fix For: 1.0 > > > Before, we were shading almost all of Jackson but left the annotations > unshaded/relocated. However, this causes problems in older Spark environments > where the annotations in the class path don’t quite match what the other > shaded parts of Jackson expect (missing classes being the most serious > issue). This can cause the library to fail on certain Spark versions. > > We should shade +all+ of Jackson in the shaded client to prevent these issues. -- 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] (CASSANDRASC-81) Improve TokenRangeReplicasResponse payload
[
https://issues.apache.org/jira/browse/CASSANDRASC-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-81:
--
Labels: pull-request-available (was: )
> Improve TokenRangeReplicasResponse payload
> --
>
> Key: CASSANDRASC-81
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-81
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Labels: pull-request-available
>
> The {{TokenRangeReplicasResponse}} returns {{ReplicaMetadata}}. This
> information is used by clients to lookup the metadata. The lookup is done
> with the replica information, which consists of the host {{ip:port}}. Clients
> are looping over the {{ReplicaMetadata}} list and matching IP and port to
> retrieve the metadata object. Instead, we can improve the payload by changing
> the data structure from a list to a map, and have clients lookup by the
> replica (ip + port), without having to loop.
--
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-18471) CEP-15 Accord: NotWitnessed commands can receive an invalidate promise but would return Zero instead
[
https://issues.apache.org/jira/browse/CASSANDRA-18471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRA-18471:
---
Labels: pull-request-available (was: )
> CEP-15 Accord: NotWitnessed commands can receive an invalidate promise but
> would return Zero instead
>
>
> Key: CASSANDRA-18471
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18471
> Project: Cassandra
> Issue Type: Bug
> Components: Accord
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Labels: pull-request-available
> Fix For: 5.0, 5.0-alpha1
>
>
> While working on CASSANDRA-18451 I hit the following failure
> {code}
> Failed on seed -5929214838499924343
> accord.burn.SimulationException: Failed on seed -5929214838499924343
> Caused by: java.lang.AssertionError: Unexpected exception encountered
> at
> accord.impl.basic.PropagatingPendingQueue.poll(PropagatingPendingQueue.java:73)
> at accord.impl.basic.Cluster.processPending(Cluster.java:179)
> at accord.impl.basic.Cluster.run(Cluster.java:296)
> at accord.burn.BurnTest.burn(BurnTest.java:309)
> at accord.burn.BurnTest.run(BurnTest.java:386)
> at accord.burn.BurnTest.testOne(BurnTest.java:372)
> Suppressed: java.lang.IllegalStateException: Received replies from a
> node that must have known the route, but that did not include it
> at accord.coordinate.Invalidate.invalidate(Invalidate.java:204)
> at accord.coordinate.Invalidate.handle(Invalidate.java:131)
> at accord.coordinate.Invalidate.onSuccess(Invalidate.java:105)
> at accord.coordinate.Invalidate.onSuccess(Invalidate.java:51)
> at
> accord.impl.basic.Cluster.lambda$processNext$1(Cluster.java:209)
> at accord.impl.basic.Cluster.now(Cluster.java:260)
> at accord.impl.basic.Cluster.processNext(Cluster.java:206)
> at accord.impl.basic.Cluster.processPending(Cluster.java:183)
> {code}
> In a debugger was able to figure out the state and create a unit test to hit
> the same situation
> {code}
> class InvalidateTest
> {
> @Test
> void test() throws ExecutionException
> {
> try (MockCluster cluster =
> MockCluster.builder().replication(2).nodes(2).build())
> {
> Node n1 = cluster.get(1);
> Node n2 = cluster.get(2);
> RoutingKey n1RoutingKey =
> n1.topology().current().get(0).range.end();
> IntKey.Raw n1key = IntKey.key(((IntKey.Routing)
> n1RoutingKey).key);
> RoutingKey n2RoutingKey =
> n1.topology().current().get(1).range.end();
> IntKey.Raw n2key = IntKey.key(((IntKey.Routing)
> n2RoutingKey).key);
> Keys keys = Keys.of(n1key, n2key);
> Node coordinator = n1;
> TxnId txnId = coordinator.nextTxnId(Txn.Kind.Read,
> Routable.Domain.Key);
> Txn txn = readOnly(keys);
>
> AsyncChains.getUninterruptibly(n2.commandStores().unsafeForKey(n2key).execute(PreLoadContext.contextFor(txnId,
> keys), store -> {
> Ranges ranges = store.ranges().currentRanges();
> PartialTxn partial = txn.slice(ranges, true);
> FullKeyRoute route = keys.toRoute(n2RoutingKey);
> //RoutingKey progressKey = n2RoutingKey.toUnseekable(); // if
> this is non-null this passes
> RoutingKey progressKey = null;
> CheckedCommands.preaccept(store, txnId, partial, route,
> progressKey);
> CheckedCommands.accept(store, txnId, Ballot.ZERO,
> route.slice(ranges), partial.keys().slice(ranges), progressKey, txnId,
> PartialDeps.builder(ranges).build());
> }));
> AsyncChains.getUninterruptibly(new AsyncChains.Head() {
> @Override
> protected void start(BiConsumer
> callback) {
> Invalidate.invalidate(coordinator, txnId,
> keys.toUnseekables(), callback);
> }
> });
> }
> }
> private static Txn readOnly(Seekables keys)
> {
> Read read = MockStore.read(keys);
> Query query = Mockito.mock(Query.class);
> return new Txn.InMemory(keys, read, query);
> }
> }
> {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-18378) CEP-15 (Accord) accord.messages.Defer rejects Recurrent retry of Commit
[
https://issues.apache.org/jira/browse/CASSANDRA-18378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRA-18378:
---
Labels: pull-request-available (was: )
> CEP-15 (Accord) accord.messages.Defer rejects Recurrent retry of Commit
> ---
>
> Key: CASSANDRA-18378
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18378
> Project: Cassandra
> Issue Type: Bug
> Components: Accord
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Labels: pull-request-available
> Fix For: NA
>
>
> {code}
> java.lang.IllegalStateException: Recurrent retry of Commit{…}
> at accord.messages.Defer.add(Defer.java:63)
> at accord.messages.Commit.apply(Commit.java:167)
> at accord.messages.Commit.apply(Commit.java:42)
> at
> org.apache.cassandra.service.accord.async.AsyncOperation$ForFunction.apply(AsyncOperation.java:321)
> at
> org.apache.cassandra.service.accord.async.AsyncOperation$ForFunction.apply(AsyncOperation.java:308)
> at
> org.apache.cassandra.service.accord.async.AsyncOperation.runInternal(AsyncOperation.java:226)
> at
> org.apache.cassandra.service.accord.async.AsyncOperation.run(AsyncOperation.java:268)
> {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] (CASSANDRASC-79) Sidecar should be able to load metadata even if the local instance is unavailable
[ https://issues.apache.org/jira/browse/CASSANDRASC-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-79: -- Labels: pull-request-available (was: ) > Sidecar should be able to load metadata even if the local instance is > unavailable > - > > Key: CASSANDRASC-79 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-79 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Doug Rohrer >Assignee: Doug Rohrer >Priority: Normal > Labels: pull-request-available > > Today, the sidecar’s CassandraAdapter/CqlSessionProvider uses a load > balancing policy that only allows connections to a single instance configured > for one of the managed instances of Cassandra. However, this is both > unnecessary and potentially harmful, as requests to that instance’s hostname > will fail to retrieve information like keyspace/cluster metadata when that > instance is unavailable, and will not receive any updates to metadata either, > which can cause stale metadata to be used. > Instead, the CqlSessionProvider should take a list of contact points and use > them to connect to the whole cluster (or a subset of nodes) without the > single-instance load balancing policy. Where it is necessary to query an > individual instance (system tables, attempts to check the health of a > particular instance) we can, instead, use the driver’s ability to direct > queries to a specific host on a per-statement basis. -- 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] (CASSANDRASC-78) Fix token-ranges endpoint to handle gossip-info responses without 'status'
[
https://issues.apache.org/jira/browse/CASSANDRASC-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-78:
--
Labels: pull-request-available (was: )
> Fix token-ranges endpoint to handle gossip-info responses without 'status'
> --
>
> Key: CASSANDRASC-78
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-78
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
> Components: Rest API
>Reporter: Arjun Ashok
>Assignee: Arjun Ashok
>Priority: Normal
> Labels: pull-request-available
>
> This is a fix to look for the host status in ‘Status’ and ‘StatusWithPort’
> attributes in GossipInfo response to determine the ‘state’ of the node.
> Currently, we only check for ‘status’ which can be missing from gossipInfo in
> some cases, which will result in a replacement node status to be reported as
> `Joining` instead of `Replacing`.
> eg.
> {code:java}
> Found gossipInfoEntry={generation=1697736379,
> schema=6d6abc83-a600-35a4-8bbe-fe5edca6a63b, rack=rack1, heartbeat=119,
> releaseVersion=4.1.4-SNAPSHOT, hostId=--4000-8000-0006,
> nativeAddressAndPort=127.0.0.6:9042, load=76459.0,
> internalAddressAndPort=127.0.0.6:7012, sstableVersions=big-nb,
> tokens=, dc=datacenter1, netVersion=12,
> statusWithPort=BOOT_REPLACE,127.0.0.5:7012}{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] (CASSANDRASC-77) Upgrade vertx to version 4.4.6
[ https://issues.apache.org/jira/browse/CASSANDRASC-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-77: -- Labels: pull-request-available (was: ) > Upgrade vertx to version 4.4.6 > -- > > Key: CASSANDRASC-77 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-77 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > Vertx 4.4.6 brings new features that we want to bring into Cassandra Sidecar: > 1. Hot reloading of SSL Certificates. With this feature, we can run Cassandra > Sidecar with TLS options configured, and when the certificate is expired, we > can instruct vertx to reload the certificate from disk without having to > restart the process. > 2. Traffic shaping options. This allows to introduce protections for the > service by providing ways to configure ingress/egress limits for the service, > as well as ingress limits for SSTable uploads. -- 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-18912) Specify "since" in all Deprecated annotations
[
https://issues.apache.org/jira/browse/CASSANDRA-18912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRA-18912:
---
Labels: pull-request-available (was: )
> Specify "since" in all Deprecated annotations
> -
>
> Key: CASSANDRA-18912
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18912
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/Core
>Reporter: Stefan Miklosovic
>Assignee: Maxim Muzafarov
>Priority: Normal
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> It would be great if we introduced in 5.0 a change in Deprecated annotations
> like this:
> {code}
> @Deprecated(since = "4.0")
> {code}
> or
> {code}
> @Deprecated(since = "3.11")
> {code}
> The reasoning behind this is that as of now, it is pretty cumbersome to
> figure out what can be removed on the next major version. It has to be,
> basically, done manually every time.
> There is also this parameter available:
> {code}
> @Deprecated(forRemoval = true / false)
> {code}
> which indicates whether the annotated element is subject to removal in a
> future version so we do not need to think about this every time if it is
> eligible for deletion in a next major or not.
> We could then have a check which would ensure that we are not releasing a
> next major with some deprecations introduced two majors before.
--
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-18816) Add support for repair coordinator to retry messages that timeout
[ https://issues.apache.org/jira/browse/CASSANDRA-18816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-18816: --- Labels: pull-request-available (was: ) > Add support for repair coordinator to retry messages that timeout > - > > Key: CASSANDRA-18816 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18816 > Project: Cassandra > Issue Type: Improvement > Components: Consistency/Repair >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Fix For: 5.0-alpha2 > > Time Spent: 13h 10m > Remaining Estimate: 0h > > Now that CASSANDRA-15399 is in, most of the repair messages have a state that > they can check against to make message delivery idempotent, allowing the > coordinator to retry such messages; a few of the most critical messages to > retry are: PREPARE_MSG, VALIDATION_REQ, VALIDATION_RSP, SYNC_REQ, and > SYNC_RSP. > With this I propose making the coordinator able to retry these key messages > to try and make repair more resilient to ephemeral issues. -- 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] (CASSANDRASC-74) Unable to stream index file components
[ https://issues.apache.org/jira/browse/CASSANDRASC-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-74: -- Labels: pull-request-available (was: ) > Unable to stream index file components > -- > > Key: CASSANDRASC-74 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-74 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > The stream SSTables components API fails on secondary index files. When a > table has a secondary index defined, and we list the snapshot including the > secondary index files, and then try to stream the SSTable components, we will > see a 404 (Not Found) error. -- 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-18874) Add Jepson's Elle to Accord and Paxos validation
[ https://issues.apache.org/jira/browse/CASSANDRA-18874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-18874: --- Labels: pull-request-available (was: ) > Add Jepson's Elle to Accord and Paxos validation > > > Key: CASSANDRA-18874 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18874 > Project: Cassandra > Issue Type: Improvement > Components: Accord, Feature/Lightweight Transactions >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Fix For: 5.x > > > Paxos and Accord both use a custom validator to make sure we offer Strict > Serializability, but to increase confidence we should use external validators > as well, such as Jepson’s Elle. -- 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] (CASSANDRASC-73) Update token-ranges endpoint to return additional instance metadata
[ https://issues.apache.org/jira/browse/CASSANDRASC-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-73: -- Labels: pull-request-available (was: ) > Update token-ranges endpoint to return additional instance metadata > --- > > Key: CASSANDRASC-73 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-73 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Labels: pull-request-available > > Sidecar `token-range-replicas` endpoint to return the following additional > metadata for each instance: > * State. eg Normal, Joining, Leaving > * Status. eg. Up, Down > * Address: Replica host and port > * Name: Node name resolved from the above IP address -- 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-18850) Building a Cassandra website fails when running on arm64
[
https://issues.apache.org/jira/browse/CASSANDRA-18850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRA-18850:
---
Labels: pull-request-available (was: )
> Building a Cassandra website fails when running on arm64
>
>
> Key: CASSANDRA-18850
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18850
> Project: Cassandra
> Issue Type: Task
> Components: Documentation/Website
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Normal
> Labels: pull-request-available
>
> It seems to me that building a Cassandra website is not supported when
> running on arm64 (tested on Mac M1). Running the build command throws the
> following exceptions below.
> Docker Version 4.23.0 (120376), the experimental feature "use Rosetta for
> x86/amd64 emulation on Apple Silicon" is enabled.
> {code:java}
> m@m1 cassandra-website % ./run.sh website build
> Server Docker Engine version: 20.10.21
> Executing docker command:
> docker build -f ./site-content/Dockerfile -t apache/cassandra-website:latest
> ./site-content/
> [+] Building 7.2s (12/23)
>
>
>
> => [internal] load build definition from Dockerfile
>
>
> 0.0s
> => => transferring dockerfile: 5.03kB
>
>
> 0.0s
> => [internal] load .dockerignore
>
>
> 0.0s
> => => transferring context: 2B
>
>
> 0.0s
> => [internal] load metadata for docker.io/library/ubuntu:18.04
>
>
> 0.6s
> => [ 1/19] FROM
> docker.io/library/ubuntu:18.04@sha256:152dc042452c496007f07ca9127571cb9c29697f42acbfad72324b2bb2e43c98
>
>
> 0.0s
> => [internal] load build context
>
>
> 0.0s
> => => transferring context: 42B
>
>
> 0.0s
> => CACHED [ 2/19] RUN echo "Building with arguments:" && echo " -
> BUILD_USER_ARG=build" && echo " - UID_ARG=1000" && echo " -
> GID_ARG=1000" && echo " - NODE_VERSION_ARG=v12.16.2" && echo " -
> ENTR_VERSION_ARG=4.6"
> 0.0s
> => CACHED [ 3/19] RUN apt update && apt install -y openjdk-8-jdk
> openjdk-11-jdk python3 python3-pip ant
> ant-optional make git gpg wget sudo
> 0.0s
> => CACHED [ 4/19] RUN apt-get install -y python-markupsafe
>
[jira] [Updated] (CASSANDRASC-72) [CircleCI] Split unit tests and integration tests
[ https://issues.apache.org/jira/browse/CASSANDRASC-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-72: -- Labels: pull-request-available (was: ) > [CircleCI] Split unit tests and integration tests > - > > Key: CASSANDRASC-72 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-72 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > Fix For: 1.0 > > > As the number of integration tests continues to grow, it is desirable to > split unit tests and integration tests. It is also desirable to parallelize > integration tests, each integration test should be its own job. The goals of > this improvement are: > * Fail fast on checkstyle or minor errors > * Speed up test runtime by running integration tests in parallel > * Isolate failing tests to specific combinations of 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] [Updated] (CASSANDRA-18804) (Accord): Bug fixes from CASSANDRA-18675 to better support adding keyspaces
[ https://issues.apache.org/jira/browse/CASSANDRA-18804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-18804: --- Labels: pull-request-available (was: ) > (Accord): Bug fixes from CASSANDRA-18675 to better support adding keyspaces > --- > > Key: CASSANDRA-18804 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18804 > Project: Cassandra > Issue Type: Bug > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Fix For: 5.x > > > This work is forking CASSANDRA-18675 and pulling out the initial work and bug > fixes, but does not actually include drop keyspace support, but does include > the testing for add keyspaces. -- 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] (CASSANDRASC-68) Add Metrics publisher interface to Sidecar to expose metrics for capture
[ https://issues.apache.org/jira/browse/CASSANDRASC-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-68: -- Labels: pull-request-available (was: ) > Add Metrics publisher interface to Sidecar to expose metrics for capture > > > Key: CASSANDRASC-68 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-68 > Project: Sidecar for Apache Cassandra > Issue Type: New Feature > Components: Rest API >Reporter: Saranya Krishnakumar >Assignee: Saranya Krishnakumar >Priority: High > Labels: pull-request-available > > We need metrics publisher interface in Sidecar to capture some of the metrics > like bytes written/streamed. > PR: [https://github.com/apache/cassandra-sidecar/pull/64] > CircleCI run: > [https://app.circleci.com/pipelines/github/sarankk/cassandra-sidecar] > -- 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] (CASSANDRASC-71) Allow configuring permissions for uploaded SSTables
[
https://issues.apache.org/jira/browse/CASSANDRASC-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-71:
--
Labels: pull-request-available (was: )
> Allow configuring permissions for uploaded SSTables
> ---
>
> Key: CASSANDRASC-71
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-71
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Labels: pull-request-available
>
> When uploading SSTables, the default permissions are being set. Currently,
> 644 or {{rw---}} are the default permissions. Ideally, a user should be
> able to configure the desired file permissions used during an SSTable upload.
> This allows the Cassandra process to import the SSTable with the permissions
> suitable for the import process.
--
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] (CASSANDRASC-70) Add Client Methods for Obtaining Sidecar and Cassandra Health
[ https://issues.apache.org/jira/browse/CASSANDRASC-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-70: -- Labels: pull-request-available (was: ) > Add Client Methods for Obtaining Sidecar and Cassandra Health > - > > Key: CASSANDRASC-70 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-70 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Yuriy Semchyshyn >Priority: Normal > Labels: pull-request-available > > Methods for obtaining Sidecar and Cassandra health need to be added to the > client. > Both of these methods will be used for start-up validation by the Analytics > library. -- 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-18783) CEP-15 (C*): when loading commands that have empty waiting_on, make sure not to loose the partial deps
[
https://issues.apache.org/jira/browse/CASSANDRA-18783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRA-18783:
---
Labels: pull-request-available (was: )
> CEP-15 (C*): when loading commands that have empty waiting_on, make sure not
> to loose the partial deps
> --
>
> Key: CASSANDRA-18783
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18783
> Project: Cassandra
> Issue Type: Bug
> Components: Accord
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Labels: pull-request-available
> Fix For: 5.x
>
>
> This was found in benchmark clusters
> {code}
> java.lang.IllegalStateException: Deps do not match; expected {}, {} ==
> [tlp_stress:[(-1182483594468561006,-472993437787424406]]]:{tlp_stress:DecoratedKey(-136068852656106,
> 3030312e302e35383730313035):[[17,1692599889087003,0,1]]}, {}
> accord.utils.Invariants.illegalState(Invariants.java:44)
> accord.utils.Invariants.checkState(Invariants.java:133)
> accord.local.Command$Committed.(Command.java:826)
> accord.local.Command$Committed.(Command.java:817)
> accord.local.Command$Executed.(Command.java:905)
> accord.local.Command$Executed.executed(Command.java:951)
> accord.local.Command$SerializerSupport.executed(Command.java:165)
>
> org.apache.cassandra.service.accord.AccordKeyspace.loadCommand(AccordKeyspace.java:1197)
> {code}
> The root cause is that “empty” waiting_on drops the partial deps when we
> write/load but this becomes an issue for Command.Committed as it double
> checks partial_deps == waiting_on.deps
--
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] (CASSANDRASC-69) Refactor Configuration
[
https://issues.apache.org/jira/browse/CASSANDRASC-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-69:
--
Labels: pull-request-available (was: )
> Refactor Configuration
> --
>
> Key: CASSANDRASC-69
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-69
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Labels: pull-request-available
>
> Currently, the Sidecar Configuration is provided via a yaml file. The yaml
> file is parsed and a the configuration is used during the Sidecar application
> runtime.
> The configuration parsing is done manually, and adding a new configuration to
> the yaml file has become a big task where multiple files need to be touched.
> Ideally, we should add the configuration POJOs needed for new configurations
> and add the new fields in the yaml file.
> Additionally, we are leaking the configuration implementation to the
> {{InstancesConfig}}. We should improve the separation of concerns from the
> yaml configuration and the instances configuration.
--
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-18618) Update tasks configuration to run checks locally when requested
[ https://issues.apache.org/jira/browse/CASSANDRA-18618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-18618: --- Labels: pull-request-available (was: ) > Update tasks configuration to run checks locally when requested > --- > > Key: CASSANDRA-18618 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18618 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Jacek Lewandowski >Assignee: Jacek Lewandowski >Priority: Normal > Labels: pull-request-available > Fix For: 5.0 > > Time Spent: 7h 50m > Remaining Estimate: 0h > > Currently CheckStyle and RAT are run with almost every single Ant target, > which is annoying as when developing locally. The targets should be clear - > "test" - runs the tests, "jar" - builds the project and creates jars, and > then we should have a task "check" which runs all the static analysis, that > is CheckStyle, RAT and Eclipse-Warnings (or whatever we decide to replace > Eclipse-Warnings with). > Such goal should be include in "artifacts" and we should run it instead of > "eclipse-warnings" on CircleCI. This way building, static analysis and > testings are clearly separated. -- 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-18727) JMXUtil.getJmxConnector should retry connection attempts
[ https://issues.apache.org/jira/browse/CASSANDRA-18727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-18727: --- Labels: pull-request-available (was: ) > JMXUtil.getJmxConnector should retry connection attempts > - > > Key: CASSANDRA-18727 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18727 > Project: Cassandra > Issue Type: Improvement >Reporter: Doug Rohrer >Priority: Normal > Labels: pull-request-available > > We previously added a JMXUtil class that makes it easy for dtests to get a > JMX connection. It ends up that occasionally the JMX server side needs more > time to start up (especially when stopping and restarting instances, which > we’re now doing more frequently, or when stopping and restarting the whole > cluster). In these cases, JMXUtil.getJmxConnector can fail, when it would be > possible to connect if a retry mechanism was added. We should add this > capability to the in-jvm dtest framework. > -- 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] (CASSANDRASC-67) Fix relocation of native libraries for vertx-client-shaded
[
https://issues.apache.org/jira/browse/CASSANDRASC-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-67:
--
Labels: pull-request-available (was: )
> Fix relocation of native libraries for vertx-client-shaded
> --
>
> Key: CASSANDRASC-67
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-67
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
> Components: Configuration
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Labels: pull-request-available
>
> OpenSSL is currently unavailable in the {{vertx-client-shaded}} library. This
> is due to the incorrect relocation of the netty native libraries under
> {{META-INF/native/libnetty}}. In order to utilize native libraries, we need
> to fix the relocation and ensure that relocation is properly configured by
> adding tests guaranteeing OpenSSL is loading correctly.
--
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] (CASSANDRASC-66) Fix failing unit tests in Apache CI
[
https://issues.apache.org/jira/browse/CASSANDRASC-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-66:
--
Labels: pull-request-available (was: )
> Fix failing unit tests in Apache CI
> ---
>
> Key: CASSANDRASC-66
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-66
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Labels: pull-request-available
>
> Currently, the tests under
> {{org.apache.cassandra.sidecar.HealthServiceSslTest}} [are
> failing|https://ci-cassandra.apache.org/job/cassandra~sidecar/42/] when
> running inside ASF's CI. The logs show that some resources (keystore and
> truststore) are not found. This is causing the tests to fail.
--
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] (CASSANDRASC-64) File descriptor is not being closed on MD5 checksum
[ https://issues.apache.org/jira/browse/CASSANDRASC-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-64: -- Labels: pull-request-available (was: ) > File descriptor is not being closed on MD5 checksum > --- > > Key: CASSANDRASC-64 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-64 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > The file descriptor is not being closed when an MD5 checksum is performed > during SSTable upload. This could prevent the Sidecar JVM to not be able to > open more files when the ulimit has been reached -- 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] (CASSANDRASC-63) Support credential rotation in JmxClient
[
https://issues.apache.org/jira/browse/CASSANDRASC-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-63:
--
Labels: pull-request-available (was: )
> Support credential rotation in JmxClient
>
>
> Key: CASSANDRASC-63
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-63
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Labels: pull-request-available
>
> JMX credentials in a Cassandra instance can be rotated on a cadence, on every
> bounce, or by some other means. In those cases, the {{JmxClient}} will no
> longer be able to connect to the instance completely losing the ability to
> talk to that instance.
> In those cases, it is desirable for the {{JmxClient}} to support changes to
> be able to continue working correctly, without any potential downtime to the
> Sidecar service.
--
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] (CASSANDRASC-60) Sidecar API to expose cluster topology information
[ https://issues.apache.org/jira/browse/CASSANDRASC-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-60: -- Labels: pull-request-available (was: ) > Sidecar API to expose cluster topology information > -- > > Key: CASSANDRASC-60 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-60 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Labels: pull-request-available > > This API will expose token ranges and the corresponding read and write > replicas. The write replica-set token ranges will include natural and pending > ranges, so clients can have a complete view of the cluster as nodes are > joining or leaving. -- 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] (CASSANDRASC-62) Fix uncaught exception in sidecar client that causes request to freeze
[ https://issues.apache.org/jira/browse/CASSANDRASC-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-62: -- Labels: pull-request-available (was: ) > Fix uncaught exception in sidecar client that causes request to freeze > -- > > Key: CASSANDRASC-62 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-62 > Project: Sidecar for Apache Cassandra > Issue Type: Bug > Components: Rest API >Reporter: Yifan Cai >Assignee: Yifan Cai >Priority: Normal > Labels: pull-request-available > > When processing response, the sidecar client does not catch throwable rather > than IOException. The uncaught exception leads to the response future never > gets closes and the client that is waiting on the completion of it never make > progress. > The fix is to catch all throwable instead of only IOException. -- 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] (CASSANDRASC-61) Add Release Audit Tool (RAT) plugin to Sidecar
[
https://issues.apache.org/jira/browse/CASSANDRASC-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-61:
--
Labels: pull-request-available (was: )
> Add Release Audit Tool (RAT) plugin to Sidecar
> --
>
> Key: CASSANDRASC-61
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-61
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Labels: pull-request-available
>
> Add the Release Audit Tool plugin to Cassandra Sidecar to automate the
> {{check}} process and make it part of the regular Sidecar build.
--
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] (CASSANDRASC-59) Expose JMX host and port from JMXClient
[ https://issues.apache.org/jira/browse/CASSANDRASC-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-59: -- Labels: pull-request-available (was: ) > Expose JMX host and port from JMXClient > --- > > Key: CASSANDRASC-59 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-59 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > Many integrations require the JMX host and port configured for a given JMX > client. It is desired that this information is available in the > ICassandraDelegate. -- 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] (CASSANDRASC-58) Support retries in Sidecar Client when MD5 checksum is mismatched
[ https://issues.apache.org/jira/browse/CASSANDRASC-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-58: -- Labels: pull-request-available (was: ) > Support retries in Sidecar Client when MD5 checksum is mismatched > - > > Key: CASSANDRASC-58 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-58 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > In rare occasions an SSTable upload will get corrupted during upload. Bit > flips are expected to occur occasionally while transmitting the SSTables from > the client to the server. The current behavior of the Sidecar Client in those > situations is to fail fast without any retries. > We want to support Sidecar Client retries when checksum mismatch occurs > during SSTable upload. -- 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] (CASSANDRASC-57) Remove RESTEasy
[ https://issues.apache.org/jira/browse/CASSANDRASC-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-57: -- Labels: pull-request-available (was: ) > Remove RESTEasy > --- > > Key: CASSANDRASC-57 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-57 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > RESTEasy has been replaced by vertx handlers in the project. Additionally, > Vertx offers OpenAPI support natively [1], which can be considered for future > improvements to the Sidecar project. > [1] https://vertx.io/docs/vertx-web-openapi/java/ -- 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] (CASSANDRASC-56) Create staging directory if it doesn't exists
[ https://issues.apache.org/jira/browse/CASSANDRASC-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-56: -- Labels: pull-request-available (was: ) > Create staging directory if it doesn't exists > - > > Key: CASSANDRASC-56 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-56 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Configuration >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > During SSTable upload, the upload will fail if the configured staging > directory does not exist. When this occurs we must manually have to create > the directory, which increases the configuration toil. To improve the > experience, it is desired that Sidecar creates the staging directory if it > doesn't exist. -- 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] (CASSANDRASC-55) Extract integration test framework for use in other projects
[ https://issues.apache.org/jira/browse/CASSANDRASC-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-55: -- Labels: pull-request-available (was: ) > Extract integration test framework for use in other projects > - > > Key: CASSANDRASC-55 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-55 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Doug Rohrer >Priority: Normal > Labels: pull-request-available > > The CassandraIntegrationTest implementation in the Sidecar project can be > used in the Analytics project as well. > Extract the necessary classes into their own project so they can be more > easily used in other projects. -- 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] (CASSANDRASC-54) Add NOTICE.txt file
[ https://issues.apache.org/jira/browse/CASSANDRASC-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-54: -- Labels: pull-request-available (was: ) > Add NOTICE.txt file > --- > > Key: CASSANDRASC-54 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-54 > Project: Sidecar for Apache Cassandra > Issue Type: Task > Components: Documentation >Reporter: Francisco Guerrero >Assignee: Francisco Guerrero >Priority: Normal > Labels: pull-request-available > > The Cassandra Sidecar project is missing the NOTICE.txt file required for > compliance with the ASF guidance -- 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] (CASSANDRASC-53) [Sidecar Client] Allow unknown fields in the response
[
https://issues.apache.org/jira/browse/CASSANDRASC-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-53:
--
Labels: pull-request-available (was: )
> [Sidecar Client] Allow unknown fields in the response
> -
>
> Key: CASSANDRASC-53
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-53
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Configuration
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Labels: pull-request-available
>
> While testing CASSANDRASC-52 on the server side, the Sidecar client based off
> of {{trunk}} failed to deserialize the JSON payload with error
> {code:java}
> Caused by:
> o.a.c.sidecar.client.shaded.com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException:
> Unrecognized field "sidecar" (class
> org.apache.cassandra.sidecar.common.NodeSettings), not marked as ignorable (2
> known properties: "releaseVersion", "partitioner"])
> at [Source:
> (byte[])"{"releaseVersion":"4.0.9-SNAPSHOT","partitioner":"org.apache.cassandra.dht.Murmur3Partitioner","sidecar":{"version":"1.0-SNAPSHOT"}}";
> line: 1, column: 107] (through reference chain:
> org.apache.cassandra.sidecar.common.NodeSettings["sidecar"])
> at
> o.a.c.sidecar.client.shaded.com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException.from(UnrecognizedPropertyException.java:61)
> at
> o.a.c.sidecar.client.shaded.com.fasterxml.jackson.databind.DeserializationContext.handleUnknownProperty(DeserializationContext.java:1132)
> {code}
> As we are evolving the code, we expect the API on the server side to evolve.
> The deployed clients need to tolerate these new fields in the response JSON
> payload to continue working correctly.
--
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] (CASSANDRASC-51) Leverage in-jvm dtest framework for improved Sidecar testing
[ https://issues.apache.org/jira/browse/CASSANDRASC-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-51: -- Labels: pull-request-available (was: ) > Leverage in-jvm dtest framework for improved Sidecar testing > > > Key: CASSANDRASC-51 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-51 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Doug Rohrer >Priority: Normal > Labels: pull-request-available > > Today, the sidecar uses TestContainers > ([testcontainers.org|http://testcontainers.org/]) and a single-node, > single-data-directory Cassandra instance for all of its tests. While this has > worked well so far, it is incapable of doing some of the more complex testing > necessary to validate new endpoints and requires Docker locally and special > CircleCI setup for CI builds. > > Now that the in-jvm dtest framework supports JMX, we can leverage it to do > our testing in stead. It will enable us to do multi-node testing and exercise > code paths under conditions like joining/leaving/moving nodes, which is > critical for correctness. -- 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] (CASSANDRASC-52) Sidecar Should Return Own Version in Node Settings
[ https://issues.apache.org/jira/browse/CASSANDRASC-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRASC-52: -- Labels: pull-request-available (was: ) > Sidecar Should Return Own Version in Node Settings > -- > > Key: CASSANDRASC-52 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-52 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement >Reporter: Yuriy Semchyshyn >Assignee: Dinesh Joshi >Priority: Normal > Labels: pull-request-available > > As of now, Sidecar's node settings endpoint returns Cassandra version and > partitioner only. > Sidecar should add its own build version into the node settings object for > reporting purposes. -- 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-18537) Add JMX utility class to in-jvm dtest to ease development of new tests using JMX
[ https://issues.apache.org/jira/browse/CASSANDRA-18537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-18537: --- Labels: pull-request-available (was: ) > Add JMX utility class to in-jvm dtest to ease development of new tests using > JMX > > > Key: CASSANDRA-18537 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18537 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java >Reporter: Doug Rohrer >Priority: Normal > Labels: pull-request-available > Fix For: NA > > > While reviewing CASSANDRA-18511, some repetitive code was identified across > the 4 branches, and 2 different tests, that would also be repeated for any > new usages of the JMX support in the in-jvm dtest framework. Therefore, a > utility class should be added to the dtest-api's `shared` package that will > simplify some of this repetitive and error-prone 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-18519) CEP-15: (C*) Add notion of CommandsForRanges and make this durable in C*
[ https://issues.apache.org/jira/browse/CASSANDRA-18519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-18519: --- Labels: pull-request-available (was: ) > CEP-15: (C*) Add notion of CommandsForRanges and make this durable in C* > > > Key: CASSANDRA-18519 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18519 > Project: Cassandra > Issue Type: Task > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Fix For: 5.x > > > To add support for range transactions in C* we need to make sure > 1) their state is durable and can be recovered on restart > 2) have some way to find all CommandsForKey that are contained in the range > transaction range > 3) have some way to find all CommandsForRange that intersect this range > To do this, I propose the following > 1) Create a new commands_for_range table that stores: (store, range) -> > list — this is byId, not sure if repair needs > byExecuteId as well > 2) For C*, store a in-memory mapping of Range -> List, and on-boot > repopulate this cache. This then can be used to construct the > CommandsForRange needed by the transaction. This makes an assumption that > many ranges will not exist, at least for the time being. > 3) Change commands_for_keys to use LocalPartitioner, and order the table by > (store, key) > 4) When C* sees a range transaction, find all keys that are contained by the > range by running the logical query "SELECT key FROM commands_for_keys WHERE > key BETWEEN range.start AND range.end". Implementation has to make sure to > handle many keys (may need to partition the range to increase parallel > access, and may need to page through the table to see all keys (aka multiple > ReadCommands)). Once all keys are found, then must load into the > CommandsForKeys cache > For #4, https://github.com/apache/cassandra-accord/pull/27 maybe able to > optimize the logic to lazy load only what is actually needed rather than load > the whole world -- 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] (CASSANDRASC-50) Remove deprecate health endpoint containing instance segment
[
https://issues.apache.org/jira/browse/CASSANDRASC-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated CASSANDRASC-50:
--
Labels: pull-request-available (was: )
> Remove deprecate health endpoint containing instance segment
>
>
> Key: CASSANDRASC-50
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-50
> Project: Sidecar for Apache Cassandra
> Issue Type: Improvement
> Components: Rest API
>Reporter: Francisco Guerrero
>Assignee: Francisco Guerrero
>Priority: Normal
> Labels: pull-request-available
>
> The Cassandra Health endpoint containing the instance segment in the path
> usage is deprecated. This endpoint is currently unused and it is replaced by
> the health endpoint with the {{instanceId}} query string parameter. Since the
> {{instanceId}} is optional we move the path param (mandatory) to the query
> param (optional).
--
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-18511) Add support for JMX in the in-jvm dtest framework
[ https://issues.apache.org/jira/browse/CASSANDRA-18511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-18511: --- Labels: pull-request-available (was: ) > Add support for JMX in the in-jvm dtest framework > - > > Key: CASSANDRA-18511 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18511 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java >Reporter: Doug Rohrer >Assignee: Doug Rohrer >Priority: Normal > Labels: pull-request-available > Fix For: 3.11.x, 4.0.x, 4.1.x, 5.0 > > > In many cases, it would be useful to be able to enable JMX endpoints within > the in-jvm dtest framework, including the existing JMX Getter test, which > used to simply spin up a JMX registry and then leave it running. There are > quite a few JMX-related functions that don’t have tests today, and some > external usages of the in-jvm dtest framework could also benefit from > exposing JMX like we did Native before. -- 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-18488) WEBSITE - Replace Forward banner with Summit banner on pages
[ https://issues.apache.org/jira/browse/CASSANDRA-18488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-18488: --- Labels: pull-request-available (was: ) > WEBSITE - Replace Forward banner with Summit banner on pages > > > Key: CASSANDRA-18488 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18488 > Project: Cassandra > Issue Type: Task > Components: Documentation/Website >Reporter: Stefano Lottini >Assignee: Stefano Lottini >Priority: Normal > Labels: pull-request-available > Fix For: NA > > Attachments: banner_on_events_page.png, banner_on_index_page.png > > > Cassandra Forward is in the past, so this addresses the fact by simply > replacing the banner and the "register now" CTA with an equivalent thing for > the December C* Summit. > The (very simple) PR is available for inspection here: > [https://github.com/apache/cassandra-website/pull/219] > See images: > !banner_on_index_page.png|width=300! > !banner_on_events_page.png|width=300! -- 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-18451) CEP-15: (C*) Improve the chaos generation for Burn Tests: slow/flakey connections and dropped messages
[ https://issues.apache.org/jira/browse/CASSANDRA-18451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-18451: --- Labels: pull-request-available (was: ) > CEP-15: (C*) Improve the chaos generation for Burn Tests: slow/flakey > connections and dropped messages > -- > > Key: CASSANDRA-18451 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18451 > Project: Cassandra > Issue Type: Improvement > Components: Accord >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Labels: pull-request-available > Fix For: NA > > > Burn test should be enhanced to add the following: > 1) message dropping from one node to another (this is different than the > current partition set logic in accord.impl.basic.Cluster#partitionSet) > 2) for messages with callbacks, trigger failure case > 3) redundant message delivery > Related work: > * Simulator’s > org.apache.cassandra.simulator.systems.SimulatedAction#applyToMessage > - Figures out what delivery action to perform via > org.apache.cassandra.simulator.FutureActionScheduler#shouldDeliver > -- timeout if dropPartition[from] != dropPartition[to] // either to/from is > in drop partition, but not both > -- config asked to override and deliver > -- 50/50 chance to deliver, after that 50/50 to deliver w/ timeout, after > that cause a failure > - in C* failure is an enum with Timeout and Unknown > - knows the schedule time and the message expire time, and can promote a > DELIVER event to DELIVER_AND_TIMEOUT > - triggers the timeout -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
