[jira] [Commented] (TS-2165) Introduce cluster-wide logging stats

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13755956#comment-13755956 ] 

ASF subversion and git services commented on TS-2165:
-----------------------------------------------------

Commit 49e8a7a0e538a53083b564baaf06a51f96acc831 in branch refs/heads/master from [~yunkai]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=49e8a7a ]

TS-2165: Introduce cluster-wide logging stats

With this patch, we can see the logging status of whole cluster.

Signed-off-by: Yunkai Zhang <qi...@taobao.com>

                
> Introduce cluster-wide logging stats
> ------------------------------------
>
>                 Key: TS-2165
>                 URL: https://issues.apache.org/jira/browse/TS-2165
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: Logging, Stats
>            Reporter: Yunkai Zhang
>            Assignee: Yunkai Zhang
>         Attachments: 0001-TS-2165-Introduce-cluster-wide-logging-stats.patch, 0001-TS-2165-Introduce-cluster-wide-logging-stats.V2.patch
>
>
> Based on TS-2145, I'm going to introduce cluster-wide logging stats, so that we can see the logging status of whole cluster.
> I have submitted a patch, which has been tested in our product and master branch. Here is an example to show how this patch works:
> I tested it with:
> 1) Two log clients, test78/test79, in the same cluster.
> 2) One log server, test81.
> I used jtest to do stress testing(rm -rf /var/run/trafficserver/*.snap to clear history value before testing), after a while, stop jtest, and use following commands to verify the logging metrics:
> ==Log client1: test78==
> {code}
> [root@test78 ~]# lynx -dump http://localhost:8080/stat/ | grep -E 'cluster.*sent_to_network|log_access_ok'
> proxy.node.log.event_log_access_ok=6898925
> proxy.cluster.log.event_log_access_ok=8795630
> proxy.cluster.log.num_sent_to_network=8795630
> proxy.cluster.log.num_lost_before_sent_to_network=0
> proxy.cluster.log.bytes_sent_to_network=1268834448
> proxy.cluster.log.bytes_lost_before_sent_to_network=0
> proxy.cluster.log.bytes_sent_to_network_avg_10s=0
> proxy.process.log.event_log_access_ok=6898925
> {code}
> ==Log client2: test79==
> {code}
> [root@test79 ~]# lynx -dump http://localhost:8080/stat/ | grep -E 'cluster.*sent_to_network|log_access_ok'
> proxy.node.log.event_log_access_ok=1896705
> proxy.cluster.log.event_log_access_ok=8795630
> proxy.cluster.log.num_sent_to_network=8795630
> proxy.cluster.log.num_lost_before_sent_to_network=0
> proxy.cluster.log.bytes_sent_to_network=1268834448
> proxy.cluster.log.bytes_lost_before_sent_to_network=0
> proxy.cluster.log.bytes_sent_to_network_avg_10s=0
> proxy.process.log.event_log_access_ok=1896705
> {code}
> ==Log server: test81==
> {code}
> [root@test81.cn8 trafficserver]# lynx -dump http://localhost:8080/stat/ | grep -E "received_from_network|_to_disk" | grep process
> proxy.process.log.num_received_from_network=8795630
> proxy.process.log.num_flush_to_disk=8795630
> proxy.process.log.num_lost_before_flush_to_disk=0
> proxy.process.log.bytes_received_from_network=1268834448
> proxy.process.log.bytes_flush_to_disk=857743696
> proxy.process.log.bytes_lost_before_flush_to_disk=0
> proxy.process.log.bytes_written_to_disk=857743696
> proxy.process.log.bytes_lost_before_written_to_disk=0
> {code}
> According these stats data above, We can easy to verify whether the logs in the whole cluster are lost.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira