Monday, 2014-09-08

*** rushiagr_away is now known as rushiagr02:52
*** jeromatron has joined #magnetodb02:52
*** rushiagr is now known as rushiagr_away03:03
*** rushiagr_away is now known as rushiagr03:05
*** rushiagr is now known as rushiagr_away03:16
*** jeromatron has quit IRC03:21
*** rushiagr_away is now known as rushiagr04:11
*** ajayaa has joined #magnetodb05:18
rushiagrI'm having a tough time setting up magnetodb-devstack behind the proxy06:03
*** ajayaa has quit IRC06:11
*** ajayaa has joined #magnetodb06:38
*** ajayaa has quit IRC07:08
*** ajayaa has joined #magnetodb07:21
*** ajayaa has quit IRC07:33
*** ajayaa has joined #magnetodb07:55
*** idegtiarov has joined #magnetodb08:01
*** idegtiarov has quit IRC08:09
*** idegtiarov has joined #magnetodb08:14
ajayaaHi dukhlov,08:22
openstackgerritIlya Sviridov proposed a change to stackforge/magnetodb: DevStack installation hanging on ccm stage  https://review.openstack.org/11945808:30
dukhlovHello09:43
dukhlovHi, ajayaa09:43
ajayaadynamodb does not have support for List and dictionary data type it seems.09:44
dukhlovcorrect09:44
ajayaaAre we providing additional functionality?09:44
dukhlovyes09:44
ajayaadukhlov, okay.09:45
*** isviridov_away is now known as isviridov09:45
isviridovHello everybody09:45
ajayaaHi isviridov09:46
isviridovajayaa, hello09:46
ajayaadukhlov, Are we trying to support provisioned throughput as of now?09:47
ajayaain any way*09:48
isviridovWe are not.09:48
isviridovWe are not amazon and not all models are applicable for openstack. I mean mdb can be installed on different hardware and reach different performance.09:50
isviridovHowever, the quota management isin roadmap and it is covers the case mostly.09:50
isviridovBTW we have an opensourced benchmark for mdb. It is not under project ambrela yet, but available for usage.09:52
isviridovHere it is https://github.com/AlexanderChudnovets/magnetodb-test-bench09:52
isviridovrushiagr, what the problem?09:56
ajayaaisviridov, ++09:56
rushiagrI've pinpointed it to command 'ccm test -v 2.0.8' command10:01
rushiagreven when the proxy environment variables are set, it fails10:02
isviridovrushiagr, how much memory?10:02
rushiagr4G total10:02
isviridovrushiagr, all other openstack services are also enabled? nova, swift so on?10:03
rushiagrno, only keystone and horizon10:04
rushiagrlet me check again. It should've started other services too I think10:04
rushiagrhere's the paste http://paste.openstack.org/show/108172/10:05
isviridovI see it first time. Will you file it as a bug? The usuall problem with memory. Each cassandra node requires 500Mb of memory by default.10:17
isviridovrushiagr, FYI here is a patch where we experementing with memory https://review.openstack.org/#/c/119458/10:18
isviridovrushiagr, however have you managed to start C* cluster?10:19
rushiagrthe ccm itself don't have support for proxy it seems10:23
rushiagrI downloaded cassdandra source, and was trying to run "ant jar" inside it, and it failed10:24
rushiagrthis 'ant jar' command I found out by looking into the code of ccm10:24
isviridovrushiagr, not sure about proxy. It is easy to ask in cassandra channel. Have you exported it as env variable?10:32
rushiagrsorry, in a meeting. Will be back in an hour, sorry10:32
isviridovAnother problem with ant, i think. You can try to pass JVM proxy setting like that10:32
isviridovexport JAVA_OPTIONS='-Dhttp.proxyHost=cache.com -Dhttp.proxyPort=3128'10:33
isviridovrushiagr, sure. See you10:33
openstackgerritIlya Sviridov proposed a change to stackforge/magnetodb: Added system memory info output  https://review.openstack.org/11972610:50
*** isviridov is now known as isviridov_away10:51
rushiagrok, I'm back11:10
rushiagrjava_options didn't help11:10
rushiagrisviridov_away: the review you posted is a different error12:09
rushiagrisviridov_away: I'm filing a bug report for my problem, and will include all the details there12:09
rushiagrhere it is https://bugs.launchpad.net/magnetodb/+bug/136678812:15
isviridov_awayrushiagr, I know, I've added more output for shooting https://bugs.launchpad.net/magnetodb/+bug/136446912:15
rushiagrisviridov_away: okay12:16
isviridov_awayrushiagr, first it is not target usecase for devstack and ccm to work behind proxy server.12:18
isviridov_awayrushiagr, but from your output i see that you have problems with DNS12:18
rushiagrisviridov_away: atleast for devstack it is12:19
rushiagrisviridov_away: I have seen bugs related to proxy variables in DevStack12:19
rushiagrand in trove too12:19
rushiagrisviridov_away: DNS I am not sure..12:19
isviridov_awayanother idea define -Dhttp.proxyHost as host without 'http://', and make sure that those paramaters are passed to java process.12:20
isviridov_awaywith checking ps aux| grep java during running ant12:20
rushiagrisviridov_away: okay. Trying..12:20
isviridov_awayAbout DNS, /home/r/.ccm/repository/2.0.8/build.xml:274: java.net.UnknownHostException: repo2.maven.org looks like it can't resolve the host12:22
isviridov_awaycould you wget http://repo2.maven.org from you VM?12:22
* isviridov_away have to leave right now for 30 mins12:23
rushiagrisviridov_away: sure, thanks for your help12:23
rushiagrisviridov_away: I can do a wget for sure12:23
openstackgerritAndrei V. Ostapenko proposed a change to stackforge/magnetodb: Adds mechanism for request time measuring  https://review.openstack.org/11531412:33
*** isviridov_away is now known as isviridov13:03
openstackgerritIlya Sviridov proposed a change to stackforge/magnetodb: Added system memory info output  https://review.openstack.org/11972613:04
isviridovdukhlov, ikhudoshyn_ please take a look at https://review.openstack.org/#/c/119726/13:07
ikhudoshyn_isviridov, will do13:07
ajayaaisviridov, Why dynamodb does not allow attribute definitions which are not present in either primary key and secondary index?13:19
ajayaahttps://bugs.launchpad.net/magnetodb/+bug/126895813:20
dukhlovajayaa, because it is not needed for dynamodb13:20
dukhlovbut magnetodb is based on cassandra13:21
dukhlovand if you specify another attributes you will use native cassandra support for them13:21
ajayaadukhlov, okay.13:22
dukhlovand inserting such attributes (predefined) will work faster  then another attributes(dynamic)13:22
isviridovajayaa, good catch, it is not actual anymore. 'Won't fix'13:25
ajayaadukhlov, Does that mean that in dynamodb I can't have a table with more than six columns?13:26
ajayaadukhlov, Because it seems that I can't have more than five secondary indices.13:27
ajayaaisviridov, I am confused now. Can I create such a table in dynamodb?13:28
ajayaaTable where all attributes are not present in either primary or secondary index.13:29
isviridovIt is up to dynamodb. Have a look at http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Limits.html13:30
isviridovFor magnetodb such limits are very specific to hardware and workload. Benchmarking has to answer for such question.13:31
*** bogeyon18 has joined #magnetodb13:32
*** achuprin has joined #magnetodb13:34
isviridovajayaa, have I answered?13:38
ajayaaisviridov, I haven't used dynamodb. So I don't know in detail about it. Just read the dynamodb paper. As you invalidated the bug, I can deduce that it is possible to create a table such that all attributes are not necessarily part of indices.13:40
*** achuprin has left #magnetodb13:42
*** achuprin has joined #magnetodb13:43
isviridovajayaa, not quite right. It is nessesary to mention all indexed attributes, all 'dynamic' attributes shouldn't be desccribed and will be defined during putting data.13:43
isviridovajayaa, it is possible to get 1 year free tier where dynamodb is included http://aws.amazon.com/free/13:45
isviridovYou need only credit card for this13:45
*** achuprin has left #magnetodb13:46
openstackgerritOleksandr Minakov proposed a change to stackforge/magnetodb: Adds count table item in monitoring API  https://review.openstack.org/11855713:48
*** SpyRay has joined #magnetodb13:49
isviridovHello SpyRay13:49
isviridovSpyRay, welcome back13:49
SpyRayHi all!13:49
*** achuprin has joined #magnetodb13:51
isviridovSpyRay, rushiagr has trables with installing devstack with mdb behind the proxy13:51
isviridovSpyRay, here it is https://bugs.launchpad.net/magnetodb/+bug/136678813:51
isviridovSpyRay, could you take a look?13:51
SpyRaySure13:52
isviridovgr8!13:52
dukhlovajayaa, "Does that mean that in dynamodb I can't have a table with more than six columns?" - No13:56
dukhlovyou can but you can't specify types of them in table schema at table creation time13:57
*** charlesw has joined #magnetodb13:58
isviridovHello charlesw13:59
charleswHi isviridov13:59
isviridovHello ominakov. How are you today?14:01
ominakovhello guys14:02
ominakovhello isviridov, i'am fine14:02
openstackgerritIlya Sviridov proposed a change to stackforge/magnetodb: (WIP)Adds count table item in monitoring API  https://review.openstack.org/11855714:02
isviridovominakov, any success with getting table size?14:03
isviridovDo we know how to get it from C*?14:03
ominakovunfortunately no, I can't find this information in system table14:04
isviridovWhat do guys from cassadnra say?14:05
ominakovi've asked this question in C* irc channel, but not received any response14:06
openstackgerritAndrei V. Ostapenko proposed a change to stackforge/magnetodb: Fixes bug with put item predefined attributes  https://review.openstack.org/11946214:19
*** ajayaa has quit IRC14:29
*** bogeyon18 has quit IRC14:35
*** isviridov is now known as isviridov_away14:40
charleswI don't believe C* maintains a row or key count on table. CQL's select count(*) from has a limit and can take very long time if limit is too high. nodetool cfstats can provide estimate of number of keys but there's no accurate count.14:41
openstackgerritA change was merged to stackforge/magnetodb: Added system memory info output  https://review.openstack.org/11972614:42
openstackgerritAlexei Vinogradov proposed a change to stackforge/magnetodb: Heap memory parameters are configurable now  https://review.openstack.org/11945814:46
*** SpyRay has quit IRC14:49
*** jeromatron has joined #magnetodb15:21
isviridov_awayjeromatron, hello15:23
*** isviridov_away is now known as isviridov15:23
isviridovjeromatron, we need your help with C*15:24
isviridov:)15:24
*** jeromatron has quit IRC15:24
*** jeromatron has joined #magnetodb15:24
jeromatronokay, what's up?15:25
isviridovYou know we are working on building monitoring api in mdb15:25
isviridovThe thing is we need to expose size of table in bytes15:25
isviridovIs there any way in cassadnra to get such info?15:26
*** jeromatron has quit IRC15:27
* isviridov can't catch this guy15:32
*** bogeyon18 has joined #magnetodb15:33
*** jeromatron has joined #magnetodb15:36
isviridovjeromatron, I can't catch you :)15:37
jeromatronI'll be in the office shortly.  the only way I know is through jmx, getting the column family stats on each node and add those up but that's not 100% accurate.15:37
jeromatronthe opscenter guys collect some of that and they expose it through their rest api.  I can check with them on that15:37
jeromatronbrb15:37
*** jeromatron has quit IRC15:37
openstackgerritOleksandr Minakov proposed a change to stackforge/magnetodb: (WIP) Adds count table item in monitoring API  https://review.openstack.org/11855715:40
*** isviridov is now known as isviridov_away16:13
*** rushiagr is now known as rushiagr_away16:14
*** bogeyon18 has quit IRC16:35
*** jeromatron has joined #magnetodb16:39
*** jeromatron has quit IRC16:46
*** jeromatron has joined #magnetodb16:55
*** jeromatron has quit IRC17:00
*** jeromatron has joined #magnetodb17:02
*** bogeyon18 has joined #magnetodb17:06
*** rushiagr_away is now known as rushiagr17:06
*** jeromatron has quit IRC17:17
*** jeromatron has joined #magnetodb17:17
*** jeromatron has quit IRC17:19
rushiagrthanks guys for triaging the bug, and targetting it for j-rc1. Very much needed for our evaluation efforts..17:24
openstackgerritAndrei V. Ostapenko proposed a change to stackforge/magnetodb: Adds mechanism for request time measuring  https://review.openstack.org/11531417:30
*** bogeyon18 has quit IRC17:32
*** bogeyon18 has joined #magnetodb17:37
openstackgerritAndrei V. Ostapenko proposed a change to stackforge/magnetodb: Adds mechanism for request time measuring  https://review.openstack.org/11531417:42
*** jeromatron has joined #magnetodb17:44
openstackgerritAndrei V. Ostapenko proposed a change to stackforge/magnetodb: Adds mechanism for request time measuring  https://review.openstack.org/11531418:08
openstackgerritAndrei V. Ostapenko proposed a change to stackforge/magnetodb: Adds mechanism for request time measuring  https://review.openstack.org/11531418:19
*** rushiagr is now known as rushiagr_away18:32
*** openstackgerrit has quit IRC18:51
jeromatronisviridov_away 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.19:03
*** openstackgerrit has joined #magnetodb19:08
*** jeromatron has quit IRC19:15
*** vnaboychenko has joined #magnetodb19:59
*** jeromatron has joined #magnetodb20:07
*** jeromatron has quit IRC20:51
openstackgerritOleksandr Minakov proposed a change to stackforge/magnetodb: (WIP) Adds count table item in monitoring API  https://review.openstack.org/11855720:58
*** jeromatron has joined #magnetodb21:00
*** bogeyon18 has quit IRC21:28
*** charlesw has quit IRC22:09
*** bogeyon18 has joined #magnetodb22:41
*** vnaboychenko has quit IRC23:37

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!