zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Leader Ni (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-1804) Stat the realtime tps of zookeepr server
Date Mon, 04 Nov 2013 06:39:17 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Leader Ni updated ZOOKEEPER-1804:
---------------------------------

    Description: 
At this time, we assessed whether zookeeper supports some business scenarios, always use the
number of subscribers, or to assess the number of clients。

You konw, some times, many client connection with zookeeper, but do noting, and the onthers
do complex business logic。

So,we must stat the realtime tps of zookeepr。


[-----------------Solution-------------------]

Solution1: 

If you only want to know the real time transaction processed, you can use the patch "ZOOKEEPER-1804.patch".

Solution2:

If you also want to know how client use zookeeper, and the real time r/w ps of each zookeeper
client, you can use the patch "ZOOKEEPER-1804-2.patch"
use java properties: -Dserver_process_stats=true to open the function.

Sample:
$>echo rwps|nc localhost 2181
RealTime R/W Statistics:
        getChildren2:   0.5994005994005994
        createSession:  1.6983016983016983
        closeSession:   0.999000999000999
        setData:     110.18981018981019
        setWatches:   129.17082917082917
        getChildren:    68.83116883116884
        delete:      19.980019980019982
        create:      22.27772227772228
        exists:      1806.2937062937062
        getDate:     729.5704295704296

  was:
At this time, we assessed whether zookeeper supports some business scenarios, always use the
number of subscribers, or to assess the number of clients。

You konw, some times, many client connection with zookeeper, but do noting, and the onthers
do complex business logic。

So,we must stat the realtime tps of zookeepr。


[-----------------Solution-------------------]

Solution1: 

If you only want to know the real time transaction processed, you can use the patch "ZOOKEEPER-1804.patch".

Solution2:

If you also want to know how client use zookeeper, and the real time r/w ps of each zookeeper
client, you can use the patch "ZOOKEEPER-1804-2.patch"

Sample:
$>echo rwps|nc localhost 2181
RealTime R/W Statistics:
        getChildren2:   0.5994005994005994
        createSession:  1.6983016983016983
        closeSession:   0.999000999000999
        setData:     110.18981018981019
        setWatches:   129.17082917082917
        getChildren:    68.83116883116884
        delete:      19.980019980019982
        create:      22.27772227772228
        exists:      1806.2937062937062
        getDate:     729.5704295704296


> Stat the realtime tps of zookeepr server
> ----------------------------------------
>
>                 Key: ZOOKEEPER-1804
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1804
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>            Reporter: Leader Ni
>            Assignee: Leader Ni
>         Attachments: ZOOKEEPER-1804.patch
>
>
> At this time, we assessed whether zookeeper supports some business scenarios, always
use the number of subscribers, or to assess the number of clients。
> You konw, some times, many client connection with zookeeper, but do noting, and the onthers
do complex business logic。
> So,we must stat the realtime tps of zookeepr。
> [-----------------Solution-------------------]
> Solution1: 
> If you only want to know the real time transaction processed, you can use the patch "ZOOKEEPER-1804.patch".
> Solution2:
> If you also want to know how client use zookeeper, and the real time r/w ps of each zookeeper
client, you can use the patch "ZOOKEEPER-1804-2.patch"
> use java properties: -Dserver_process_stats=true to open the function.
> Sample:
> $>echo rwps|nc localhost 2181
> RealTime R/W Statistics:
>         getChildren2:   0.5994005994005994
>         createSession:  1.6983016983016983
>         closeSession:   0.999000999000999
>         setData:     110.18981018981019
>         setWatches:   129.17082917082917
>         getChildren:    68.83116883116884
>         delete:      19.980019980019982
>         create:      22.27772227772228
>         exists:      1806.2937062937062
>         getDate:     729.5704295704296



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message