traditionally, yes, a command line parameter should take precedence over any defaults, configs, etc.
The problem here is that this option is used in _automatic_ (read: unattended) node recovery: to pass a GTID value found via --wsrep-recover option from InnoDB table space. So it is not always user-supplied, and hence grastate.dat takes precedence, since InnoDB does not store DDL and other non-transactional GTIDs.
And I don't think that lp:1111706 can ever be fixed without a risk of inconsistency.
Jay,
traditionally, yes, a command line parameter should take precedence over any defaults, configs, etc.
The problem here is that this option is used in _automatic_ (read: unattended) node recovery: to pass a GTID value found via --wsrep-recover option from InnoDB table space. So it is not always user-supplied, and hence grastate.dat takes precedence, since InnoDB does not store DDL and other non-transactional GTIDs.
And I don't think that lp:1111706 can ever be fixed without a risk of inconsistency.