Skip to content

Avoid using _recovery_source when logsdb is enabled and source mode is synthetic. #116726

Description

@martijnvg

This issue is about relying on synthetic source for peer recovery and car and not storing recovery source. The latter has the potential to improve index throughput for logsdb by around ~10%.

Activity

  1. elasticsearchmachine commented on Nov 13, 2024

    @elasticsearchmachine
    Collaborator

    Pinging @elastic/es-storage-engine (Team:StorageEngine)

  2. self-assigned this
    on Nov 13, 2024
  3. added
    :Distributed/RecoveryAnything around constructing a new shard, either from a local or a remote source.
    on Nov 13, 2024
  4. elasticsearchmachine commented on Nov 13, 2024

    @elasticsearchmachine
    Collaborator

    Pinging @elastic/es-distributed-indexing (Team:Distributed Indexing)

  5. added a commit that references this issue on Mar 5, 2025
    26de534
  6. added 2 commits that reference this issue on Mar 5, 2025
    cc2a023
    ea29afd
  7. added a commit that references this issue on Mar 11, 2025
    f3082a2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions