Support Topics Documentation Slack YouTube Blog

Crash regarding db tables

(Rajasekhar Puligadda) #1

Showing issue as below

Backendless encountered an error while handling the request. An internal trouble ticket with ID 5CC185BE-5D37-BCF3-FF88-4BBE89CE1100 has been created and we will be investigating the issue.

(Rajasekhar Puligadda) #2

What happened, still there is no reply?

(Vladimir Upirov) #3

Hello, please provide your appId

(Rajasekhar Puligadda) #4

app id is FB4CB018-6F5D-7274-FF56-46A6BFAE8300

(Vladimir Upirov) #5

could you check your data please

(Mark Piller) #6

@rajasekhar_puligadda, could you please confirm if you can see all your data now?

(Rajasekhar Puligadda) #7

Now data is getting, but why it happened and if the backendless project in live in that case it will be problematic, some times as i observed that the data coming from backendless is getting slow

(Mark Piller) #8

We had an incident where the database cluster experienced an outage and went into the recovery mode. Due to the size of the database it took about 10 hours for it to run all the checksum checks. While the database cluster was running in the recovery mode we made a decision to switch the service to point to an older dataset. This resulted in what appeared that some data was lost and tables disappeared. On February 5th we have restored majority of the apps, including yours. The new environment is an updated database cluster which has much higher reliability and fault tolerance criteria. We have been running speed tests and the round trip times have actually improved.