Unanswered
Suddenly All Experiments We Try To Log Run Into An Error. I Think It'S A Server Thing At Our Side, Because As Far As I Know Nothing Changed About Trains (We Didn'T Update Or Anything) And Yesterday It Was Working Well.
Can Anyone Provide Some Insights At
SuccessfulKoala55 Thank you. I stared myself dead at trains-apiserver , but by coincidence I found this message:trains-elastic | {"type": "server", "timestamp": "2020-11-10T06:11:08,956Z", "level": "WARN", "component": "o.e.c.r.a.DiskThresholdMonitor", "cluster.name": "trains", "node.name": "trains", "message": "flood stage disk watermark [95%] exceeded on [QyZ2i1mxTG6yR7uhVWjV9Q][trains][/usr/share/elasticsearch/data/nodes/0] free: 43.3gb[4.7%], all indices on this node will be marked read-only", "cluster.uuid": "sDf_05oOQmm5euASjIp3Fw", "node.id": "QyZ2i1mxTG6yR7uhVWjV9Q" }So I was about to post that it's likely due to our disk getting full.
Thank you for your insights!
136 Views
0
Answers
3 years ago
one year ago