[ 
https://issues.apache.org/jira/browse/CASSANDRA-15633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17057189#comment-17057189
 ] 

Chirantan commented on CASSANDRA-15633:
---------------------------------------

sorry for type issue is with repair 

when i try to bring up node it came up 

but nodetool command is not working  that node 

getting below message 

nodetool: Failed to connect to '127.0.0.1:7199' - FailedLoginException: 'Cannot 
login as server authentication setup is not yet completed'.

for other node its showing as down asd in describe cluster that node is showing 
as unavailable 

and for other node 

> Cassandra rebuild failing 
> --------------------------
>
>                 Key: CASSANDRA-15633
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15633
>             Project: Cassandra
>          Issue Type: Task
>            Reporter: Chirantan
>            Priority: Normal
>
> [2020-03-10 18:09:51,533] Repair session 7be9f3c0-631e-11ea-8e47-ef25c77f7899 
> for range [(6301399909211397355,6302095577836606571], 
> (6301291625775958686,6301399909211397355], 
> (6302095577836606571,6313970392023331777], 
> (6297705134651154643,6301291625775958686]] finished (progress: 44%)
> Exception occurred during clean-up. 
> java.lang.reflect.UndeclaredThrowableException
> Cassandra has shutdown.
> error: [2020-03-10 18:09:56,868] JMX connection closed. You should check 
> server log for repair status of keyspace cortex(Subsequent keyspaces are not 
> going to be repaired).
> -- StackTrace --
> java.io.IOException: [2020-03-10 18:09:56,868] JMX connection closed. You 
> should check server log for repair status of keyspace cortex(Subsequent 
> keyspaces are not going to be repaired).
>  at 
> org.apache.cassandra.tools.RepairRunner.handleConnectionFailed(RepairRunner.java:98)
>  at 
> org.apache.cassandra.utils.progress.jmx.JMXNotificationProgressListener.handleNotification(JMXNotificationProgressListener.java:86)
>  at 
> javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:286)
>  at 
> javax.management.NotificationBroadcasterSupport$SendNotifJob.run(NotificationBroadcasterSupport.java:363)
>  at 
> javax.management.NotificationBroadcasterSupport$1.execute(NotificationBroadcasterSupport.java:348)
>  at 
> javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:259)
>  at 
> javax.management.remote.rmi.RMIConnector.sendNotification(RMIConnector.java:452)
>  at 
> javax.management.remote.rmi.RMIConnector.access$1200(RMIConnector.java:132)
>  at 
> javax.management.remote.rmi.RMIConnector$RMIClientCommunicatorAdmin.gotIOException(RMIConnector.java:1542)
>  at 
> javax.management.remote.rmi.RMIConnector$RMINotifClient.fetchNotifs(RMIConnector.java:1363)
>  at 
> com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.fetchOneNotif(ClientNotifForwarder.java:667)
>  at 
> com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.fetchNotifs(ClientNotifForwarder.java:619)
>  at 
> com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.doRun(ClientNotifForwarder.java:483)
>  at 
> com.sun.jmx.remote.internal.ClientNotifForwarder$NotifFetcher.run(ClientNotifForwarder.java:464)
>  at 
> com.sun.jmx.remote.internal.ClientNotifForwarder$LinearExecutor$1.run(ClientNotifForwarder.java:120)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to