Log file Viewer

[02:38:26] <UberDuper> ernetas: Could be powerof2sizes if you've got a particularly large dataset. Could be the size of the oplog changed.

[02:39:23] <UberDuper> If you don't define a size for the oplog in the config, it'll create one as a percentage of available disk space during an initial sync.

[02:44:48] <UberDuper> That should be obvious difference in size of the local db

[10:54:45] <kurushiyama> niemeyer I am trying to wrap my head around the fact that all time.Time values are converted to UTC when persisted with mgo. I guess there is a good reason about it, but I can not deduct it. Could you clarify that?

[11:14:52] <niemeyer> kurushiyama, p4r4n01d: That's what the spec says timestamps in the database side should be..

[11:16:47] <p4r4n01d> niemeyer Thanks a lot. Yes, "UTC datetime" is a pretty clear statement.

[11:18:29] <niemeyer> np

[14:24:48] <ernetas> UberDuper: yeah, that does not seem to be it. I do define oplog size and that shouldn't show up in 'show dbs' output, should it?

[20:01:39] <UberDuper> ernetas: Yes you'd see the increased size of the local database. The only other thing I can think of off the top of my head is powerof2sizes.

[20:02:45] <cheeser> which is the new default i believe, actually, so you might be on to something

[20:03:22] <UberDuper> He'd still have to manually turn it on. An initial sync wouldn't cause it to be enabled.

[20:04:17] <UberDuper> But if he'd enabled it after his collections were fairly large, an initial sync would then apply it to every doc.