-
Notifications
You must be signed in to change notification settings - Fork 367
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rapns Worker stalls and not setting notifications as delivered #9
Comments
Comment by ileitch from Wednesday Nov 20, 2013 at 10:42 GMT Not much detail for me to work with here. Do you see an SQL activity in the log? Does sending USR2 signal print any debug info to the log? |
Comment by navied from Wednesday Nov 20, 2013 at 20:30 GMT Yeah sorry about, I actually looked at SQL logs around the same time the The problems started when I did a global notification to all our users I will perform a USR2 signal when the problem pops up again to see if On Wednesday, November 20, 2013, Ian Leitch wrote:
Navied Shoushtarian |
Comment by ileitch from Thursday Nov 21, 2013 at 10:13 GMT How long after creating the notifications did you then check the log? I wonder if the batch size is too large. The default is to load 5000 notifications at a time, combined with the error detection option Try setting |
Comment by navied from Monday Nov 25, 2013 at 04:38 GMT It has been behaving properly so far, I am not too sure why, could be less notifications being delivered or possibly because I enabled config.batch_storage_updates = true , but that could of always been true as a default. What are the downsides to turning off check_for_errors would that effect feedback and disabling devices that do not have the app installed anymore? |
Comment by j-mcnally from Thursday Nov 28, 2013 at 00:38 GMT Is it possible if you are using MyISAM instead of INNODB tables that you are running into locks? |
Comment by navied from Thursday Nov 28, 2013 at 00:50 GMT Using PostgreSQL, which correct me if I am wrong uses neither but it's own storage engine. |
Comment by j-mcnally from Thursday Nov 28, 2013 at 00:51 GMT yeah, durr just throwing that out there. |
Comment by navied from Monday Dec 23, 2013 at 20:25 GMT So the rapns process did this again after not doing it for a while, I tried sending a USR2 signal doing "kill -USR2 pid" but nothing has been returned in the logs. I might be doing the USR2 signal wrong. I just ended up lowering the rapns batch size and turned off error checking to see if how that affects it now. |
Please try |
Issue by navied from Tuesday Nov 19, 2013 at 00:27 GMT
Originally opened as ileitch/rapns#179
I am having an issue with the rapns worker lately, It seems to suddenly stop working randomly and needs to be restarted, but what is worse is that the notifications that are sent after restarting the rapns worker is not being set as delivered and need to manually be set or the next time the worker is restarted it will resend them all again.
The text was updated successfully, but these errors were encountered: