Skip to main content

Troubleshooting Firestore Writer

This topic describes errors you may see when using Firestore Writer, and possible resolutions.

Exception

Resolutions

Authentication failure on connection

  • Verify the connection profile's Authentication Type matches the credentials provided.

  • For SCRAM, verify the username and password, and that the database user has the User role or higher.

  • For Service Account Key, verify the key file path is correct and readable by Striim, and that the service account has the roles/datastore.user role or higher.

  • For Application Default, verify Striim is running on a Google Compute Engine VM with the service account attached and the Cloud Platform access scope enabled.

Connection failure

  • Verify the Connection URL is the database's MongoDB-format URL, including the port (typically 443), for example mongodb://abc.asia-south1.firestore.goog:443.

  • Verify the Firestore database is an Enterprise edition database with MongoDB compatibility.

  • Verify the Firestore endpoint is reachable from the Striim server.

Aborted (112)

The database is overloaded or the operation conflicted with another operation. Firestore Writer retries automatically according to the Overload Retry Policy property. If the error persists, increase the retry interval or number of retries, or reduce the write rate by adjusting the Batch Policy. See Understand error codes > Aborted (112) in Google's documentation.

Writes fail because a target collection does not exist

Firestore Writer does not create collections automatically. Create the target collections in Firestore before starting the application.