Extending mongooplog to include remote auth and stop point

28 views
Skip to first unread message

David Murphy

unread,
Oct 27, 2014, 5:37:43 PM10/27/14
to mongo...@googlegroups.com

Currently Mongooplog  supports  --from  which could support a host or host+port.

I was thinking of using  r.auth() but  _conn is not exposed to do that from the OpLogReader class.
Would it be best to just make the connection using  OpLogTool  aka Tool()  or should I be extended opLogReader to  support auth.
Given tool.cpp only governs 1 connection and not a from/to, it seems to me we should be using Tool->connect then passing that into opLogReader for setting the correct connection options to use  the tailable cursor.

Am I on the write path there or should I just extend OpLogReader to pass auth to it?

My goal here is to add a few things to oplog to make it more usable as  a PIT recovery tool:
--from—host , alias to --from
--from-user
--from-password
--from-port
--stop  = timestamp to stop replay  at

Thanks
David Murphy

Eliot Horowitz

unread,
Oct 28, 2014, 11:51:35 PM10/28/14
to mongo...@googlegroups.com
The tools are all being move to go @ https://github.com/mongodb/mongo-tools
All new development should go there as we won't be adding any new features to the c++ versions.

--
You received this message because you are subscribed to the Google Groups "mongodb-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-dev...@googlegroups.com.
To post to this group, send email to mongo...@googlegroups.com.
Visit this group at http://groups.google.com/group/mongodb-dev.
For more options, visit https://groups.google.com/d/optout.

David Murphy

unread,
Oct 29, 2014, 11:17:29 AM10/29/14
to mongo...@googlegroups.com
I am not sure that is actually the focus here. The placement wether in go/c++ of where we should support a remote second connection is should it be in the tools generic area or should we extend oplog itself. This seems like something needed for future tools so I am thinking the generic vs specialty class.

That said what is the plan around Mongosniff as I didn't not notice it in the go tools.

Sent from my iPhone

Dan Pasette

unread,
Oct 29, 2014, 6:28:40 PM10/29/14
to mongo...@googlegroups.com
We're not porting mongosniff to the go tools, but it is still maintained.  That said, it hasn't been included in the packages or the tarballs since 2.6.0.  I just looked at the mongosniff docs page and it appears that they weren't updated to reflect this.  We'll update this now.
Reply all
Reply to author
Forward
0 new messages