[
https://issues.apache.org/jira/browse/TS-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13757392#comment-13757392
]
ASF subversion and git services commented on TS-2165:
-----------------------------------------------------
Commit 9aad786e82fc13c17fce88959a4cfc80286212f1 in branch refs/heads/5.0.x from
[~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=9aad786 ]
Merge branch 'master' into 5.0.x
* master:
ci: test make distclean in jenkins
ci: fix debug jobs for centos5
TS-2174: Fix StatBinaryEval() on div operation
TS-2173: RECD_COUNTER type is missing in setTokenValue()
TS-2172: automake subdir-objects requires AM_PROG_CC_C_O
sdk docs: fix links & formatting in preface
TS-2172: Explicitly use subdir-objects in automake init
doc: minor formatting fixes
TS-2165: Introduce cluster-wide logging stats
finishing up the cleanup of the admin guide
ci: shrink builders pollng period
ci: fix experimental tag substitution
Fix the 4.0.1 relase
added TS-2167
TS-2167: Update apichecker.pl to give suggestions on additional deprecated
APIs
Doc: Add transaction buffering control.
ci: build experimental configuration options
ci: reduce the number of job templates
Add debug builds for 3.2.x and 4.0.x in the CI
Fix git paths for the 4.0.x branch in Jenkins
> 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
> Fix For: 4.1.0
>
> 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}
> [[email protected] 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
