fesiqueira commented on issue #1736:
URL: 
https://github.com/apache/cassandra-gocql-driver/issues/1736#issuecomment-3397970918

   > Oh maybe you're looking for something like 
[this](https://github.com/apache/cassandra-java-driver/blob/e2c7ad4d11555eeacce6bd436547b403f83eb24f/core/src/main/java/com/datastax/oss/driver/internal/core/metadata/SchemaAgreementChecker.java#L192-L211).
 If gocql doesn't ignore DOWN nodes (along with other checks in that java 
driver method) then that is something we can add for sure
   
   @joao-r-reis I believe that's what I need (similar to what I added in 
#1738), and if it makes sense for gocql to have these checks I'd like to 
address any feedback on that PR and keep working on it.
   
   The node gocql keeps complaining about the schema version is down and it 
will never show up again as it was destroyed and replaced by a new instance.
   
   @dkropachev I tried both  `nodetool removenode` and `nodetool assassinate`.
   
   While `assassinate` removed the bad row from `system.peers` I would still 
like gocql to ignore it, as in the near future we will make some changes to our 
infrastructure and login in to the cluster would become more restricted.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to