toBeTheLight / node-zookeeper-issue

ISSUE 228-1

Run

1. Run npm i
2. Start a zookeeper server
3. cd issue228-1
4. Change the address in options.js to the server address
5. Run node init-data.js until enough nodes have been appended to root path (create 8000 nodes to the root path)
6. Run node watch.js (watch root path's children change event)
7. Run node add.js (create a new child node every 2 seconds)

Result

There will be some logs of empty response when a new node has been append to the path been watched.

Try

• Change the total number in init-data.js.
• Change the length of the node path character.
• Create a large data node, and get it.

When you are getting data, with the increasing of data size（children list data size or single node data size）, the number of empty response increases.

Conclusion

A safe limit times for empty response does not exist.

ISSUE 228-2

1. Run npm i
2. Start a zookeeper server
3. cd issue228-2
4. Change the address in options.js to the server address
5. Run node init-data.js until enough nodes have been appended to root node (create 100000 nodes to root node) and the data size of root node have reached the upper limit.
6. Run node get-node.js (get data of root node) for serveral times. yield:zookeeper_process returned no response too many times: 48
7. Run node get-children.js (get children of root node) for serveral times.yield:zookeeper_process returned no response too many times: 60
8. Maybe 60*3 is a safety limit for no response.