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
I am attempting to side load ~2GB worth of backed up data from a temporary bucket to an existing bucket in my InfluxDB instance. To do this I am running the following flux query:
While running this query it sometimes appears the influx query CLI command hangs. During this I can see my instances memory usage and CPU usage drop (as if the query stopped, the influx instance usually maxes a single core and uses >8Gi of memory during this time) and I find this entry in the logs:
ts=2023-01-20T16:44:26.130913Z lvl=warn msg="internal error not returned to client" log_id=0fTme62G000
handler=error_logger error="context canceled"
Any ideas on how to make this restore process more reliable (and possibly faster)?
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
influx backup ~2GiB worth of data from a single bucket
influx restore into a temp bucket
Attempt to use Flux to sideload points into an existing bucket with data in it.
Expected behavior:
Sideloading to complete.
Actual behavior:
Indefinite hang.
Environment info:
System info: Linux 5.4.0-1098-azure x86_64 - Azure AKS, Standard_E4as_v4 node
Yep, using the stop parameter to create smaller chunks in sequence has been our workaround. I can't say we've investigated the resulting state of the bucket, I'll report back.
The bigger problem for us is that the HTTP response is never sent and the client appears to hang, so our scripts spin forever before timing out. Do you have any methods of debugging why that might be the case?
I am attempting to side load ~2GB worth of backed up data from a temporary bucket to an existing bucket in my InfluxDB instance. To do this I am running the following flux query:
While running this query it sometimes appears the
influx query
CLI command hangs. During this I can see my instances memory usage and CPU usage drop (as if the query stopped, the influx instance usually maxes a single core and uses >8Gi of memory during this time) and I find this entry in the logs:Any ideas on how to make this restore process more reliable (and possibly faster)?
Steps to reproduce:
List the minimal actions needed to reproduce the behavior.
influx backup
~2GiB worth of data from a single bucketinflux restore
into a temp bucketExpected behavior:
Sideloading to complete.
Actual behavior:
Indefinite hang.
Environment info:
Linux 5.4.0-1098-azure x86_64
- Azure AKS, Standard_E4as_v4 nodeInfluxDB v2.6.0 (git: 24a2b621ea) build_date: 2022-12-15T18:47:00Z
Config:
The text was updated successfully, but these errors were encountered: