FusionAuth
    • Home
    • Categories
    • Recent
    • Popular
    • Pricing
    • Contact us
    • Docs
    • Login

    "A request to the search index has failed" - OpenSearch(AWS)

    Scheduled Pinned Locked Moved Unsolved
    Q&A
    2
    2
    5
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      tim.clark
      last edited by

      Hello,

      We're experiencing a known compatibility issue between FusionAuth and AWS-managed OpenSearch related to Point-in-Time (PIT) operations during bulk delete operations.

      Issue Summary:

      Error: SearchEngineRequestFailedException with message "A request to the search index has failed"
      
      Log Pattern: Unable to create point in time on index [fusionauth_user]
      
      Frequency: Occurs during nightly dedupe operations
      
      Impact: Prevents deletion of users via the bulk delete API
      
      Status Code: 503
      

      Environment:

      FusionAuth Version: 1.55.1
      
      Search Engine: AWS-managed OpenSearch
      
      Infrastructure: AWS
      

      Background:
      We understand this is a known issue with PIT operations against AWS OpenSearch, as documented in FusionAuth community discussions. We've reviewed release notes through version 1.62.1 and haven't found a specific fix for this issue.

      Questions:

      • Is there a timeline for a fix to address AWS OpenSearch PIT compatibility?
      • Are there alternative deletion methods that bypass PIT operations we could use as a workaround?

      We'd appreciate any guidance on addressing this issue or information about planned fixes.

      Thank you for your assistance.

      mark.robustelliM 1 Reply Last reply Reply Quote 0
      • mark.robustelliM
        mark.robustelli @tim.clark
        last edited by

        @tim-clark Can you please point to the community discussion where this comes up? I could not find it in the issues.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post