You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Mahadev konar (JIRA)" <ji...@apache.org> on 2009/02/19 03:25:01 UTC
[jira] Created: (ZOOKEEPER-321) optmize session tracking in
zookeeper.
optmize session tracking in zookeeper.
--------------------------------------
Key: ZOOKEEPER-321
URL: https://issues.apache.org/jira/browse/ZOOKEEPER-321
Project: Zookeeper
Issue Type: New Feature
Reporter: Mahadev konar
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.
[jira] Commented: (ZOOKEEPER-321) optmize session tracking in
zookeeper.
Posted by "Flavio Paiva Junqueira (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830194#action_12830194 ]
Flavio Paiva Junqueira commented on ZOOKEEPER-321:
--------------------------------------------------
In your example, it seems that we would be generating 256kbits/s, which is indeed small if we are talking about 100Mbit/1Gbit interfaces. Thanks for the insight.
> 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.
[jira] Updated: (ZOOKEEPER-321) optmize session tracking in
zookeeper.
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-321:
-----------------------------------
Affects Version/s: 3.2.2
Fix Version/s: (was: 3.3.0)
> 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
> Affects Versions: 3.2.2
> Reporter: Mahadev konar
> Assignee: Mahadev konar
>
> 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.
[jira] Commented: (ZOOKEEPER-321) optmize session tracking in
zookeeper.
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829720#action_12829720 ]
Mahadev konar commented on ZOOKEEPER-321:
-----------------------------------------
sorry i used size of long as 4 in the above calculations. Please replace it with 8 and you will get the new numbers which are mostly of the same order.
> 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.
[jira] Commented: (ZOOKEEPER-321) optmize session tracking in
zookeeper.
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829719#action_12829719 ]
Mahadev konar commented on ZOOKEEPER-321:
-----------------------------------------
flavio,
here is what I think the average use case will be. Lets say we have 2000 clients on each of the zookeeper server. If we assume that even 100% of these clients are read only, we will be saving - <size of long> * 2000 of traffic from a follower to the leader (the session touch updates that go out every 2 seconds to the leader). That is 8 KB of data from the follower to the leader.
A total of 4 * 8KB of data can be saved on the net traffic to the leader from the followers which is not very high at all. The amount of the network saving that we will make does not seem like worth the effort that we would be spending in doing whats being proposed (basically no session tracking for read only/watching clients).
Does this clear things out?
> 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.
[jira] Commented: (ZOOKEEPER-321) optmize session tracking in
zookeeper.
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675165#action_12675165 ]
Mahadev konar commented on ZOOKEEPER-321:
-----------------------------------------
true... read only clients was just an exmaple :) ...
> optmize session tracking in zookeeper.
> --------------------------------------
>
> Key: ZOOKEEPER-321
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-321
> Project: Zookeeper
> Issue Type: New Feature
> Reporter: Mahadev konar
>
> 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.
[jira] Commented: (ZOOKEEPER-321) optmize session tracking in
zookeeper.
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829303#action_12829303 ]
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 watches
- 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.
[jira] Updated: (ZOOKEEPER-321) optmize session tracking in
zookeeper.
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar updated ZOOKEEPER-321:
------------------------------------
Fix Version/s: (was: 3.2.0)
3.3.0
moving it to 3.3...
> 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.
[jira] Commented: (ZOOKEEPER-321) optmize session tracking in
zookeeper.
Posted by "Flavio Paiva Junqueira (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829621#action_12829621 ]
Flavio Paiva Junqueira commented on ZOOKEEPER-321:
--------------------------------------------------
By no means I'm trying to say we shouldn't close this issue, but I'm curious to understand how you reached the conclusion that the reduction amount of traffic is negligible. If it is not too much trouble, could you please elaborate?
> 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.
[jira] Commented: (ZOOKEEPER-321) optmize session tracking in
zookeeper.
Posted by "Benjamin Reed (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675164#action_12675164 ]
Benjamin Reed commented on ZOOKEEPER-321:
-----------------------------------------
not just read only clients. any client that doesn't have an ephemeral node doesn't need to have its session tracked.
> optmize session tracking in zookeeper.
> --------------------------------------
>
> Key: ZOOKEEPER-321
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-321
> Project: Zookeeper
> Issue Type: New Feature
> Reporter: Mahadev konar
>
> 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.
[jira] Updated: (ZOOKEEPER-321) optmize session tracking in
zookeeper.
Posted by "Patrick Hunt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Hunt updated ZOOKEEPER-321:
-----------------------------------
Component/s: server
java client
c client
Fix Version/s: 3.2.0
> 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
> Fix For: 3.2.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.
[jira] Resolved: (ZOOKEEPER-321) optmize session tracking in
zookeeper.
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar resolved ZOOKEEPER-321.
-------------------------------------
Resolution: Won't Fix
resolving this as wont fix!
> 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.
[jira] Assigned: (ZOOKEEPER-321) optmize session tracking in
zookeeper.
Posted by "Mahadev konar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ZOOKEEPER-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mahadev konar reassigned ZOOKEEPER-321:
---------------------------------------
Assignee: Mahadev konar
> 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.2.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.