Running an opentsdb cluster in AWS; it's been running fantastic for about 5 days now without incident, using hdfs as the storage medium for a 3-node hbase cluster, with opentsdb running on one of the nodes.
Just saw this below error in the logs for opentsdb and I'm unsure of where I should go from here to try to prevent this, or stop it from happening.
I noticed issue #170 also reports this problem, but I was unsure whether my cause is the same as the cause for 170.
Running an opentsdb cluster in AWS; it's been running fantastic for about 5 days now without incident, using hdfs as the storage medium for a 3-node hbase cluster, with opentsdb running on one of the nodes.
Just saw this below error in the logs for opentsdb and I'm unsure of where I should go from here to try to prevent this, or stop it from happening.
I noticed issue #170 also reports this problem, but I was unsure whether my cause is the same as the cause for 170.