PMXBOT Log file Viewer

Help | Karma | Search:

#mongodb logs for Sunday the 23rd of August, 2015

(Back to #mongodb overview) (Back to channel listing) (Animate logs)
[00:01:35] <MacWinne_> anyone use mongoose here? I have a legacy collection where a specific attribute is either a string or a number.. I need to be able toe query with either one.. is this the purpose of the Mixed type
[07:50:04] <mongotri> .
[07:50:11] <mongotri> I deleted the files of my dbPath(after copying them to external disk). Then restarted the mongodb and copied them again. Now my mongodb server is refusing to start. What should be done now.
[13:00:41] <Modjo> Hello
[15:11:23] <yopp> hi
[18:03:32] <yopp> ""bytes read into cache" : 441206804589,"
[18:03:37] <yopp> for 25Mb collection
[18:48:52] <Fernandos> hi
[18:49:42] <Fernandos> how can I access the the data array at a given index? ie: schema.data[index]
[18:49:50] <Fernandos> for this scheme: var exampleSchema = new Schema({ title:String, data:[{name:String,lastname:String}] });
[18:51:30] <Fernandos> I thought this should work, but it appears to be wrong=> this.find({"_id": id},{"data.$": index}).exec(callback);
[18:52:27] <Fernandos> I've checked that index is populated with a value. ie. index=1;
[18:52:53] <Fernandos> And there is data at that position too, the query seems to be wrong though
[19:20:42] <Douhan> In this page: http://mongodb.github.io/node-mongodb-native/2.0/api/ObjectID.html
[19:21:09] <Douhan> ObjectID(id) says id: Can be a 24 byte hex string, 12 byte binary string or a Number.
[19:21:18] <Douhan> What is hex string or binary string?
[21:54:49] <yopp> um
[21:57:30] <yopp> I've got a situation here: seems like sharded collection is locked by shard balacer, but the process that issued a lock is dead now
[21:58:50] <yopp> and I can see that some request are failed because of this lock in mongos logs: the collection metadata could not be locked for mapreduce, already locked by
[21:59:19] <yopp> what the proper way to resolve this?
[23:11:08] <MacWinne_> does the PRIMARY_PREFERRED concern only apply to read operations?
[23:34:41] <joannac> MacWinne_: ...yes
[23:59:30] <MacWinne_> joannac, so if read consistency is not important, setting to PRIMARY_PREFERRED should be safe?