contrail-logs doesn't output log messages for the complete query duration
Bug #1632446 reported by
Sundaresan Rajangam
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R3.0 |
Fix Committed
|
High
|
Sundaresan Rajangam | |||
R3.0.3.x |
Fix Committed
|
High
|
Sundaresan Rajangam | |||
R3.1 |
Fix Committed
|
High
|
Sundaresan Rajangam | |||
Trunk |
Fix Committed
|
High
|
Sundaresan Rajangam |
Bug Description
If there are more log messages for the duration specified in the query, then contrail-logs doesn't dump all the log messages. Expiry time for each row in the query result is 5 minutes. analytics-api takes more time to read the query result from redis and hence some query results get expired before they are read by the anlaytics-api.
To post a comment you must log in.
After further analysis, it is observed that contrail-logs takes more time to read/process the messages from analytics-api and hence back pressures analytics-api to read query result at slower pace.
Profiling stats for contrail-logs shows that lot of time is being spent on xmltodict.parse()