[03:13:47] <trq> Hi people. We currently have a replica set with 1 primary and one secondary, both running 2.6.something. We want to move to 3.2. I have looked at the docs and the apparent upgrade path is 2.6 -> 3.0 then 3.0 to 3.2. What I am wondering however is this. Could we create two entirely new secondaries have the data synced accross and then when we are ready step down the old secondary, then step down the old
[03:13:53] <trq> primary and have one of the new secondaries take over ?
[03:14:42] <trq> Failing that, I would probably do the same process but create these new instances using 3.0, sync them, then upgrade them to 3.2 and sync them.
[03:36:42] <joannac> trq: A mixed-mode replica set with 2.6 and 3.2 has never been tested, so I can't validate it would work
[03:37:31] <trq> Yeah, I figured that might be the answer.
[03:38:10] <trq> Do you think it would create issues for the 2 2.6 servers if I tried it?
[03:38:11] <joannac> In addition, there is a change in replication protocol in 3.2, and you won't be able to upgrade to that until all nodes are on 3.2
[03:38:22] <trq> Again, I assume you would just be guessing... never tested :)
[03:42:38] <joannac> don't forget to upgrade the repl protocol https://docs.mongodb.com/manual/release-notes/3.2-upgrade/#upgrade-the-replication-protocol
[03:44:01] <joannac> and bear in mind if you do need to downgrade, you can't downgrade past 2.6.8
[13:13:40] <obiwahn> i have a file with data and i want to import every line so that the linenumber is the key and the data is addressable as data. Can I do that with somehow with mongoimort?
[13:57:53] <jayjo> ok thanks - I got that to go. As the root user of either the db or the server, can I reset the password of the biuser I just created?
[13:58:20] <cheeser> you'll have to drop it and recreate it with the new password
[13:58:59] <jayjo> cheeser: via mongobiuser drop, or in the mongo shell drop the user?
[14:04:04] <cheeser> then you'd need to use mongobiuser
[14:25:36] <jayjo> I've gone through all of the steps of setting up the bi connector and the biuser. If my mongo instance has ssl, does this "postgres" instance have the same ssl creds?
[14:46:16] <jayjo> Via pgadmin3, I can connect to the 'postgres' instance, which is a lie of an instance, but when I try to run queries that retrieve data (I can do anything that doesn't actually access the data right now) I get back the error (from psql): ERROR: Error in python: ConfigurationError Detail: `ssl_cert_reqs` is not ssl.CERT_NONE and no system CA certificates could be loaded. `ssl_ca_certs` is required.
[14:51:42] <jayjo> I don't know the solution to this - security is important to me, but in order to make this work do I need to disable ssl for the connector to do its work?
[14:52:01] <cheeser> you shouldn't need to, no. file a support ticket.
[14:52:14] <jayjo> ok - where do I do that? i haven't submitted one before
[14:55:02] <jayjo> cheeser: is this mongodb tools or python driver? I'm creating an issue?
[15:06:49] <cheeser> jayjo: there's a BIConnector project
[15:09:10] <jayjo> I don't see that project - is it called "BIConnector"?
[15:09:33] <cheeser> oh, that might be an internal guy...
[15:09:42] <cheeser> file it under customer support
[15:10:22] <jayjo> I think I know the error- too ... I got it to work by changing the order of the connection string. I needed the paramater ssl_ca_certs in the string to be the first. The rest are ignored (and the command hangs after running it)
[17:37:39] <DigitalSpeed> so im getting started with a database for the first time and decided to try out mongo...i just created my /data/db directory...how do i claim ownership over this directory so that i can change the read/write permissions?
[17:51:19] <cheeser> if you created you already can
[18:16:58] <StephenLynx> id recommend letting mongo create the files
[18:27:41] <`jpg> I'm seeing strange behaviour when trying to serialise the replSetConfig using mgo BSON.
[18:28:39] <`jpg> Basically I want to be able to set the version field to a specific integer for each version. This works for 1 but anytime I try to do a replSetReconfig with a version other than 1 specified I see the server applying a completely different versoin.
[19:06:48] <DigitalSpeed> okay im having crazy amounts of problems with mongo and looking for some help in simply getting the correct version up and running. been attempting to debug for a while and having no luck.
[19:11:24] <cheeser> gist.github.com if nothing else
[19:52:06] <`jpg> Is it even possible to set the version for a replica set configuration? (aside from the initial replica set configuration at version 0)
[20:03:01] <cheeser> why would you want to set the version?
[20:03:40] <cheeser> DigitalSpeed: what does "ps axuw | grep mongod" show?
[20:05:54] <`jpg> cheeser to enforce that updates to the configuration are only applied in the order I want them to be
[20:06:15] <`jpg> I have a state machine managed by a consensus store that manages the replica set topology
[20:06:56] <`jpg> I need to be able to use the "force" replSetReconfig because at times I may need to recover the replica set when a quorum is not available
[20:07:09] <`jpg> inspecting the code I find that the version is randomly incremented if and only if you are using the force flag
[20:07:17] <DigitalSpeed> ive gotten further along now by specifying each individual package that needed to be uninstalled such as sudo apt-get remove mongodb-org-shell --purge etc but still having issues with getting things running in general. not really sure what the problem is but i think it may have to do with permissions...ive already set the permissions for /data/db and a few other folders/files but i have no idea which ones exactly i need to change
[20:09:54] <`jpg> That is only triggered if "force" is given though
[20:10:06] <`jpg> Otherwise if you don't provide a version then yes, it increments it.
[20:10:23] <`jpg> Should I file a bug that explicit version is ignored if "force" is given?
[20:11:03] <DigitalSpeed> that's essentially the tutorial i followed EXACTLY and it still isnt working. ive changed the permissions already on those two files/directories as well /var/lib/mongodb and /var/log/mongodb
[20:11:04] <cheeser> i would ask on the mailing list first. chances are your understanding might be off a bit. could be a bug, though.
[20:11:34] <cheeser> DigitalSpeed: you shouldn't need to change any permissions if you're doing that as root or sudo'ing appropriately
[20:16:00] <DigitalSpeed> if i just type mongod into my shell everything seems to be operating okay...with the last line of the code as waiting for connections on port 27017. but then when i attempt to start it as a service then open another shell and type sudo systemctl status mongod i get an error telling me how it exited with an invalid argument.
[20:16:18] <DigitalSpeed> is it possible that i messed up the installation with attempting to change the permissions?
[20:25:47] <cheeser> probably, yes. those instructions worked last time i walked through them.
[20:29:42] <dsardari> do you guys discuss any morphia here or is that in a different channel?
[20:32:37] <cheeser> not only do we discuss it, that's my day job. :)
[20:37:59] <dsardari> right on. well i suppose it's not morphia specifically, but using the @Embedded tag, creating that object then adding it to two separate lists on two separate entities should be fine, right?
[20:39:09] <cheeser> you'd end up with two copies of that document in the databse.
[20:40:07] <dsardari> okay, that's what i figured.
[20:45:18] <dsardari> does is it seem typical for a tagging/label system to have a list of embedded tags for a user and embedded tags for each taggable object? deletes/updates on the user tags would have be reflected on the tagged objects and filtering on collections based on the tags would be required. i wasn't sure if references or embedding would make more sense.
[20:48:11] <cheeser> depends on the nature of the tags but usually they're just dumb strings and can be embedded in an array on the taggable item.
[20:50:20] <dsardari> essentially, yeah. a string and an associated color, possibly additional fields in the future. i'm mostly worried about the propagation of delete/update operations across multiple collections and a potentially large amount of items in each.
[21:03:01] <cheeser> if you find yourself updating these labels, it might make sense to make the references. though that has certain obvious performance updates on querying.
[21:03:42] <cheeser> it *might* be better to propagate such updates to all the various embedded tags instead. that's a cost you'd pay once for an update (which is hopefully rare) vs every query.
[21:15:55] <dsardari> yeah, that's what i was thinking too. thanks for the help!
[22:02:37] <DigitalSpeed> so i completely uninstalled then reinstalled using that exact page you linked (for probably the third time today) and still no luck.
[22:02:57] <DigitalSpeed> i have no idea what the issue(s) are/is
[22:05:02] <DigitalSpeed> it finally logged something to my mongod.log so i guess thats good
[23:15:02] <tambu> Anyone open to a query question. http://pastebin.com/E66mKqdE .. assuming the objects under tasks are random and there could be many. I'd like to query for documents with a task that has a status: "running".. also is there a way to filter out the rest of the Task ID that do not have status running from a returned document?