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

Verification of continuous ingest with agitation should check for orphaned files #167

Open
AlbertWhitlock opened this issue Nov 9, 2021 · 3 comments
Assignees

Comments

@AlbertWhitlock
Copy link
Contributor

Original Jira ticket: ACCUMULO-4748

We have found instances where files are being orphaned but we have not as of writing this ticket figured out why. We should however expand the continuous ingest verification to check for orphaned files which we hypothesize will show up when agitation is when running continuous ingest.

@keith-turner
Copy link
Contributor

We should however expand the continuous ingest verification to check for orphaned files which we hypothesize will show up when agitation is when running continuous ingest.

@milleruntime just made some changes to improve log4j logging related to files in apache/accumulo#2342. Looking at this issue and the changes by @milleruntime made me wonder if orphaned files are found, will there be enough information in the debug logs to understand where they came from? If not that may show us some areas where we could make more improvements to logging about files.

@ctubbsii ctubbsii transferred this issue from apache/accumulo Nov 9, 2021
@milleruntime
Copy link
Contributor

@EdColeman
Copy link
Contributor

Not sure if this is within the scope of what you are considering orphaned files - but there is a similar open issue: apache/accumulo#1227 with some discussion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants