You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Bianca Stanciu (Jira)" <ji...@apache.org> on 2026/07/13 13:43:00 UTC

[jira] [Updated] (CASSANALYTICS-181) Support Sidecar behind a load balancer for time-skew validation in coordinated writes

     [ https://issues.apache.org/jira/browse/CASSANALYTICS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bianca Stanciu updated CASSANALYTICS-181:
-----------------------------------------
    Priority: High  (was: Normal)

> Support Sidecar behind a load balancer for time-skew validation in coordinated writes
> -------------------------------------------------------------------------------------
>
>                 Key: CASSANALYTICS-181
>                 URL: https://issues.apache.org/jira/browse/CASSANALYTICS-181
>             Project: Apache Cassandra Analytics
>          Issue Type: Improvement
>          Components: Writer
>            Reporter: Bianca Stanciu
>            Assignee: Bianca Stanciu
>            Priority: High
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
>   ## Problem                                                                                                            
>                   
>   Time-skew validation before a coordinated bulk write fans out HTTP calls directly to per-replica FQDNs resolved from the Cassandra token map. In deployments where Sidecar is fronted by a *load balancer,* those FQDNs are *not* routable from Spark executors, only the load balancer address is. This causes  time-skew validation to fail at the start of every coordinated write job,  blocking bulk writes entirely in load-balanced Sidecar deployments.                                                                 
>   ## Solution                                                                                                           
>                   
>   Add a _*SIDECAR_BEHIND_LOAD_BALANCER*_ writer option (default: false). When true, time-skew validation skips the per-replica fan-out and routes through the preconfigured load balancer contact points instead:                                                                                             
> {code:java}
>     sidecarClient.timeSkew()  // routes through LB, no per-replica list{code}
>                                                                                                                         
>   Implemented via a *new CoordinatedCassandraClusterInfo* subclass that overrides only the time-skew fetch step, leaving all other behavior unchanged.
>                                                                                                                         
>   ## Acceptance Criteria
>                                                                                                                         
>   - [ ] Flag has no effect on single-cluster writes (warning logged if misconfigured)                
>   - [ ] Default behavior (flag=false) is unchanged
>   - [ ] Unit test verifies timeSkew(List) is never called when flag is enabled                               
>   - [ ] CHANGES.txt entry added under 0.5.0   



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org