[jira] [Commented] (TS-2165) Introduce cluster-wide logging stats
[
https://issues.apache.org/jira/browse/TS-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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 qiushu@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
[jira] [Updated] (TS-2165) Introduce cluster-wide logging stats
[
https://issues.apache.org/jira/browse/TS-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yunkai Zhang updated TS-2165:
-
Fix Version/s: 4.1.0
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}
[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
[jira] [Created] (TS-2170) stats.config.xml is undocumented
Igor Galić created TS-2170:
--
Summary: stats.config.xml is undocumented
Key: TS-2170
URL: https://issues.apache.org/jira/browse/TS-2170
Project: Traffic Server
Issue Type: Bug
Components: Documentation
Reporter: Igor Galić
Save for its DTD: {proxy/config/stats.config.dtd}, {stats.config.xml} is
undocumented.
We should change that.
--
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
[jira] [Commented] (TS-2172) Explicitly use subdir-objects in automake init
[ https://issues.apache.org/jira/browse/TS-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756194#comment-13756194 ] Li-Wen Hsu commented on TS-2172: I've created a pull-request on github: https://github.com/apache/trafficserver/pull/12 Patch is available here: https://github.com/apache/trafficserver/pull/12.patch Explicitly use subdir-objects in automake init -- Key: TS-2172 URL: https://issues.apache.org/jira/browse/TS-2172 Project: Traffic Server Issue Type: Improvement Components: Build Reporter: Li-Wen Hsu This avoids warnings from automake 1.14: warning: source file 'foo/bar.c' is in a subdirectory, but option 'subdir-objects' is disabled and generates correct configure script. -- 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
[jira] [Commented] (TS-2172) Explicitly use subdir-objects in automake init
[ https://issues.apache.org/jira/browse/TS-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756204#comment-13756204 ] ASF subversion and git services commented on TS-2172: - Commit 471655ca1f9469515444decaaa2f81fde0bd5a25 in branch refs/heads/master from [~lwhsu] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=471655c ] TS-2172: Explicitly use subdir-objects in automake init This avoids warnings from automake 1.14 and generates correct configure script. Explicitly use subdir-objects in automake init -- Key: TS-2172 URL: https://issues.apache.org/jira/browse/TS-2172 Project: Traffic Server Issue Type: Improvement Components: Build Reporter: Li-Wen Hsu This avoids warnings from automake 1.14: warning: source file 'foo/bar.c' is in a subdirectory, but option 'subdir-objects' is disabled and generates correct configure script. -- 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
[jira] [Updated] (TS-2172) Explicitly use subdir-objects in automake init
[ https://issues.apache.org/jira/browse/TS-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yunkai Zhang updated TS-2172: - Fix Version/s: 4.1.0 Explicitly use subdir-objects in automake init -- Key: TS-2172 URL: https://issues.apache.org/jira/browse/TS-2172 Project: Traffic Server Issue Type: Improvement Components: Build Reporter: Li-Wen Hsu Fix For: 4.1.0 This avoids warnings from automake 1.14: warning: source file 'foo/bar.c' is in a subdirectory, but option 'subdir-objects' is disabled and generates correct configure script. -- 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
[jira] [Commented] (TS-2172) Explicitly use subdir-objects in automake init
[ https://issues.apache.org/jira/browse/TS-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756205#comment-13756205 ] Yunkai Zhang commented on TS-2172: -- applied, thanks. Explicitly use subdir-objects in automake init -- Key: TS-2172 URL: https://issues.apache.org/jira/browse/TS-2172 Project: Traffic Server Issue Type: Improvement Components: Build Reporter: Li-Wen Hsu This avoids warnings from automake 1.14: warning: source file 'foo/bar.c' is in a subdirectory, but option 'subdir-objects' is disabled and generates correct configure script. -- 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
[jira] [Resolved] (TS-2172) Explicitly use subdir-objects in automake init
[ https://issues.apache.org/jira/browse/TS-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yunkai Zhang resolved TS-2172. -- Resolution: Fixed Assignee: Yunkai Zhang Explicitly use subdir-objects in automake init -- Key: TS-2172 URL: https://issues.apache.org/jira/browse/TS-2172 Project: Traffic Server Issue Type: Improvement Components: Build Reporter: Li-Wen Hsu Assignee: Yunkai Zhang Fix For: 4.1.0 This avoids warnings from automake 1.14: warning: source file 'foo/bar.c' is in a subdirectory, but option 'subdir-objects' is disabled and generates correct configure script. -- 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
[jira] [Commented] (TS-2172) Explicitly use subdir-objects in automake init
[ https://issues.apache.org/jira/browse/TS-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756250#comment-13756250 ] ASF subversion and git services commented on TS-2172: - Commit 3fed45cdc3b18d048c657502fbaf61d1b12a9ee5 in branch refs/heads/master from [~jpe...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=3fed45c ] TS-2172: automake subdir-objects requires AM_PROG_CC_C_O Explicitly use subdir-objects in automake init -- Key: TS-2172 URL: https://issues.apache.org/jira/browse/TS-2172 Project: Traffic Server Issue Type: Improvement Components: Build Reporter: Li-Wen Hsu Assignee: Yunkai Zhang Fix For: 4.1.0 This avoids warnings from automake 1.14: warning: source file 'foo/bar.c' is in a subdirectory, but option 'subdir-objects' is disabled and generates correct configure script. -- 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
[jira] [Commented] (TS-2068) Add subdir-objects to configure.ac
[ https://issues.apache.org/jira/browse/TS-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13756256#comment-13756256 ] Leif Hedstrom commented on TS-2068: --- This was duplicated in TS-2172. Also, be aware that last I checked, this still failed completely on RHEL5. Add subdir-objects to configure.ac -- Key: TS-2068 URL: https://issues.apache.org/jira/browse/TS-2068 Project: Traffic Server Issue Type: Bug Components: Build Reporter: Leif Hedstrom Fix For: 4.1.0 New versions of automake needs it, however, it seems to fail with automake on RHEL5. How can we make this conditional on automake version? -- 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
[jira] [Created] (TS-2173) cache total hit/miss stats broken in version 4.0.1
Scott Harris created TS-2173: Summary: cache total hit/miss stats broken in version 4.0.1 Key: TS-2173 URL: https://issues.apache.org/jira/browse/TS-2173 Project: Traffic Server Issue Type: Bug Components: Stats Reporter: Scott Harris In version 4.0.1 both proxy.node.cache_total_hits and proxy.node.cache_total_misses always return 0 In version 3.2.5 both stats returned correctly. -- 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
[jira] [Updated] (TS-2173) cache total hit/miss stats broken in version 4.0.1
[ https://issues.apache.org/jira/browse/TS-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-2173: -- Fix Version/s: 4.1.0 cache total hit/miss stats broken in version 4.0.1 -- Key: TS-2173 URL: https://issues.apache.org/jira/browse/TS-2173 Project: Traffic Server Issue Type: Bug Components: Stats Reporter: Scott Harris Fix For: 4.1.0 In version 4.0.1 both proxy.node.cache_total_hits and proxy.node.cache_total_misses always return 0 In version 3.2.5 both stats returned correctly. -- 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
