Roughly every minute we get a write transaction to mongo to update the addresses for the stateapi severs ports and network addresses. This should only happen if there is a change in value, else we're just creating db churn. I have hundreds of the following in the transaction log.
2014/04/24-16:25:42 applied
stateServers:apiHostPorts update {u'$set': {u'apihostports': [[{u'networkscope': u'public', u'addresstype': u'ipv4', u'port': 17070, u'value': u'1\
07.170.210.210'}, {u'networkscope': u'local-machine', u'addresstype': u'ipv4', u'port': 17070, u'value': u'127.0.0.1'}, {u'networkscope': u'local-mach\
ine', u'addresstype': u'ipv6', u'port': 17070, u'value': u'::1'}, {u'addresstype': u'ipv6', u'port': 17070, u'value': u'fe80::601:17ff:fe48:801'}]]}}
2014/04/24-16:26:42 applied
stateServers:apiHostPorts update {u'$set': {u'apihostports': [[{u'networkscope': u'public', u'addresstype': u'ipv4', u'port': 17070, u'value': u'1\
07.170.210.210'}, {u'networkscope': u'local-machine', u'addresstype': u'ipv4', u'port': 17070, u'value': u'127.0.0.1'}, {u'networkscope': u'local-mach\
ine', u'addresstype': u'ipv6', u'port': 17070, u'value': u'::1'}, {u'addresstype': u'ipv6', u'port': 17070, u'value': u'fe80::601:17ff:fe48:801'}]]}}
It should be once every 15 minutes once things stabilize, but I agree. Also
when we do this it wakes up everything connected to those machines because
it looks like they have a change so their NotifyWatchers fire (for things
like the Upgrader)
On Thu, Apr 24, 2014 at 9:01 PM, Curtis Hovey <email address hidden> wrote:
> ** Changed in: juju-core /bugs.launchpad .net/bugs/ 1312290 /bugs.launchpad .net/juju- core/+bug/ 1312290/ +subscriptions
> Status: New => Triaged
>
> ** Changed in: juju-core
> Importance: Undecided => High
>
> ** Changed in: juju-core
> Milestone: None => 2.0
>
> ** Tags added: ha mongodb
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> https:/
>
> Title:
> ha stateservers apihostports writing no op/change updates to db
>
> To manage notifications about this bug go to:
> https:/
>