Mahadev konar commented on ZOOKEEPER-321:

Ben and myself were discussing about session tracking and here is a dump of 
that discussion -

-  we would like to optimize session tracking for the most common zookeeper 
client.  The most common zookeeper clients is  - a read client that can set 
- for a client with watches we would need pings as a part of the client 
library. This is becasue we need to keep track of server being live or being up 
to date. So the client to server traffic would not change at all!
- the traffic from followers to leader will reduce by some (not drastic) amount 
since we would be tracking less sessions.

Given the above findings, the amount of work required to do this doesnt really 
qualify for the amount of savings we will be making on the network traffic 
reduction. I would suggest to close this jira as WONT FIX unless someone else 
thinks otherwise or plans to work on it... 

> optmize session tracking in zookeeper.
> --------------------------------------
>                 Key: ZOOKEEPER-321
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-321
>             Project: Zookeeper
>          Issue Type: New Feature
>          Components: c client, java client, server
>            Reporter: Mahadev konar
>            Assignee: Mahadev konar
>             Fix For: 3.3.0
> sometimes a lot of zookeeper clients are read only. For such clients we do 
> not need the session tracking in zookeeper. Getting rid of session tracking 
> for such clients will help us sclae much better.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Reply via email to