Mixed Index (ElasticSearch) Backpressure Ignored?
I understand that JG views writes to mixed indices as a "best effort" and documents(https://docs.janusgraph.org/operations/recovery/#transaction-failure) that failures in transactions with regards to mixed indices are left to a separate periodic clean up process after enabling JG's WAL:
But I wanted to inquire if 429 Too Many Requests could be omitted from this.
If the primary persistence into the storage backend succeeds but secondary persistence into the indexing backends or the logging system fail, the transaction is still considered to be successful because the storage backend is the authoritative source of the graph.
...
In addition, a separate process must be setup that reads the log to identify partially failed transaction and repair any inconsistencies caused.
....
But I wanted to inquire if 429 Too Many Requests could be omitted from this.
