1Mark
1Mark
@addaleax it's just a replicaset with https://www.mongodb.com/docs/manual/tutorial/configure-secondary-only-replica-set-member/#prevent-secondary-from-becoming-primary this enabled. `replicaset that cannot be promoted to writer`
> and you are connecting with directConnection=true to this specific node? Yes that's correct
``` { hosts: [ 'host1:27017', 'host2:27017', 'host3:27017' ], setName: 'someName', setVersion: 31, ismaster: false, secondary: true, primary: 'host1:27017', passive: true, hidden: true, tags: { fqdn: 'someURI', dc: 'something' }, me:...
`mongodb://someURI/?readPreference=secondary&directConnection=true` That's it. The rest is just default from Compass
Will this change the state/settings of the DB or only client session settings?
> @ZhigunovSemen I do see an explanation for the closing of that ticket: > > > Compass requires MongoDB 3.6+. In 1.29 we start using some session-related features only available...
The advice on SO for just using Compass 1.28.4 is the only workaround for now https://stackoverflow.com/a/70298708/5506988
Any update on this please?
Any chance getting a fix for this?
The following works with `xterm-256color` ``` bindkey '^[[H' beginning-of-line bindkey '^[[F' end-of-line ```