Sorry for this inconvenience. There are each reasons for these mudfish nodes:
- HK Asia (Hong Kong - Azure 14)
This mudfish node is now suspended by MS without any notification. They (microsoft) say that it’s due to suspicious activities with mudfish account but didn’t say us a clear clarification.
- SG Asia (Singapore - Amazon EC2)
For this case, it’s caused by disk failure of AWS host node. Due to unknown reason, it begins to consume 100% disk I/Os while node was UP. So I should make it down .
However at this moment I’d added multiple new HK Asia (Hong Kong - Azure XX) nodes so I think you can test. However for SG Asia (Singapore - Amazon EC2) node, I need to create one.