Uploaded image for project: 'Samza'
  1. Samza
  2. SAMZA-1768

Handle corrupted OFFSET file elegantly

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.0
    • None
    • None

    Description

      TaskStorageManager.readOffsetFile() has a bug that if the OFFSET file is corrupted, it will throw exception and shut down the container. If host affinity is turned on, the container won't be able start up again since it will read the same corrupted OFFSET file every time, until it was manually removed. Since we cannot recover in this case, we should catch the exception and return null and let the store bootstrap from changelog.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. SAMZA-1777 Logged store OFFSET file write during flush should be atomic

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link GitHub Pull Request #588

          Activity

            People

              xinyu Xinyu Liu
              xinyu Xinyu Liu
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: