You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TransportMasterNodeOperationAction#checkBlock should be implemented by any subclasses of ``TransportMasterNodeOperationActionbut it's returningnull` by default. We should make that abstract to force implementations for it.
The text was updated successfully, but these errors were encountered:
Master node related operations were missing proper handling of cluster blocks, allowing for example to perform cluster level update settings even before the state was fully restored on initial cluster startup
Note, the change allows to change read only related settings without checking for blocks on update settings, as without it, it means one can't re-enable metadata/write. Also, it doesn't check for blocks on cluster state and health API, as those are allowed to be used even when blocked to figure out what causes the block.
closes#7763closes#7740
Master node related operations were missing proper handling of cluster blocks, allowing for example to perform cluster level update settings even before the state was fully restored on initial cluster startup
Note, the change allows to change read only related settings without checking for blocks on update settings, as without it, it means one can't re-enable metadata/write. Also, it doesn't check for blocks on cluster state and health API, as those are allowed to be used even when blocked to figure out what causes the block.
closes#7763closes#7740
clintongormley
changed the title
[CORE] Make TransportMasterNodeOperationAction#checkBlock abstract
Internal: Make TransportMasterNodeOperationAction#checkBlock abstract
Sep 26, 2014
Master node related operations were missing proper handling of cluster blocks, allowing for example to perform cluster level update settings even before the state was fully restored on initial cluster startup
Note, the change allows to change read only related settings without checking for blocks on update settings, as without it, it means one can't re-enable metadata/write. Also, it doesn't check for blocks on cluster state and health API, as those are allowed to be used even when blocked to figure out what causes the block.
closeselastic#7763closeselastic#7740
TransportMasterNodeOperationAction#checkBlock
should be implemented by any subclasses of ``TransportMasterNodeOperationActionbut it's returning
null` by default. We should make that abstract to force implementations for it.The text was updated successfully, but these errors were encountered: