Re: [ClusterLabs] attrd/attrd_updater asynchronous behavior

I got an answer on IRC from Ken Gaillot. Bellow his answer for tracking purpose. On Mon, 16 Apr 2018 23:28:39 +0200 Jehan-Guillaume de Rorthais wrote: [...] > * does looping until the value becomes available is enough to conclude all > other node have the same value? Or is

[ClusterLabs] attrd/attrd_updater asynchronous behavior

Hi, I have a question in regard with attrd asynchronous behavior In PAF, during the election process to pick the best PgSQL master, we are using private attributes to publish the status (LSN) of each pgsql instances during the pre-promote action. Because we need these LSN from each nodes during