| *** wanghao has joined #openstack-zaqar | 00:32 | |
| *** geong has joined #openstack-zaqar | 00:39 | |
| *** openstackgerrit has quit IRC | 00:41 | |
| *** wanghao has quit IRC | 00:44 | |
| *** openstackgerrit has joined #openstack-zaqar | 00:44 | |
| *** wanghao has joined #openstack-zaqar | 00:44 | |
| *** gecong has joined #openstack-zaqar | 01:27 | |
| *** shu-mutou-AWAY is now known as shu-mutou | 01:53 | |
| *** lhx__ has joined #openstack-zaqar | 02:04 | |
| *** wanghao has quit IRC | 02:13 | |
| *** wanghao has joined #openstack-zaqar | 02:41 | |
| *** geong has quit IRC | 02:46 | |
| yangzhenyu | flwang, hi，I have a question. | 03:35 |
|---|---|---|
| yangzhenyu | flwang, When the message is publish to subscriber, if all threads are blocked, the default is 10, which may cause the message to be issued to fail. Is that so? cc wanghao wxy | 03:36 |
| flwang | yangzhenyu: could be | 03:36 |
| flwang | that's the part we need to improve for sure | 03:37 |
| yangzhenyu | flwang, And cause the message to be lost | 03:37 |
| flwang | personally, I'd like to see an auto scale handler | 03:37 |
| flwang | I don't think the message will be lost | 03:37 |
| flwang | but I never done that kind of test before, so i'm not 100% sure | 03:40 |
| yangzhenyu | flwang, I added some retry mechanism when messages publish failed, that would cause the thread to block for some time. But I found when all threads were blocked, I publish the message again, the message is lost and it is not stored in the mongodb. | 03:46 |
| yangzhenyu | Do you have any good suggestions? Is it better to use rabbitmq for asynchronous processing? | 03:48 |
| flwang | yangzhenyu: that's the good catch | 03:48 |
| flwang | sorry? do you mean using rabbitmq in zaqar? | 03:49 |
| flwang | i'm a bit confused | 03:49 |
| flwang | do you mean you're using zaqar for some internal jobs/tasks and got current problem? | 03:49 |
| yangzhenyu | no, just use it for asynchronous processing rather than thread pool. | 03:52 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/zaqar master: Updated from global requirements https://review.openstack.org/494942 | 03:52 |
| openstackgerrit | OpenStack Proposal Bot proposed openstack/zaqar-ui master: Updated from global requirements https://review.openstack.org/502840 | 03:53 |
| flwang | yangzhenyu: i see. i mean at least you're using zaqar for some real jobs, not testing, right? | 03:55 |
| yangzhenyu | flwang, yes | 03:55 |
| flwang | yangzhenyu: i see. and you're using the notification service, but the default 10 threads can't meat your performance requirements? | 03:56 |
| yangzhenyu | flwang, provide a message services for users. | 03:56 |
| flwang | i see | 03:56 |
| yangzhenyu | yes | 03:57 |
| flwang | did you try to enlarge the default 10 to 50 or more? | 03:57 |
| flwang | or you're looking for an auto-scaling way? | 03:57 |
| yangzhenyu | yes, even if the increase of this value, there may still be problems. the notification is not queuing function, when all threads were blocked, the notification would be not work. | 04:00 |
| yangzhenyu | and notify to subscriber is failed. | 04:02 |
| yangzhenyu | also the messages is lost. | 04:04 |
| flwang | yep, i see. | 04:19 |
| flwang | we're using the pipeline of zaqar for notification | 04:19 |
| flwang | so if there is something wrong with the notification/pipeline stage, the message may be lost | 04:20 |
| flwang | or we shouldn't say "message lost", we should say the message is not posted successfully | 04:21 |
| flwang | I will double check the process | 04:21 |
| openstackgerrit | Merged openstack/zaqar-ui master: Updated from global requirements https://review.openstack.org/502840 | 04:23 |
| *** wanghao_ has joined #openstack-zaqar | 04:57 | |
| *** wanghao has quit IRC | 04:57 | |
| *** flwang1 has quit IRC | 05:03 | |
| *** pcaruana has joined #openstack-zaqar | 05:09 | |
| *** jtomasek has joined #openstack-zaqar | 05:29 | |
| *** lei-zh has joined #openstack-zaqar | 05:50 | |
| yangzhenyu | flwang, I tested it again and found that there was no problem. just a delay. It does not cause message loss. It was my fault. But restart the zaqar server can loss. | 05:51 |
| *** flwang1 has joined #openstack-zaqar | 06:17 | |
| *** rcernin has joined #openstack-zaqar | 06:28 | |
| openstackgerrit | Merged openstack/zaqar master: Updated from global requirements https://review.openstack.org/494942 | 06:28 |
| *** pcaruana has quit IRC | 07:05 | |
| *** ChanServ sets mode: +o openstack | 07:14 | |
| *** tesseract has joined #openstack-zaqar | 07:19 | |
| *** jtomasek has quit IRC | 07:23 | |
| *** pcaruana has joined #openstack-zaqar | 07:23 | |
| *** jtomasek has joined #openstack-zaqar | 07:25 | |
| *** wanghao has joined #openstack-zaqar | 07:54 | |
| *** wanghao_ has quit IRC | 07:58 | |
| *** gecong has quit IRC | 08:04 | |
| openstackgerrit | gecong proposed openstack/zaqar master: Add subscription confirm tempest https://review.openstack.org/343999 | 08:38 |
| *** wanghao has quit IRC | 08:58 | |
| *** wanghao has joined #openstack-zaqar | 08:59 | |
| openstackgerrit | gecong proposed openstack/zaqar master: Delete some duplicate code of mongodb/claims.py. https://review.openstack.org/504033 | 09:14 |
| *** tesseract has quit IRC | 09:41 | |
| *** tesseract has joined #openstack-zaqar | 09:41 | |
| *** lei-zh has quit IRC | 09:50 | |
| *** shu-mutou is now known as shu-mutou-AWAY | 10:01 | |
| *** lhx_ has joined #openstack-zaqar | 10:51 | |
| *** lhx__ has quit IRC | 10:52 | |
| *** aputtur has joined #openstack-zaqar | 12:07 | |
| *** openstackgerrit has quit IRC | 14:33 | |
| *** openstackgerrit has joined #openstack-zaqar | 15:07 | |
| openstackgerrit | zhangyangyang proposed openstack/python-zaqarclient master: Cleanup test-requirements https://review.openstack.org/506232 | 15:07 |
| *** jtomasek has quit IRC | 16:49 | |
| *** tesseract has quit IRC | 16:50 | |
| *** jtomasek has joined #openstack-zaqar | 16:50 | |
| *** rcernin has quit IRC | 16:52 | |
| -openstackstatus- NOTICE: Gerrit OpenIDs have been accidentally overwritten and are in the process of being restored | 18:18 | |
| -openstackstatus- NOTICE: The Gerrit service on review.openstack.org is being taken offline briefly to perform database repair work but should be back up shortly | 18:24 | |
| *** ChanServ changes topic to "The Gerrit service on review.openstack.org is being taken offline briefly to perform database repair work but should be back up shortly" | 18:24 | |
| *** aputtur has quit IRC | 19:16 | |
| *** ChanServ changes topic to "OpenStack Queuing and Notification Service || Smile :D || Meetings every Monday @ 21:00 UTC/15:00 UTC || Wiki: https://wiki.openstack.org/wiki/Zaqar || Paste: http://paste.openstack.org/ || Send messages and make some noise :D" | 19:22 | |
| -openstackstatus- NOTICE: OpenIDs for the Gerrit service have been restored from a recent backup and the service is running again; before/after table states are being analyzed now to identify any remaining cleanup needed for changes made to accounts today | 19:22 | |
| *** pcaruana has quit IRC | 19:41 | |
| *** lhx_ has quit IRC | 19:53 | |
| *** lhx__ has joined #openstack-zaqar | 19:53 | |
| *** wanghao_ has joined #openstack-zaqar | 20:01 | |
| *** wanghao has quit IRC | 20:03 | |
| *** flwang1 has quit IRC | 20:07 | |
| *** flwang1 has joined #openstack-zaqar | 21:32 | |
| *** vkmc has quit IRC | 21:47 | |
| *** vkmc has joined #openstack-zaqar | 21:53 | |
| *** vkmc has quit IRC | 21:53 | |
| *** vkmc has joined #openstack-zaqar | 21:53 | |
| *** flwang1 has quit IRC | 23:07 | |
| *** flwang1 has joined #openstack-zaqar | 23:25 | |
| *** flwang has quit IRC | 23:30 | |
| *** flwang has joined #openstack-zaqar | 23:43 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!