Giter VIP home page Giter VIP logo

Comments (3)

agshift avatar agshift commented on June 27, 2024 3

I think I found a workaround. I think by default the read is not enabled on the secondaries. So I went to the mongo shell for each of mongo-1 and mongo-2 and ran this command

rs.slaveOk()

That solved the problem. Now all my primaries and secondaries are working great. I tested, by inserting a document in primary and reading it from secondaries.

Hope this helps.
Thanks,
Amit

from mongo-k8s-sidecar.

agshift avatar agshift commented on June 27, 2024

I am also getting similar error. The primary (master) is working great. But the 2 secondaries (slaves) are not. Here is what I get after I bash to mongo-1 or mongo-2 (the secondaries):

rs0:SECONDARY> show dbs   
2018-02-26T21:54:26.010+0000 E QUERY    [thread1] Error: listDatabases failed:{   
	"operationTime" : Timestamp(1519682056, 1),   
	"ok" : 0,   
	"errmsg" : "not master and slaveOk=false",   
	"code" : 13435,   
	"codeName" : "NotMasterNoSlaveOk",   
	"$clusterTime" : {   
		"clusterTime" : Timestamp(1519682056, 1),   
		"signature" : {   
			"hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),   
			"keyId" : NumberLong(0)   
		}   
	}   
} :   
_getErrorWithCode@src/mongo/shell/utils.js:25:13   
Mongo.prototype.getDBs@src/mongo/shell/mongo.js:65:1   
shellHelper.show@src/mongo/shell/utils.js:813:19   
shellHelper@src/mongo/shell/utils.js:703:15   
@(shellhelp2):1:1   

But, when I do it on mongo-0 (primary) it shows the databases:

rs0:PRIMARY> show dbs
admin   0.000GB
config  0.000GB
local   0.000GB

I checked rs.status() on each one of them and it looks correct to me. The "me" field has the respective :<port_number> and the "ismaster" and "secondary" fields all look correct. For the slave, I can see that the "primary" also got assigned correctly with the :<port_number> of the primary mongo instance.

It will be great to have a solution to this problem.
Thanks,
Amit

from mongo-k8s-sidecar.

diegosucaria avatar diegosucaria commented on June 27, 2024

Hello, I'm facing the same issue here.

I did rs.slaveOk() on each pod, however, that only worked for a while, and after that, the error came back.

Any ideas how we can make this a permanent change?

from mongo-k8s-sidecar.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.