Timeouts using Push Notification feature

Question

Timeouts using Push Notification feature

kangaroosterussave opened this issue 8 years ago · 7 comments

kangaroosterussave commented 8 years ago

Calling the Pusher notify method often (but not always) results in a timeout.

For example doing something like:

pusher = Pusher(app_id=app_id,
key=key,
secret=secret,
timeout=1,
retry=5, # THE DEFAULT
ssl=False)

pusher.notify([channel], notification)

Results in:

requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='nativepush-cluster1.pusher.com', > port=443): Read timed out. (read timeout=1)

Any ideas?

Answer 1 · 2017-04-24T02:25:17.000Z

Also, when I set the timeout to a large enough number (ie. timeout=60),
I'm getting HTTP Service Unavailable status code:

pusher.errors.PusherBadStatus: 503:

Answer 2 · 2017-04-24T08:34:06.000Z

@kangaroosterus Hi there!

We're investigating availability issues with the Push Notification API. A fix is currently being developed and should hopefully resolve these issues soon.

Apologies for any inconvenience.

Answer 3 · 2017-05-17T10:35:29.000Z

@kangaroosterus Are you still seeing these timeouts? We've made some changes to the backend which should hopefully have improved the situation.

Answer 4 · 2017-07-18T14:20:52.000Z

I am seeing timeout exceptions like this:

requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='nativepush-cluster1.pusher.com', port=443): Read timed out. (read timeout=5)

Answer 5 · 2017-07-18T15:37:01.000Z

Hi @tySwift93, we were experiencing some issues earlier today that could have caused this – though they should be resolved now. Are you still seeing the timeouts?

Answer 6 · 2017-07-18T16:55:26.000Z

Not anymore, thank you

Answer 7 · 2018-07-16T16:57:56.000Z

Closing because it appears this issue was resolved, and we are deprecating Push Notifications support in this library anyway.