Comment 2 for bug 1825500
Revision history for this message
| John A Meinel (jameinel) wrote Re: [Bug 1825500] Re: [2.6-beta1] Configuration changes do not propagate correctly with HA enabled | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
67d34a1
(Get the code!)
We don't read from secondaries. This looks more like the config isn't
getting set.
John
=:->
On Fri, Apr 19, 2019, 14:50 Ian Booth <email address hidden> wrote:
> Just a note - the config checksums are used to prevent unnecessary
> firing of the config-changed hook on units. The fact that the bug report
> seems to say that the config-change hooks are correctly firing each time
> a config change is made suggests that the change is correctly being
> stored and propagated to the unit agents. The config checksum is only
> used on the unit agents, not elsewhere.
>
> Perhaps there's a mongo replication issue. It could be that the config
> change is being written to the primary, but the secondaries are stale. I
> can't recall off hand if read operations are allowed to be done on
> secondaries. You could open a mongo client session on the primary and
> check the db content directly to ensure the updated config is being
> written. Or you could run rs.status() in the mongo shell to see that
> everything is healthy.
>
> Regardless, we'll try and reproduce.
>
>
> ** Changed in: juju
> Milestone: None => 2.6-rc1
>
> ** Changed in: juju
> Importance: Undecided => High
>
> ** Changed in: juju
> Status: New => Triaged
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> [2.6-beta1] Configuration changes do not propagate correctly with HA
> enabled
>
> To manage notifications about this bug go to:
> https:/
>
On Fri, Apr 19, 2019, 14:50 Ian Booth <email address hidden> wrote:
> Just a note - the config checksums are used to prevent unnecessary
> firing of the config-changed hook on units. The fact that the bug report
> seems to say that the config-change hooks are correctly firing each time
> a config change is made suggests that the change is correctly being
> stored and propagated to the unit agents. The config checksum is only
> used on the unit agents, not elsewhere.
>
> Perhaps there's a mongo replication issue. It could be that the config
> change is being written to the primary, but the secondaries are stale. I
> can't recall off hand if read operations are allowed to be done on
> secondaries. You could open a mongo client session on the primary and
> check the db content directly to ensure the updated config is being
> written. Or you could run rs.status() in the mongo shell to see that
> everything is healthy.
>
> Regardless, we'll try and reproduce.
>
>
> ** Changed in: juju
> Milestone: None => 2.6-rc1
>
> ** Changed in: juju
> Importance: Undecided => High
>
> ** Changed in: juju
> Status: New => Triaged
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> [2.6-beta1] Configuration changes do not propagate correctly with HA
> enabled
>
> To manage notifications about this bug go to:
> https:/
>