V2X Hub is a message handler that acts as a translator and data aggregator/disseminator for infrastructure components of a connected vehicle deployment.
118
stars
67
forks
source link
V2xHub container log size: There is no upper limit for the v2xhub container log #576
The v2xhub container logs increase to 15GB during a load testing with telematic tool. The load testing is conducted in local by sending 10 different J2735 messages at 10hz to MessageReceiver plugin, and the testing lasts for around 10 hours.
Version
4.3.0 (Current)
Expected Behavior
The v2xhub container log should roll after it reaches certain limit.
The v2xhub container log should not indefinitely consume host device disk space.
Actual Behavior
There is no upper limit configured for the v2xhub container. The log size increases to 15GB after around a day during a load testing.
Steps to Reproduce the Actual Behavior
Run v2xhub
Send sample J2735 messages to messagereceiver plugin at 10hz or higher frequency for a long time (more than a day)
Monitor the v2xhub container log disk consumption
Summary
The v2xhub container logs increase to 15GB during a load testing with telematic tool. The load testing is conducted in local by sending 10 different J2735 messages at 10hz to MessageReceiver plugin, and the testing lasts for around 10 hours.
Version
4.3.0 (Current)
Expected Behavior
The v2xhub container log should roll after it reaches certain limit. The v2xhub container log should not indefinitely consume host device disk space.
Actual Behavior
There is no upper limit configured for the v2xhub container. The log size increases to 15GB after around a day during a load testing.
Steps to Reproduce the Actual Behavior
Run v2xhub Send sample J2735 messages to messagereceiver plugin at 10hz or higher frequency for a long time (more than a day) Monitor the v2xhub container log disk consumption
Related Work
No response