Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Cassandra: route coordinators to the configured datacenter

Abierto
#594 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 4 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
rust

Línea de trabajo

Read crates/storage-cassandra/src/engine.rs and the session builder in crates/storage-cassandra/src/lib.rs, then check how datacenter is exposed in crates/storage-cassandra/src/config.rs. The issue points to cdrs-tokio 9.0.2's topology-aware load balancing and node distance evaluator; verify their API and how they use the configured datacenter. Done means coordinators route to that datacenter and the described local consistency operations no longer fail when remote peers are discovered.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

backend:cassandra

Summary

The Cassandra backend creates every keyspace with NetworkTopologyStrategy in the one datacenter named by datacenter, and since #591 (the fix for #560) runs every data-path statement at LOCAL_QUORUM or LOCAL_ONE. The session uses RoundRobinLoadBalancingStrategy with the driver's default node distance evaluator, which treats every node the driver discovers from system.peers_v2 as local. A coordinator in a datacenter that holds no replica of the keyspace evaluates LOCAL_QUORUM and LOCAL_ONE against its own datacenter, finds no replica, and answers unavailable; the driver retries once on the next node and then fails the request.

Expected

Statements are coordinated by nodes in datacenter. cdrs-tokio 9.0.2 has TopologyAwareLoadBalancingStrategy and TopologyAwareNodeDistanceEvaluator::new(local_dc), which route to the local datacenter and treat remote nodes as remote.

Today

The datacenter field doc, the differences table, the high availability design and the upgrade manual tell the operator to run ExtendDB against contact points whose peers are all in datacenter. Before #591 the LOCAL_QUORUM batches, the query_lwt paths and the quorum reads already failed from such a coordinator; the reads, the OCC lightweight transactions and the plain delete succeeded at ONE.

Where

  • crates/storage-cassandra/src/engine.rs (RoundRobinLoadBalancingStrategy::new())
  • crates/storage-cassandra/src/lib.rs (the session builder)
  • crates/storage-cassandra/src/config.rs (datacenter)
Lenguaje dominante
Rust
Estrellas
517
Forks
60
Merge medio
4 d 22 h
PR fusionados (30 d)
40

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ExtendDB/extenddb

Todos los issues de ExtendDB/extenddb

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.