Right... so what happened...

[Jamie]

Downtime wasn't me this time lol

The root of the problem is a new NVMe based storage architecture that our data infrastructure utilizes which is/was supposed to be a significant upgrade from the previous SSD based storage cluster we had previously, however with these two instances that does not seem to be the case.

Once it's back online we will be seriously evaluating this cluster and the company providing the software for this cluster if they are to remain in the KH network.

 

[HaarlemShuffler]

Downtime wasn't me this time lol

I wouldae guessed like

 

[hibbybilly]

Downtime wasn't me this time lol

Just put it down tae you fuckin aboot Jamie
Nae biggie

 

[Jamie]

CU*TS

 

[Jack]

Mice ate through the cable.

 

[Jamie]

Mice ate through the cable.

Nae they go for fresh water plastic pipes. Repaired a few o those in my time

 

[GORDONSMITH7]

The root of the problem is a new NVMe based storage architecture that our data infrastructure utilizes which is/was supposed to be a significant upgrade from the previous SSD based storage cluster we had previously, however with these two instances that does not seem to be the case.

Once it's back online we will be seriously evaluating this cluster and the company providing the software for this cluster if they are to remain in the KH network.





BIG G

 

[EH17 Jimmy]

The root of the problem is a new NVMe based storage architecture that our data infrastructure utilizes which is/was supposed to be a significant upgrade from the previous SSD based storage cluster we had previously, however with these two instances that does not seem to be the case.

Once it's back online we will be seriously evaluating this cluster and the company providing the software for this cluster if they are to remain in the KH network.

View attachment 9068



BIG G

That's what I thought as well.

 

[HaarlemShuffler]

Sounds like a clusterfúck to me!