Log file Viewer

[02:20:01] <akadian> hi

[03:02:41] <aniasis> Hello I'm attempting to install the mongodb driver, but I am receiving errors

[03:03:12] <aniasis> gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"

[03:03:34] <aniasis> nodejs v0.12.7

[03:03:45] <aniasis> node-gyp -v v2.0.1

[08:33:15] <nEosAg> why mongodb v3 takes too much time to accept connections immediately after start

[08:33:25] <nEosAg> how to debug ..any help?

[08:33:50] <nEosAg> because of that my migration script is breaking and couldn't migrate to v3

[08:54:57] <nEosAg> v3.0.6

[11:21:02] <MadWasp> Hello, what would be the best way to test if a single document matches a query? I’m using spring data mongodb to query a bunch of documents and i want to test every single one against a query.

[11:22:29] <MadWasp> is there some method in the java driver i can use?

[12:06:03] <madlord> hello guys, I'm suffering with the mongodb bson limit of 16MB when saving data of one year from a sensor that uploads its measures each 5 sec

[12:06:15] <madlord> is that any way to handle this?

[12:06:37] <madlord> I was looking for gridfs option, but I'm not sure if it is the right option here

[12:06:41] <madlord> thank you

[12:06:53] <flok420> madlord: I changed my schema to one document per sensor-reading

[12:07:13] <madlord> flok420: one document means one collection?

[12:09:38] <madlord> flok420: do you have a link exemplifying this?

[12:14:13] <MadWasp> madlord: one document means one document

[12:14:30] <MadWasp> the 16mb limit is per document

[12:15:05] <madlord> MadWasp: :) sure I have to study about this

[12:15:23] <madlord> each database has collections, and collections has documents?

[12:15:41] <MadWasp> ye, documents are a bit like a row in sql databases

[12:16:27] <MadWasp> so collections are the counterpart of tables

[12:17:41] <MadWasp> madlord: you’re saving roughly 6 million documents / year so you should think about some indices before inserting them

[12:17:50] <madlord> hm

[12:18:16] <madlord> yes

[12:18:22] <MadWasp> if you want you can upload a single reading on gist and i could suggest some

[12:18:38] <madlord> I was storing each reading in a nested sstructure of the sensor

[12:19:27] <MadWasp> that will take longer each time your document grows and you’ll hit that 16mb limit

[12:23:35] <madlord> MadWasp: I will try a different structure here to see if it works :) thank you

[12:24:02] <MadWasp> i’d suggest a collection for sensors and one for readings

[12:31:49] <madlord> MadWasp: yes, it makes sense to me now :)

[13:24:28] <djMax> I have a replica set member stuck in "RECOVERING" for days now... The other two members seem fine. What's the easiest fix?

[13:25:04] <Zelest> Not saying it's the best way.. or the right way.. but I tend to shut down that replica member.. remove the entire datadir.. and starting it again..

[13:25:27] <Zelest> That syncs up the entire database using a fresh copy instead of trying to catch up

[13:25:51] <Zelest> but yeah, take a backup of the old data (just copy the datadir after it's shutdown) ..

[13:26:00] <Zelest> Depends of course entirely of how big your database is

[13:26:45] <djMax> so remove the entire contents of dbpath? admin, journal, local, etc?

[13:27:01] <djMax> how does it know the keys and stuff for the rs?

[13:27:11] <djMax> or is everything it needs in the config

[13:28:16] <Zelest> Ah, true, I normally start my server using the --replSet .. or, my OS does that for me

[13:28:24] <Zelest> removing the related database should be enough

[13:29:58] <djMax> worked, thanks

[13:30:19] <Zelest> :)

[13:30:29] <djMax> now to upgrade from 2.6.5 to 3... Any big gotchas?

[13:31:09] <Zelest> http://docs.mongodb.org/manual/release-notes/3.0-upgrade/#upgrade-requirements

[13:31:11] <Zelest> :)

[13:32:29] <djMax> yeah, just wasn't sure if there was any real-world mods to that. But reading through it now

[13:32:59] <Zelest> Ah, I still run 2.6.7 myself so, no idea sadly. :)

[13:44:37] <cheeser> Zelest: i'd add a new replSet and when that one's done syncing, remove the errant one.

[13:45:51] <Zelest> yeah, probably a better idea yeah :)

[13:55:39] <Zelest> nice to see paypal using mongodb :)

[15:16:29] <nixfreak> Good morning , is there a certain permission value I need to set for /data/db in order to write too besides 0700 ?

[15:41:42] <bros_> I have a collection "accounts" that has a group of subdocuments called "users" that has a field for "email". How can I do what would have effectively been "SELECT email FROM accounts" in SQL? Do I need aggregation? I want to aggregate all over the account documents, lumping all e-mails into one resulting array at the end.

[15:44:03] <cheeser> you just want the email addresses?

[18:38:00] <amitprakash> Hi, while using pymongo.MongoClient to connect to a replica set, I am getting a ServerSelectionTimeoutError: No replica set members match selector "<function any_server_selector at 0x7f601e10f158>"

[18:38:04] <amitprakash> How do I resolve this issue?

[21:33:43] <MBravo> hi! has anyone met a problem w/ 3.0.5+ where logs are getting bloated pretty fast even though quiet: true is set?