| *** jeromatron has quit IRC | 00:37 | |
| *** charlesw has joined #magnetodb | 00:40 | |
| *** charlesw has quit IRC | 00:52 | |
| *** bogeyon18 has quit IRC | 02:09 | |
| *** openstackgerrit has quit IRC | 02:33 | |
| *** openstack has joined #magnetodb | 03:42 | |
| *** sendak.freenode.net sets mode: +ns | 03:42 | |
| *** sendak.freenode.net sets mode: -o openstack | 03:46 | |
| -sendak.freenode.net- *** Notice -- TS for #magnetodb changed from 1410234156 to 1385052681 | 03:46 | |
| *** sendak.freenode.net sets mode: +ct-s | 03:46 | |
| *** achuprin has joined #magnetodb | 03:46 | |
| *** idegtiarov has joined #magnetodb | 03:46 | |
| *** boris-42 has joined #magnetodb | 03:46 | |
| *** ikhudoshyn_ has joined #magnetodb | 03:46 | |
| *** aostapenko has joined #magnetodb | 03:46 | |
| *** igormarnat has joined #magnetodb | 03:46 | |
| *** rushiagr_away has joined #magnetodb | 03:46 | |
| *** ominakov has joined #magnetodb | 03:46 | |
| *** dukhlov has joined #magnetodb | 03:46 | |
| *** isviridov_away has joined #magnetodb | 03:46 | |
| *** [o__o] has joined #magnetodb | 03:46 | |
| *** anteaya has joined #magnetodb | 03:46 | |
| *** achudnovets has joined #magnetodb | 03:46 | |
| *** ChanServ has joined #magnetodb | 03:46 | |
| *** sendak.freenode.net sets mode: +o ChanServ | 03:46 | |
| *** sendak.freenode.net changes topic to "MagnetoDB - key-value database service for OpenStack (https://wiki.openstack.org/wiki/MagnetoDB, logs @ https://botbot.me/freenode/magnetodb/ and http://eavesdrop.openstack.org/irclogs/%23magnetodb/) | More info in our screencast http://goo.gl/21HRCf" | 03:46 | |
| *** rushiagr_away is now known as rushiagr | 04:29 | |
| rushiagr | hi folks, think it's time to update magnetodb wiki | 04:43 |
|---|---|---|
| rushiagr | https://wiki.openstack.org/wiki/MagnetoDB | 04:43 |
| rushiagr | seems outdated | 04:43 |
| *** jeromatron has joined #magnetodb | 05:06 | |
| *** rushiagr is now known as rushiagr_away | 05:07 | |
| *** jeromatron has quit IRC | 05:08 | |
| *** rushiagr_away is now known as rushiagr | 05:21 | |
| *** jeromatron has joined #magnetodb | 05:33 | |
| *** jeromatron has quit IRC | 05:49 | |
| *** jeromatron has joined #magnetodb | 06:05 | |
| *** jeromatron has quit IRC | 06:05 | |
| *** ajayaa has joined #magnetodb | 06:18 | |
| *** isviridov_away is now known as isviridov | 07:41 | |
| isviridov | rushiagr, yeap, it is really really outdated. Now we have documentation at RTD magnetodb.readthedocs.org and openstack wiki will be used only for community process support. | 07:43 |
| isviridov | rushiagr, planned to start working on it this week | 07:43 |
| rushiagr | isviridov: okay. Thanks :) | 07:44 |
| isviridov | rushiagr, have you managed to start C* cluster behind the proxy? | 07:45 |
| rushiagr | isviridov: nope. I've given up on that | 07:58 |
| rushiagr | isviridov: I'm in the process of setting it up locally on my laptop (which isnt behind proxy) | 07:59 |
| rushiagr | isviridov: any idea on the minimum requirements of RAM for the devstack+mdb VM? | 07:59 |
| rushiagr | RAM is at a premium on my laptop, so I'd like to use as little as possible :) | 08:00 |
| rushiagr | I'm currently trying with 3.6G | 08:38 |
| ajayaa | Hi isviridov, | 09:01 |
| ajayaa | Hi dukhlov, | 09:05 |
| ajayaa | I was recently going through https://blueprints.launchpad.net/magnetodb/+spec/monitoring-api | 09:06 |
| ajayaa | It is unclear on what is the scope of the blueprint and what all is going to be added. | 09:10 |
| ajayaa | Could we have something like a github repo for specs. somthing similar to https://github.com/openstack/keystone-specs | 09:11 |
| *** openstackgerrit has joined #magnetodb | 09:21 | |
| *** rushiagr is now known as rushiagr_away | 09:21 | |
| *** rushiagr_away is now known as rushiagr | 09:34 | |
| isviridov | Hello ajayaa. Good point. Let me describe a bit | 10:13 |
| isviridov | ajayaa, you are right, most of BP contains no information about implementation details. It is because we have a great communication within mdb team. | 10:15 |
| isviridov | ajayaa, now we have contributors and we must make our processes working for everybody | 10:16 |
| ajayaa | isviridov, makes sense! | 10:16 |
| ajayaa | :) | 10:16 |
| isviridov | ajayaa, not sure that we need such heavy process with formal approvement of specification, at least until we really need it. But I think that we MUST write a wiki page per every new feature or big change we are adding. | 10:17 |
| isviridov | ajayaa, f.e. https://wiki.openstack.org/wiki/MagnetoDB/api or https://wiki.openstack.org/wiki/MagnetoDB/streamingbulkload | 10:18 |
| isviridov | ajayaa, let me create the wiki for monitoring api and write down all thoughts about it. | 10:19 |
| isviridov | ajayaa, ominakov will update it | 10:19 |
| isviridov | ajayaa, if you have any questions right now, feel free to ask. | 10:19 |
| ajayaa | isviridov, In the monitoring api, Do we really want count of number of rows in a table? | 10:22 |
| ajayaa | It is very expensive, as it will scan all the rows in a table. | 10:22 |
| ajayaa | isviridov, Also creating a wiki for a blueprint makes sense. Thanks! :) | 10:23 |
| ajayaa | isviridov, I think with this kind of queries coming from multiple sources, could easily overwhelm cassandra. | 10:25 |
| isviridov | We have to provide the information about usage statistics - size of table in bytes, number of items, size of indexes in bytes so on. Another thing, such information should be available not only for tenant, but for external monitoring tool on system level. | 10:25 |
| isviridov | That is why we need this API | 10:25 |
| isviridov | You are talking about implementation, and here you are right. Query such a data too often can impact UX. But first API goes, next prototyping of working functionality, next caching the data so on. | 10:26 |
| isviridov | ajayaa, we are now on the first stage. Do you have any ideas how to make it better already? | 10:27 |
| ajayaa | okay. | 10:28 |
| ajayaa | isviridov, There are ways in cassandra in which you can get an approximate estimate of rows. | 10:28 |
| ajayaa | But that really depends on your usage. | 10:29 |
| ajayaa | It could off by several factors if you have a lot of overwrite. | 10:29 |
| isviridov | What do you mean? Approximate data can be good enough. | 10:30 |
| ajayaa | http://planetcassandra.org/blog/counting-key-in-cassandra/ | 10:30 |
| isviridov | ajayaa, I see. You know we are really close to using C* JMX for getting size of tables. Shouldn't be a problem to use it for count of items as well. I like it. But must be discussed with ominakov | 10:37 |
| *** isviridov is now known as isviridov_away | 10:59 | |
| aostapenko | Hello everybody. review this patches please https://review.openstack.org/119462 https://review.openstack.org/115314 | 11:14 |
| isviridov_away | ajayaa, here it is https://wiki.openstack.org/wiki/MagnetoDB/specs/monitoring-api | 11:25 |
| isviridov_away | The whole list https://wiki.openstack.org/wiki/MagnetoDB/specs/ | 11:25 |
| ajayaa | thanks isviridov_away. | 11:28 |
| *** isviridov_away is now known as isviridov | 11:29 | |
| openstackgerrit | A change was merged to stackforge/magnetodb: Fixes bug with put item predefined attributes https://review.openstack.org/119462 | 12:48 |
| openstackgerrit | A change was merged to stackforge/magnetodb: Adds mechanism for request time measuring https://review.openstack.org/115314 | 12:57 |
| isviridov | ominakov, around? | 13:22 |
| ominakov | isviridov, yep | 13:30 |
| ominakov | hi guys | 13:30 |
| isviridov | Hello ominakov. Really wanted to talk with you. | 13:31 |
| isviridov | I've started drafting spec about monitoring API. Here it is https://wiki.openstack.org/wiki/MagnetoDB/specs/monitoring-api | 13:32 |
| isviridov | Please add there implementation details so on. We have to be more open. | 13:32 |
| isviridov | Have to managed to talk with C* guys? | 13:33 |
| *** charlesw has joined #magnetodb | 13:35 | |
| *** bogeyon18 has joined #magnetodb | 13:35 | |
| ominakov | isviridov, ok, i'll add details and no i didn't have talk with C* guys yet | 13:41 |
| ominakov | isviridov, jeromatron wrote only: "just checking with the opscenter guys now. it sounds like that's what they do. just get the jmx estimate and add it up through the cluster." | 13:41 |
| ominakov | today i'll try manage more details conversation | 13:42 |
| openstackgerrit | Dmitriy Ukhlov proposed a change to stackforge/magnetodb: Adapt cassandra tox tests to the latest code https://review.openstack.org/120094 | 13:46 |
| openstackgerrit | Aleksey Chuprin proposed a change to stackforge/magnetodb: (WIP) Investigation problem with tox job timeout https://review.openstack.org/119467 | 13:55 |
| *** ajayaa has quit IRC | 14:09 | |
| openstackgerrit | A change was merged to stackforge/magnetodb: Heap memory parameters are configurable now https://review.openstack.org/119458 | 14:11 |
| aostapenko | https://bugs.launchpad.net/magnetodb/+bug/1367303 | 14:14 |
| *** jeromatron has joined #magnetodb | 14:29 | |
| *** bogeyon18 has quit IRC | 14:48 | |
| *** bogeyon18 has joined #magnetodb | 15:05 | |
| *** bogeyon18 has quit IRC | 15:13 | |
| ominakov | jeromatron, hello. If i right understand there are two ways to know count of rows in CF: 1) for rough estimate we can use JMX; 2) for exact value we should use COUNT(*) through all our data (it's very expensive operation). Right? | 15:18 |
| *** bogeyon18 has joined #magnetodb | 15:23 | |
| jeromatron | oh for number of rows, select count is very expensive, yes. it will have to do a scan of all the data | 15:26 |
| *** jeromatron has quit IRC | 15:39 | |
| openstackgerrit | A change was merged to stackforge/magnetodb: Adapt cassandra tox tests to the latest code https://review.openstack.org/120094 | 15:39 |
| *** bogeyon18 has quit IRC | 16:06 | |
| *** jeromatron has joined #magnetodb | 16:27 | |
| *** rushiagr is now known as rushiagr_away | 16:49 | |
| *** bogeyon18 has joined #magnetodb | 17:14 | |
| *** rushiagr_away is now known as rushiagr | 17:14 | |
| *** rushiagr is now known as rushiagr_away | 17:20 | |
| *** rushiagr_away is now known as rushiagr | 17:21 | |
| *** isviridov is now known as isviridov_away | 17:22 | |
| *** rushiagr is now known as rushiagr_away | 17:23 | |
| *** bogeyon18 has quit IRC | 17:29 | |
| *** bogeyon18 has joined #magnetodb | 17:39 | |
| *** jeromatron has quit IRC | 18:23 | |
| *** jeromatron has joined #magnetodb | 18:31 | |
| *** bogeyon18 has quit IRC | 18:35 | |
| *** bogeyon18 has joined #magnetodb | 18:35 | |
| *** bogeyon18 has quit IRC | 18:58 | |
| *** openstackgerrit has quit IRC | 19:02 | |
| *** bogeyon18 has joined #magnetodb | 19:03 | |
| *** bogeyon18 has quit IRC | 19:35 | |
| *** bogeyon18 has joined #magnetodb | 19:40 | |
| *** openstackgerrit has joined #magnetodb | 19:42 | |
| *** bogeyon18 has quit IRC | 20:36 | |
| *** jeromatron has quit IRC | 21:54 | |
| *** jeromatron has joined #magnetodb | 21:56 | |
| *** charlesw has quit IRC | 21:59 | |
| *** jeromatron has quit IRC | 23:03 | |
| *** charlesw has joined #magnetodb | 23:15 | |
| *** jeromatron has joined #magnetodb | 23:28 | |
| *** charlesw has quit IRC | 23:30 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!