I’m reviewing our v2.3.0 installation prior to starting the upgrade to v2.4.2.
Our logs are littered with these messages (every 5 minutes x 3 hosts)
2022-02-21 12:01:18 level=error ts=2022-02-21T17:01:18.322640776Z caller=flush.go:220 org_id=fake msg="failed to flush user" err="RequestCanceled: request context canceled\ncaused by: context deadline exceeded"
2022-02-21 11:56:18 level=error ts=2022-02-21T16:56:18.319752182Z caller=flush.go:220 org_id=fake msg="failed to flush user" err="RequestCanceled: request context canceled\ncaused by: context deadline exceeded"
2022-02-21 11:51:18 level=error ts=2022-02-21T16:51:18.316841214Z caller=flush.go:220 org_id=fake msg="failed to flush user" err="RequestCanceled: request context canceled\ncaused by: context deadline exceeded"
2022-02-21 11:46:18 level=error ts=2022-02-21T16:46:18.313258018Z caller=flush.go:220 org_id=fake msg="failed to flush user" err="RequestCanceled: request context canceled\ncaused by: context deadline exceeded"
And we have a configuration for flush_op_timeout
in our configuration
flush_op_timeout: 5m
My question(s)
- Is this just normal business or is this something I need to investigate/fix?
- Is this documented somewhere … I’ve been searching and haven’t found anything specific.