Question 350
After admitting a new ElasticXL member, the operator notices package cloning has stalled. Other members are forwarding normally. A proposed change would be to inspect the $FWDIR/log/blade_config state messages, which addresses the different requirement to diagnose cluster member state transitions. Which action instead addresses the observed incident?
Explanation
Correct Answer
The lightshot log documents SMO snapshot and image cloning. This directly addresses the documented incident evidence.
Incorrect Answers
ElasticXL copies the SMO image and settings to added members, yet that applies to distribute the first member software to newly joined nodes rather than the observed issue.
ElasticXL provides member onboarding and clone status commands; this does not resolve the observed condition.
blade_config records important cluster up/down messages, but the current evidence calls for a different R82 operation.