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

Read-only Tailer cannot read existing queue if some segments were removed/archived #1480

Open
alamar opened this issue Dec 4, 2023 · 1 comment
Labels

Comments

@alamar
Copy link
Contributor

alamar commented Dec 4, 2023

A tailer would read queue if first roll cycle is present but will refuse to read queue if first roll cycle is absent even though some other roll cycles are present. Table Store Read Only directory listing is being used, and it seems that refreshing segments list is a modifying operation which will not be permitted.

It can be worked around by calling createAppender() with readOnly = false.

@JerryShea
Copy link
Contributor

This is only problematic if some roll cycles were removed and refreshDirectoryListing was not called?

@tgd tgd added the review label Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants