Bug 706311

Summary: starting openais adds 40KB/s traffic on network device
Product: [Fedora] Fedora Reporter: dan clark <2clarkd>
Component: openaisAssignee: Steven Dake <sdake>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 14CC: 2clarkd, fdinitto, sdake
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-31 21:47:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description dan clark 2011-05-20 03:13:21 UTC 
Description of problem:
startup corosync (no openais) and analyze network traffic (minimal)
startup openais w/ corosync and there is 40KB/s of network traffic almost all repeated packets of the same type.

Version-Release number of selected component (if applicable):


How reproducible:
analyze network traffic on a single node instance of openais on corosync

Steps to Reproduce:
1. run wireshark
2. start openais on single node
3.
  
Actual results:
40KB/s network traffic

Expected results:
minimal network traffic

Additional info:
Comment 1 Steven Dake 2011-05-20 03:54:30 UTC 
This is token traffic and normal.  It can be reduced, which either increases latency or increases failure detection time, or reduces failure detection reliability.

man corosync.conf
       token  This timeout specifies in milliseconds until  a  token  loss  is
              declared  after  not  receiving a token.  This is the time spent
              detecting a failure of a processor in the current configuration.
              Reforming  a  new  configuration  takes about 50 milliseconds in
              addition to this timeout.

              The default is 1000 milliseconds.

       token_retransmit
              This timeout specifies in milliseconds  after  how  long  before
              receiving  a  token  the  token  is retransmitted.  This will be
              automatically calculated if token is modified.  It is not recom‐
              mended  to  alter  this value without guidance from the corosync
              community.

              The default is 238 milliseconds.

       hold   This timeout specifies in milliseconds how long the token should
              be  held  by  the  representative when the protocol is under low
              utilization.   It is not recommended to alter this value without
              guidance from the corosync community.

              The default is 180 milliseconds.

       token_retransmits_before_loss_const
              This  value  identifies  how  many  token  retransmits should be
              attempted before forming a new configuration.  If this value  is
              set,  retransmit  and hold will be automatically calculated from
              retransmits_before_loss and token.

              The default is 4 retransmissions.
       merge  This  timeout  specifies in milliseconds how long to wait before
              checking for a partition when  no  multicast  traffic  is  being
              sent.   If  multicast traffic is being sent, the merge detection
              happens automatically as a function of the protocol.

              The default is 200 milliseconds.
Comment 2 Steven Dake 2011-05-20 18:01:48 UTC 
dan indicated this only occurs when openais plugins are loaded, but not when corosync is used alone.
Comment 3 dan clark 2011-05-31 21:47:10 UTC 
I can not re-create this problem with a proper configuration.  I believe the single node instance was causing additional network traffic due to a bad network configuration prevention proper communication.