Critical issue since moving to HTTP v1 from Legacy Firebase
-
Hi Murali,
We’ve come across a critical issue since moving to HTTP v1 from Legacy Firebase.
We use PNFPB REST API to send mobile app (not web app) notifications for BuddyPress private messages. Since updating to HTTP v1 we noticed that:
Messaging became unreliable.
- E.g. David would attempt to message Ana, but the request would timeout. To David, it would appear that the message had never been sent. However, Ana actually received the message multiple times. In our Android app, the message would be received twice. In the iOS version, the message would continue to be received repeatedly until the app was shut down.
- This issue seemed to only occur for specific users (i.e. it was not impacting every user). This made it harder for us to test/isolate the problem, and was concerning as we didn’t know how widespread the issue was.
- In Postman, we could see that the server executed the send request very quickly, but was very slow to reply back to Postman that the message had been sent, causing it to timeout.
Our server CPU usage was significantly higher than it usually would be (e.g. 80%, when it normally sits between 5-10%).
- E.g. four or five users being online would cause significant CPU spikes, which we had not encountered previously.
- This caused our servers to become very slow in responding, with timeouts for some users, as above.
- Our server has more than enough capacity to handle a much higher number of active users, and regularly does so.
These issues were resolved immediately once we moved back to Legacy Firebase, when using version 1.89 of PNFPB; or by rolling the plugin back to version 1.69, where we’re able to continue using HTTP v1 Firebase. We rolled it back to 1.69 as we knew this version had worked for us previously. We haven’t tested other versions to know when this issue started.
Given Legacy Firebase is being retired on the 21st of June, could these issues be looked into as soon as possible?
Thanks.
- The topic ‘Critical issue since moving to HTTP v1 from Legacy Firebase’ is closed to new replies.