| *** charlesw has joined #magnetodb | 01:28 | |
| *** achanda has quit IRC | 04:32 | |
| *** achanda has joined #magnetodb | 04:34 | |
| *** achanda has quit IRC | 04:53 | |
| *** achanda has joined #magnetodb | 04:55 | |
| *** achanda has quit IRC | 05:09 | |
| *** achanda has joined #magnetodb | 05:10 | |
| *** achanda has quit IRC | 05:29 | |
| *** achanda has joined #magnetodb | 05:37 | |
| *** charlesw has quit IRC | 05:37 | |
| *** achanda has quit IRC | 05:44 | |
| *** achanda has joined #magnetodb | 06:01 | |
| *** achanda has quit IRC | 06:25 | |
| *** achanda has joined #magnetodb | 06:26 | |
| *** achanda has quit IRC | 06:42 | |
| *** vivekd has joined #magnetodb | 07:12 | |
| *** achanda has joined #magnetodb | 07:24 | |
| *** achanda has quit IRC | 08:17 | |
| *** achanda has joined #magnetodb | 08:19 | |
| *** vivekd_ has joined #magnetodb | 08:24 | |
| *** vivekd has quit IRC | 08:25 | |
| *** vivekd_ is now known as vivekd | 08:25 | |
| *** achanda has quit IRC | 08:33 | |
| *** vivekd_ has joined #magnetodb | 08:51 | |
| *** vivekd has quit IRC | 08:52 | |
| *** vivekd_ is now known as vivekd | 08:52 | |
| *** romainh has joined #magnetodb | 08:53 | |
| *** ygbo has joined #magnetodb | 08:54 | |
| *** achanda has joined #magnetodb | 08:54 | |
| *** ygbo has quit IRC | 09:11 | |
| *** ygbo has joined #magnetodb | 09:14 | |
| *** achanda has quit IRC | 09:19 | |
| *** vivekd has quit IRC | 09:56 | |
| *** vivekd has joined #magnetodb | 09:58 | |
| *** rushiagr_away is now known as rushiagr | 10:10 | |
| *** vivekd_ has joined #magnetodb | 10:19 | |
| *** vivekd has quit IRC | 10:20 | |
| *** vivekd_ is now known as vivekd | 10:20 | |
| *** vivekd has quit IRC | 10:21 | |
| *** vivekd has joined #magnetodb | 10:22 | |
| *** romainh has left #magnetodb | 11:10 | |
| *** denis_makogon has joined #magnetodb | 11:32 | |
| *** vivekd_ has joined #magnetodb | 11:34 | |
| *** vivekd has quit IRC | 11:35 | |
| *** vivekd_ is now known as vivekd | 11:35 | |
| *** vivekd_ has joined #magnetodb | 11:58 | |
| *** vivekd has quit IRC | 12:00 | |
| *** vivekd_ is now known as vivekd | 12:00 | |
| isviridov | aostapenko around to discuss https://blueprints.launchpad.net/magnetodb/+spec/test-concurrent-writes? | 12:01 |
|---|---|---|
| aostapenko | isviridov: yep | 12:03 |
| isviridov | Just checked scenario you have suggested | 12:04 |
| isviridov | I looks like the second write will overwrite the first item | 12:05 |
| isviridov | What do you think? | 12:05 |
| aostapenko | isviridov: Thank you. I've made a mistake. Not put, but update request | 12:08 |
| isviridov | Ok. So we are putting on item and updating it with adding new attributes | 12:09 |
| isviridov | Using conditions? | 12:09 |
| aostapenko | We can just send 2 update requests | 12:10 |
| aostapenko | or send put one first. but it seems redundant. However this can be an extra scenario | 12:10 |
| aostapenko | Yes. Using conditions | 12:11 |
| isviridov | Such a test gonna be probalistic, I think with 2 calls we have not a big chance to prove anything | 12:11 |
| isviridov | I would rather recomment to start with some ammount 50-100. First to get the some kind of timeout state and use this value as a base for testing. | 12:13 |
| aostapenko | They will prove in case of success | 12:13 |
| aostapenko | One request will check if an extra item in another request do not exist | 12:14 |
| isviridov | aostapenko depends on you luck :) | 12:14 |
| aostapenko | however it will not prove if one such pair fails | 12:14 |
| aostapenko | so we need to check if update request fails | 12:15 |
| aostapenko | and try till success | 12:15 |
| isviridov | got you now | 12:41 |
| isviridov | aostapenko please describe it in bp as well as my one. I belieave it will be the most failing part first time | 12:42 |
| openstackgerrit | Illia Khudoshyn proposed stackforge/magnetodb: Add restore manager https://review.openstack.org/146909 | 12:45 |
| openstackgerrit | Illia Khudoshyn proposed stackforge/magnetodb: (WIP) Add simple backup implementation https://review.openstack.org/148963 | 12:46 |
| *** romainh has joined #magnetodb | 12:51 | |
| *** romainh has left #magnetodb | 12:52 | |
| aostapenko | https://blueprints.launchpad.net/magnetodb/+spec/test-concurrent-writes | 12:56 |
| aostapenko | isviridov: described another scenario | 12:57 |
| isviridov | I'm ok with it. Setting as approved | 12:59 |
| isviridov | aostapenko have you had a chance to look at notification refactoring? | 12:59 |
| isviridov | aostapenko I mean https://docs.google.com/a/mirantis.com/spreadsheets/d/1f0pxpA6R8zqyOpmekQmwd9ZDkYMLAGeDqUNfRs35tx8/edit#gid=0 | 12:59 |
| isviridov | BTW, not sure that it is intergaton test. Just updated the title | 13:01 |
| aostapenko | isviridov: thank you | 13:10 |
| *** vivekd has quit IRC | 13:10 | |
| *** miqui has joined #magnetodb | 13:50 | |
| openstackgerrit | Illia Khudoshyn proposed stackforge/magnetodb: Add restore manager https://review.openstack.org/146909 | 13:51 |
| *** charlesw has joined #magnetodb | 14:42 | |
| *** achanda has joined #magnetodb | 15:35 | |
| *** achanda has quit IRC | 15:42 | |
| *** achanda has joined #magnetodb | 16:03 | |
| *** achanda has quit IRC | 16:06 | |
| *** denis_makogon has quit IRC | 16:21 | |
| *** ygbo has quit IRC | 17:37 | |
| *** achanda has joined #magnetodb | 18:15 | |
| *** rushiagr is now known as rushiagr_away | 18:57 | |
| *** achanda has quit IRC | 19:42 | |
| *** achanda has joined #magnetodb | 20:42 | |
| *** achanda has quit IRC | 20:43 | |
| *** achanda has joined #magnetodb | 20:43 | |
| *** charlesw has quit IRC | 20:56 | |
| *** miqui has quit IRC | 21:38 | |
| *** charlesw has joined #magnetodb | 22:28 | |
| *** charlesw has quit IRC | 23:41 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!