You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Spark structured streaming API supports rate limit by maxFilesPerTrigger. Currently, Flint user can configure this when create index like example here: . However, there is no guidance on this value or similar support like maxBytesPerTrigger in Delta or Iceberg table.
Without such limit, Flint index like covering index may cause heavy ingestion pressure on OpenSearch cluster until back pressure mechanism triggered (end up with connect exception, socket timeout exception, circuit break or cluster write block exception).
What solution would you like?
Options:
Guide user recommended maxFilesPerTrigger value
Implement similar maxBytesPerTrigger in File source (maybe helpful to provide ALTER index statement so user can change this)
What alternatives have you considered?
Implement adaptive rate limiter on OpenSearch write latency
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
Spark structured streaming API supports rate limit by
maxFilesPerTrigger
. Currently, Flint user can configure this when create index like example here: . However, there is no guidance on this value or similar support likemaxBytesPerTrigger
in Delta or Iceberg table.Without such limit, Flint index like covering index may cause heavy ingestion pressure on OpenSearch cluster until back pressure mechanism triggered (end up with connect exception, socket timeout exception, circuit break or cluster write block exception).
What solution would you like?
Options:
What alternatives have you considered?
Implement adaptive rate limiter on OpenSearch write latency
The text was updated successfully, but these errors were encountered: