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

[Comprehensive Issue] Fix Out-Of-Memory Issue During Bulk File Reading and Upgrade Elasticsearch Version #870

Open
wtt40122 opened this issue Aug 14, 2024 · 0 comments

Comments

@wtt40122
Copy link
Collaborator

Description

  • Overview:
    The current system encounters an Out-Of-Memory (OOM) issue when processing bulk file reading with wildcard matching, and we plan to upgrade Elasticsearch (ES) to the latest stable version to improve performance and security.

  • Steps to Reproduce OOM Issue:

    1. Attempt to read a large number of files using wildcard pattern matching.
    2. Observe a sharp increase in system memory usage.
    3. After reaching the memory limit, the system throws an OOM error.
  • Elasticsearch Version Upgrade Requirement:

    • The current ES version has known performance and security issues.
    • An upgrade to the latest stable version is needed to take advantage of new features and security updates.
  • Expected Behavior:

    • The system should efficiently handle a large number of files without excessive memory consumption.
    • After upgrading, the ES version should maintain or improve performance while remaining compatible with existing data structures and queries.
  • Actual Behavior:

    • The system's memory usage sharply increases when handling a large number of files, leading to an OOM error.
    • [If an ES version upgrade has been attempted, describe the issues encountered during the upgrade process]

Milestones:

  • Resolve the OOM issue
  • Complete the Elasticsearch version upgrade
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

1 participant