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

Cherry-pick #23417 to 7.x: Update filestream reader offset when line is skipped #23624

Merged
merged 1 commit into from
Jan 21, 2021

Conversation

kvch
Copy link
Contributor

@kvch kvch commented Jan 21, 2021

Cherry-pick of PR #23417 to 7.x branch. Original message:

What does this PR do?

This PR adds two previously missing offset updates to the filestream reader when a line is skipped.

Why is it important?

The offset could be incorrect if Filebeat skips the line for the following reasons:

  1. The line is unparsable
  2. The line should not be published because of user configuration in export_line or import_line

If the offset is not updated in the reader, the state information of newer published events become incorrect. This might lead to duplicated events if Filebeat is restarted.

Checklist

  • My code follows the style guidelines of this project
    - [ ] I have commented my code, particularly in hard-to-understand areas
    - [ ] I have made corresponding changes to the documentation
    - [ ] I have made corresponding change to the default configuration files
    - [ ] I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

How to test this PR locally

  1. Start Filebeat with the following configuration
filebeat.inputs:
- type: filestream
  enabled: true
  paths:
    - test.log
  exclude_lines: ['^DONOTPUBLISH']

output.elasticsearch:
  enabled: true
  hosts: ["localhost:9200"]

Reading this file

line 1
DONOTPUBLISH line2
line 3
DONOTPUBLISH line4
line 5
  1. Stop Filebeat
  2. Add new lines to the input file which will be published
  3. Start Filebeat

Validate that Filebeat does not send duplicate messages.

@kvch kvch added [zube]: In Review backport Team:Services (Deprecated) Label for the former Integrations-Services team labels Jan 21, 2021
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jan 21, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/integrations-services (Team:Services)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jan 21, 2021
This PR adds two previously missing offset updates to the `filestream` reader when a line is skipped.

The offset could be incorrect if Filebeat skips the line if the line should not be published because of user configuration in `export_line` or `import_line`

If the offset is not updated in the reader, the state information of newer published events become incorrect. This might lead to duplicated events if Filebeat is restarted.

(cherry picked from commit e5cd64f)
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: Pull request #23624 updated

    • Start Time: 2021-01-21T18:41:44.887+0000
  • Duration: 44 min 15 sec

  • Commit: 1861631

Test stats 🧪

Test Results
Failed 0
Passed 5114
Skipped 580
Total 5694

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test Results
Failed 0
Passed 5114
Skipped 580
Total 5694

@kvch kvch merged commit 244686c into elastic:7.x Jan 21, 2021
@zube zube bot removed the [zube]: Done label Apr 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Team:Services (Deprecated) Label for the former Integrations-Services team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants