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.

Sign up for GitHub

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

Jump to bottom

No Way to tie Failed Buffer Chunks to Chunk ID #1705

Closed
GLStephen opened this issue Sep 29, 2017 · 2 comments
Closed

No Way to tie Failed Buffer Chunks to Chunk ID #1705

GLStephen opened this issue Sep 29, 2017 · 2 comments
Assignees
@repeatedly
Labels
enhancement Feature request or improve operations v0.14

Comments

@GLStephen
Copy link

  • V14
  • CentOS
  • Forwarder web servers, to aggregators

FluentD log files refer to chunk_id when it is emitting errors and warning. Sometimes of these lead to failed chunks. Those failed chunks can be put in a secondary location. However, the ${chunk_id} is not available in the failed log and the meta file is not in the failed folder so this chunk_id can't be used to figure out which specific failed buffer file an error relates to.

Remedy: file & secondary_file should support something like ${chunk_id} placeholder so that the chunk_id can be retained.
@repeatedly repeatedly self-assigned this Oct 4, 2017
@repeatedly repeatedly added enhancement Feature request or improve operations v0.14 labels Oct 4, 2017
@repeatedly
Copy link
Member

Patch is here: #1708

@GLStephen
Copy link
Author

@repeatedly awesome, thanks!

repeatedly added a commit that referenced this issue Oct 13, 2017
@repeatedly
Merge pull request #1708 from fluent/chunk_id-placeholder
f2736ac 
out_file/out_secondary_file: Support ${chunk_id} placeholder. fix #1705
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@repeatedly repeatedly

Labels
enhancement Feature request or improve operations v0.14
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@repeatedly @GLStephen