[MXS-1996] Avrorouter writes misleading error messages to the log Created: 2018-08-02  Updated: 2020-08-25  Resolved: 2018-08-21

Status: Closed
Project: MariaDB MaxScale
Component/s: avrorouter
Affects Version/s: 2.2.12
Fix Version/s: 2.2.14

Type: Bug Priority: Major
Reporter: Valerii Kravchuk Assignee: markus makela
Resolution: Fixed Votes: 0
Labels: None

Sprint: MXS-SPRINT-64

 Description   

In some cases avrorouter just works and .avro files are created as expected, but in the log of MaxScale we may see messages like these:

2018-08-02 10:32:38 error : Failed to initialize avrofile.
2018-08-02 10:32:38 error : [avrorouter] Failed to open file '/var/lib/maxscale/avro/DB.table1.000001.avro' when generating file index.
2018-08-02 10:32:38 notice : [avrorouter] End of binlog file [binlog.000002] at 362 with a close event. Rotating to next binlog file [binlog.000003].
2018-08-02 10:32:38 error : Failed to initialize avrofile.
2018-08-02 10:32:38 error : [avrorouter] Failed to open file '/var/lib/maxscale/avro/DB.table2.000001.avro' when generating file index.
...
2018-08-02 10:32:38 error : Failed to initialize avrofile. (subsequent similar messages suppressed for 10000 milliseconds)
...

These messages are either false positives (and then should not be marked as errors) or they miss useful information about possible reason for the error.

So, it's hard to decide if it's safe to ignore them when everything seems to work fine...



 Comments   
Comment by markus makela [ 2018-08-02 ]

The hypothesis for these errors is that the tables have been created but no data has been replicated for them.

Generated at Thu Feb 08 04:10:56 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.