Quoting: https://github.com/corosync/corosync/commit/ebbba5b05b05a0943dce50be16282657a31c2e05 corosync internal theory of operation is that without a quorum provider the cluster is always quorate. This is fine for membership free clusters but it does pose a problem for applications that need membership and "real" quorum. this change add quorum_type to quorum_initialize call to return QUORUM_FREE or QUORUM_SET. Applications can then make their own decisions to error out or continue operating. The only other way to know if a quorum provider is enabled/configured is to poke at confdb/objdb, but adds an unnecessary burden to applications that really don't need to use an entire library for a boolean value. I am clearly at RFC stage since variable/const names are up for discussion/improvement. The other option to approach this issue is to use a 3 state is_quorate, but that can break applications (and corosync internal) in a more subtle way. By changing the API in such a simple way, old applications will fail to build (in one function only) and will get the info they need right away. Fabio _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
