Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V2xHub container log size: There is no upper limit for the v2xhub container log #576

Open
dan-du-car opened this issue Jan 18, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@dan-du-car
Copy link
Collaborator

dan-du-car commented Jan 18, 2024

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

@dan-du-car dan-du-car added bug Something isn't working anomaly labels Jan 18, 2024
@dan-du-car dan-du-car changed the title V2xHub container logs: There is no upper limit for the v2xhub container log V2xHub container log size: There is no upper limit for the v2xhub container log Jan 18, 2024
@dan-du-car dan-du-car added enhancement New feature or request and removed bug Something isn't working anomaly labels Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant