Progress update when many znodes exist

[tr0k]

When running a command with a more complex policy:
zkpolicy -c /opt/zkpolicy/conf/config-custom.yml audit
on a zk instance with multiple znodes I experienced long execution times (of a few minutes).

In this case, the progress updates would be of help to a user waiting for the result.
I propose to calculate the progress in % based on the number of znodes retrieved/total znodes to be retrieved.

The ensemble against which I was running the commands had the following number of znodes:

getAllChildrenNumber /
42161

The total number of znodes to be retrieved could be easily calculated using getAllChildrenNumber method.

[arvchristos]

Hello @tr0k ,

Thank you for reporting this behavior.
As far as I know, getAllChildrenNumber call is not listing all nodes that will be parsed recursively but only a single level of children, hence it is not straightforward to determine the number of nodes to be parsed during znode tree traversal.

I totally agree that this will be really helpful for ZK ensembles with huge znode number like the one that you are currently executing zkpolicy on

Will have to explore the optimal way to implement this functionality. I am always open to suggestions 😄