This is a change that will break scripts parsing output from gfsh.
Scenario is running with a SNAPSHOT build on a cluster with > 1 server. There is a is a durable-cq on one of the servers, and the gfsh command was
The expected output is
The script fails because it captures the command output and looks for the servers with an OK status. With this SNAPSHOT, gfsh outputs to stderr where earlier versions output to stdout. Note that if this command was run with a --member option with a specific server that has the durable-cq, then the output DOES go to stdout.
Bottom line for scripting with gfsh: It's no longer predictable where to look for output, stderr or stdout.
As a side note: From a user point of view, indicating an ERROR status for members on a command like this is misleading. The non-existence of a durable-cq on member 'xxxxx' is a statement of fact and not necessarily an error. Reprorting N/A or DOES NOT EXIST would be more appropriate