yifan-c commented on PR #93: URL: https://github.com/apache/cassandra-analytics/pull/93#issuecomment-3100005898
@liucao-dd, I will need more help on understanding the issue. Btw, thanks for sharing the example. In the instances list shared, the vnode that owns token `-9095340097586658697` is the replication target for the vnodes `8821921454609098249` and `8957072497331100633`. Therefore, it owns the token ranges `(8665320250315620066, MAX]` and `(MIN, -9095340097586658697`. Here is a special case where the range wraps-around, so I de-wrapped the range into 2 ranges. And... it seems correct to me. If allowed, can you share more about the issue you see in production? Maybe there is a different cause. When using vnode, the tokens are randomly assigned. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
