The Cassandra nightmare continueā¦
My download routines (dumping about 450 history events every 5 days) failed again today.
Out of the 11 temperature sensors my routine should dump, I can only dump 2 āby handā from the IDE before getting the dreaded :
"java.lang.RuntimeException: java.util.concurrent.ExecutionException: com.datastax.driver.core.exceptions.ReadTimeoutException: Cassandra timeout during read query at consistency LOCAL_ONE (1 responses were required but only 0 replica responded) @ line 112"
or sometimes :
"java.lang.reflect.UndeclaredThrowableException @ line 112"
As explained before in the other Cassandra timeout during read query thread, this always happens during the history database access :
--------------------- abstract from āJJās Test2ā smartapp ---------------------
111 for (tempSens in temperatureSensors) {
112 def allEvents = tempSens.eventsBetween(startDate, endDate, [max:2000]).findAll{it.name == ātemperatureā}
--------------------- abstract from āJJās Test2ā smartapp ---------------------
This is especially irritating since this dump routine is critical for me : it is the only way I have found to overcome the limitation to 7 days of history imposed by SmartThings.
So now SmartThings, or somebody at SmartThings, makes my workaround ineffective.
Reminds me of some SF novel by Frank Herbert (Whipping Star) where a whole āBureau of Sabotageā was dedicated to prevent the administration of becoming too efficient and too complacent.
SmartThings should tone down its own āBureau of Sabotageā !
Anyway, any geek naming a mission critical service āCassandraā should have been preventively sacked for attempting to sabotage the future !