[05:45:58] RECOVERY - cassandra-a CQL 10.64.0.213:9042 on aqs1007 is OK: TCP OK - 0.000 second response time on 10.64.0.213 port 9042 [08:54:10] "21:08 ^^^ afaik, there must have been a previous acknowledgement on a clock, and that clock expired" [08:55:37] I was sure to have removed the downtime, surely I missed something.. I thought that the bootstrap was failed, but now that I think more about it (as you guys found out straight away) it is normal that the alarms went off, the instance is not really available [08:55:41] sigh [08:55:52] joal: really sorry to have pinged you late yesterday! [09:03:07] joal: aqs1007-a bootstrapped correctly and already joined the cluster! \o/ [09:06:38] all the metrics are fine, compactions completed [09:07:10] really nice [09:29:39] 10Quarry: Explain command forces Quarry to keep running endlessly - https://phabricator.wikimedia.org/T155808#2955224 (10Nemo_bis) I'm still able to run new queries, so at least this doesn't seem to be disruptive for other users. Or do we have reasons to believe it is? [09:50:19] 10Quarry: Explain command forces Quarry to keep running endlessly - https://phabricator.wikimedia.org/T155808#2955224 (10zhuyifei1999) AFAIK, queries are automatically killed after some time. [09:57:05] 10Quarry: Explain command forces Quarry to keep running endlessly - https://phabricator.wikimedia.org/T155808#2979170 (10Soni) About a dozen or more queries that happened just after this query are still marked as "Running". I believe there are others as well, some more queries that followed these. https://quar... [10:28:11] created https://gerrit.wikimedia.org/r/#/c/334753/1 to enable aqs1007-b, was tempted to do it now but I'll wait monday just in case :) [18:41:49] Hey, no prolblem elukey :) That's great all finally went well :)