<    April 2017    >
Su Mo Tu We Th Fr Sa  
                   1  
 2  3  4  5  6  7  8  
 9 10 11 12 13 14 15  
16 17 18 19 20 21 22  
23 24 25 26 27 28 29  
30
00:09 michaeldgagnon joined
00:10 lino joined
00:11 test222 joined
00:15 Ropeney joined
00:16 armyriad joined
00:27 roger_rabbit joined
00:39 gentunian joined
00:52 Gwayne joined
01:02 sterns joined
01:03 kenansulayman joined
01:09 Siegfried joined
01:10 ren0v0 joined
01:12 Ubuntu-BR joined
01:26 Ratler joined
01:30 Siegfried joined
01:38 Sasazuka joined
02:09 Soopaman joined
02:17 evulish joined
02:18 mdorenka joined
02:43 jri joined
02:55 hillct joined
02:58 Wulf joined
03:05 sspreitz joined
03:19 gentunian joined
03:22 kyuwonchoi joined
03:25 Soopaman joined
03:42 blizzow joined
03:44 harry joined
03:52 tharkun_ joined
04:23 Siegfried joined
04:35 svm_invictvs joined
04:39 ayogi joined
04:44 evulish joined
05:08 VeeWee joined
05:10 kyuwonchoi joined
05:11 kyuwonchoi joined
05:12 kyuwonchoi joined
05:12 kyuwonchoi joined
05:13 kyuwonchoi joined
05:21 preludedrew joined
05:33 evil_gordita joined
05:34 Ratler joined
05:36 lpin joined
05:36 lowbro joined
05:36 lowbro joined
05:37 coudenysj joined
05:39 FrozenSolid joined
05:42 pw_ joined
05:46 Siegfried joined
05:50 pw_ left
05:51 pwen090 joined
05:52 <pwen090> Hello; any C# mongodb linq folks in the house? Looking for some help on the question posted here. If not how in Linq even a raw mongodb query of how might help me figure out how to do it in linq properly. http://stackoverflow.com/questions/43670715/c-sharp-mongodb-merge-listbsondocument-into-single-bsonarray thanks for any help
06:10 blizzow joined
06:11 FrozenSolid joined
06:24 Waheedi joined
06:29 jri joined
06:34 BjornDeRijcke joined
06:34 jri joined
06:42 rendar joined
06:59 okapi joined
07:09 kexmex joined
07:15 kyuwonchoi joined
07:20 Folkol joined
07:20 SkyRocknRoll joined
07:27 Waheedi joined
07:33 Ironhand joined
07:34 <Ironhand> I'm seeing extreme slowness doing an initial sync of a new secondary... secondary is 3.4 using rocksdb, rest of the cluster is 3.2 using wiredtiger
07:35 <Ironhand> most of the time the CPU's of all systems involved are near idle, with the exception of occasional short periods of heavier I/O on the new secondary
07:35 <Ironhand> network traffic is next to none
07:36 <Ironhand> what could be holding back the sync? it's been running for about a day and a half, and has only copied about 300 GB
07:36 <Ironhand> it feels as though mongod is artifically throttling the sync but I can't find anything about that
07:46 Folkol joined
07:58 gfidente joined
08:01 jri_ joined
08:05 m1dnight_ joined
08:09 FatNoLife joined
08:09 ams__ joined
08:11 okapi joined
08:14 Folkol joined
08:39 Folkol joined
09:04 yeitijem joined
09:08 Waheedi joined
09:15 Folkol joined
09:33 FatNoLife joined
09:35 bgy joined
09:35 <bgy> Hi
09:44 harry joined
09:51 coudenysj1 joined
10:17 irclogger_com joined
10:17 Topic for
10:44 bgy joined
11:27 bytee joined
12:10 bytee joined
12:13 StephenLynx joined
12:14 trevor_ joined
12:23 bgy joined
12:34 bytee joined
12:52 darkfrog joined
12:57 michaeldgagnon joined
13:07 ramortegui joined
13:15 jenner_ joined
13:16 mounibec joined
13:21 Soopaman joined
13:28 jenner_ left
13:30 jenner joined
13:32 Hilli joined
13:32 <jenner> guys, what might be the reason for PRIMARY to report a perfectly healthy SECONDARY as down? I can reach secondary from primary using the hostname and port from rs.conf() but even if I increase settings.electionTimeoutMillis the PRIMARY still reports "ExceededTimeLimit: Couldn't get a connection within the time limit.."
13:33 <jenner> also, running rs.status() in secondary shows no errors
13:35 okapi joined
13:44 stalled joined
13:45 hillct joined
13:52 gentunian joined
13:54 blizzow joined
13:59 edrocks joined
14:00 geoffb joined
14:05 sterns joined
14:10 freeport joined
14:15 kyuwonchoi joined
14:22 SkyRocknRoll joined
14:26 pxed joined
14:36 cr0mulent joined
14:37 bgy joined
14:41 freeport joined
15:05 silenced joined
15:27 mounibec joined
15:32 svm_invictvs joined
15:44 evulish joined
15:57 blizzow joined
15:58 svm_invictvs joined
15:59 Siegfried joined
16:05 bytee joined
16:16 silenced joined
16:17 okapi joined
16:21 cr0mulent joined
16:24 <cr0mulent> I’ve saved a single document from a collection as a variable in pymongo, I would like to use the a key from this saved document with .find() I’ve tried to pass in db.collection.find(document[‘key’]) but it does not return results. Could someone suggest a solution?
16:26 edrocks joined
16:34 Siegfried joined
16:34 pxed joined
16:45 Soopaman joined
16:46 kyuwonchoi joined
16:48 d10n-work joined
16:58 sz0 joined
16:58 bgy joined
17:01 kexmex joined
17:04 bytee joined
17:10 pxed joined
17:12 point_ joined
17:12 jri joined
17:16 roger_rabbit joined
17:18 silenced joined
17:24 SkyRocknRoll joined
17:42 MuzlL0dr joined
17:54 joshontheweb joined
17:54 senaps joined
18:16 senaps joined
18:18 dump joined
18:19 Sasazuka joined
18:21 InfoTest joined
18:24 point_ left
18:24 point_ joined
18:24 point_ left
18:31 pxed joined
18:33 evulish joined
18:57 svm_invictvs joined
19:05 senaps joined
19:11 n0arch joined
19:15 rendar joined
19:25 rayn joined
19:26 bytee joined
19:49 senaps joined
19:49 pxed joined
19:52 senaps joined
19:55 gentunian joined
19:56 blizzow joined
20:09 senaps joined
20:12 senaps joined
20:24 edrocks joined
20:29 bytee joined
20:38 knight33 joined
20:41 evulish joined
21:06 mounibec joined
21:10 <knight33> If I have a compound index, how does MongoDB determine what to sort or find on? Does it perform the query, and then the sort? Or vice-versa?
21:10 beauvolio joined
21:17 shackra joined
21:20 <joshua> knight33: Well the query planner tries to optimize the query first I think to limit the number of results. But using compound index sort order matters too. Would have to look at the explain output.
21:20 DroidBurgundy joined
21:22 <knight33> Is there documentation on that? I think I read the query order does not matter, but I have not seen that mentioned in the docs.
21:22 <knight33> Or if the same index can be used for both the query and sort order. Or if sort is calculated before the query.
21:23 <joshua> I think if you are just sorting on a single field it doesn't matter, but if you are doing two it needs to match. I was just doing all this stuff a couple months ago when I was taking one of the online courses they have
21:23 <joshua> https://docs.mongodb.com/manual/reference/method/cursor.explain/
21:23 <joshua> That links to the explain results page.
21:23 evulish joined
21:24 <knight33> Yeah, trying to get my cert, and every question that involves compound indexes and sort I miss, even though I though I understood it.
21:25 <joshua> Read the bottom of the explain results page about Sort Stage and try out some different fields with sort orders etc.
21:26 <joshua> Says if SORT stage is not there then it is using the index to sort. That was kind of key for one of the questions I had in the courses that was tripping people up.
21:27 <joshua> Some info here too https://docs.mongodb.com/v3.0/core/index-compound/
21:29 <knight33> I've read all these pages about a dozen times over the past couple of days. :p
21:29 <joshua> Have you taken the online courses? They have videos explaining the stuff, but its still hard. heh
21:30 <joshua> Testing it out once you learn the explain output helped me see what would happen in different situations
21:30 <knight33> Yup, going through them for the third time. Ugh. Just going to play around some more.
22:08 edrocks joined
22:08 silenced joined
22:21 Siggy_ joined
22:27 bytee joined
22:56 bguery joined
23:02 bytee joined
23:05 raspado joined
23:20 druonysus_ joined
23:31 druonysus_ joined