Providing "--wsrep-start-position='00000000-0000-0000-0000-000000000000:-2' --wsrep-recover" on command line triggers that path:
WSREP: Position 00000000-0000-0000-0000-000000000000:-2 given at startup, skipping position recovery
However, benefits/necessity of it are unclear.
Given, wsrep_recover() is called only when --wsrep-recover is used and
wsrep-start-position given with that doesn't change anything, the code seems
vestigial.
Also, if seqno is -1, whatever is provided by wsrep-start-position is not
considered either, instead values in grastate are used.
Providing "--wsrep- start-position= '00000000- 0000-0000- 0000-0000000000 00:-2' --wsrep-recover" on command line triggers that path:
WSREP: Position 00000000- 0000-0000- 0000-0000000000 00:-2 given at startup, skipping position recovery
However, benefits/necessity of it are unclear.
Given, wsrep_recover() is called only when --wsrep-recover is used and position given with that doesn't change anything, the code seems
wsrep-start-
vestigial.
Also, if seqno is -1, whatever is provided by wsrep-start- position is not
considered either, instead values in grastate are used.