Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-1996

Avrorouter writes misleading error messages to the log

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.12
    • Fix Version/s: 2.2.14
    • Component/s: avrorouter
    • 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...

        Attachments

          Activity

            People

            Assignee:
            markus makela markus makela
            Reporter:
            valerii Valerii Kravchuk
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Git Integration