[jira] [Commented] (TC-76) astats-over-http assumes interface bonding

2017-08-16 Thread Matt Mills (JIRA) 

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

Matt Mills commented on TC-76:
--

It does look like this has been resolved in the latest code, 
https://github.com/apache/incubator-trafficcontrol/blob/master/traffic_server/plugins/astats_over_http/astats_over_http.c

There is no references to _slave anymore, and it looks like it directly checks 
the provided interface.

> astats-over-http assumes interface bonding
> --
>
> Key: TC-76
> URL: https://issues.apache.org/jira/browse/TC-76
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Monitor
>Affects Versions: 1.7.0
>Reporter: Amir Yeshurun
>Priority: Minor
>  Labels: astats, interface_bonding
>
> astats-over-http tries to read interface speed at 
> /sys/class/net//slave_
> Will return zero if not found, causing traffic monitor to mis-calculate 
> available bandwidth.
> Suggested workaround (not tested yet) - use a simple bond with just one NIC 
> as a slave.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (TC-76) astats-over-http assumes interface bonding

2017-08-10 Thread Hank Beatty (JIRA) 

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

Hank Beatty commented on TC-76:
---

[~psudaemon] [~jrushford] Is this still an issue? If so, are we going to fix in 
2.1?

> astats-over-http assumes interface bonding
> --
>
> Key: TC-76
> URL: https://issues.apache.org/jira/browse/TC-76
> Project: Traffic Control
>  Issue Type: Bug
>  Components: Traffic Monitor
>Affects Versions: 1.7.0
>Reporter: Amir Yeshurun
>Priority: Minor
>  Labels: astats, interface_bonding
>
> astats-over-http tries to read interface speed at 
> /sys/class/net//slave_
> Will return zero if not found, causing traffic monitor to mis-calculate 
> available bandwidth.
> Suggested workaround (not tested yet) - use a simple bond with just one NIC 
> as a slave.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)