Skip to content

Locator use disk free and status to determine object placement #4

New issue
New issue
Closed
Closed
Locator use disk free and status to determine object placement#4
Assignees
ctengel
Milestone
Basic

Description

@ctengel
ctengel
opened on Aug 17, 2025

Depends on some of #2

Cache cluster status

On write:

  1. Check cache from Locator performance enhancement on GET #1 , 409 if conflict
  2. Instead of random, do weighted random check based on cached available disk space
  3. Do a double check of selected node for space
  4. Double check all nodes for object
  5. Go ahead and respond

Activity

  1. ctengel commented on Aug 17, 2025

    @ctengel
    ctengel
    on Aug 17, 2025
    OwnerAuthor

    % free * amount free

  2. ctengel
    added this to the Basic milestone on Aug 18, 2025

  3. ctengel commented on Aug 18, 2025

    @ctengel
    ctengel
    on Aug 18, 2025
    OwnerAuthor

    Also ensure that bucket actually exists on target server; otherwise client will get a 404

  4. ctengel
    self-assigned this
    on Aug 24, 2025
  5. ctengel
    pinned this issue on Aug 24, 2025
  6. ctengel
    added a commit that references this issue on Aug 24, 2025

    Added /health endpoint to object server

    52f630b

  7. ctengel commented on Aug 24, 2025

    @ctengel
    ctengel
    on Aug 24, 2025
    OwnerAuthor

    Also check read-only status

  8. ctengel commented on Aug 24, 2025

    @ctengel
    ctengel
    on Aug 24, 2025
    OwnerAuthor

    5xx if no space

  9. ctengel
    closed this as completedin a820da2on Aug 25, 2025
  10. ctengel
    unpinned this issue on Aug 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions