Open sbhenderson opened 3 years ago
Finally, I would like to at least mention a coincidence with this issue. Recently, I had changed some logic to perform deletions of measurements in parallel allowing greater throughput considering that the API can either delete one measurement or all measurements. In addition, I'm not sure it should matter, but there are other interesting behavior as a result of this bug.
For example, by going to the dashboard and exploring, you can see that it does not believe there are any measurements in the given window
Seems reasonable, but if you select _field first, you can then see the measurements.
Could be entirely unrelated, but I thought it best to be forthcoming.
Thanks for the excellent writeup @sbhenderson! I was able to reproduce exactly this behavior locally running on macos using a build of 2.0.9
using your data, so the behavior doesn't seem to be specific to windows/docker/etc. It also repros on a recent dev build so it doesn't look like it was fixed between 2.0.9
& now. This will take some digging into I think.
@wbaker85 Please let me know if there's any additional information or details you need from me. I suspect that something I did caused the underlying store to get into this strange state, so I cannot advise if investigation should be on this "post-facto" store or if I should prepare a repro of getting it into this state. If you cannot find an obvious answer by the data itself, I may be able to produce a full replication from zero state which would hopefully elucidate the matter.
I got a similar issue using influx 2.1 via docker on my raspberry.
I delete points with the python sdk like this:
start = datetime.fromisoformat(start_timestamp) - timedelta(weeks=2)
stop = datetime.fromisoformat(stop_timestamp) + timedelta(seconds=9)
try:
client.delete_api().delete(start, stop, "", bucket=bucket_iot, org=org)
client.close()
I log into that db every 10secs and send data from it every 60secs, after which I delete everything in it. I use influx to buffer messages when the network connection drops. After longer disconnects random parts of the db won't get deleted after a successful send. The wonky part is: newer points still get deleted every 60secs. It's nearly like the older points are delete protected. I have to manually delete the whole bucket to get rid of them. The number of points affected is looking random as well. No error message from inxludb. Every 60 sec that script will try to delete the affected points again with no success.
I'm really interested in the outcome of this. @sbhenderson did you make any progress?
Does not delete in 2.6.1
Hi there,
we are using the OCI image influxdb:2.7
, and have been tripped by the same flaw that deleting data using the HTTP API apparently does not work.
We are using HTTPie to submit the delete request like this:
http POST "http://localhost:8086/api/v2/delete?org=example&bucket=testdrive" "Authorization:Token token" start="1877-09-21T00:12:43.145224194Z" stop="2162-04-11T23:47:16.854775806Z"
With kind regards, Andreas.
We need to revise our previous statement: Deleting data like outlined above, or alternatively using influx delete
, works well, but data is still included when running influxd inspect export-lp
. This is probably not related to this issue, so we will create a separate one.
Setup
Running Docker image influxdb:latest linux/amd64 version via Docker Desktop and Docker-compose on Windows 10 with WSL2 backend
Reported version info:
Relevant docker-compose:
I have attached the files being used by InfluxDB. influxdb_files.zip
Username is user, password is password. Token that should be available is:
Influx CLI config creation:
Issue Replication
Using Influx CLI (version Influx CLI 2.1.1 (git: 535183b) build_date: 2021-09-22T18:32:23Z):
Response via CLI was empty. Debug logs from InfluxDB show:
Result
I would expect the data to be indiscriminately deleted in the specified date range. However, running a query
returns data within the specified range as seen below.
Comments
I wanted to point out that this is extremely bizarre. I insert data into InfluxDB and have no problem clearing it out in most cases. This is the first time I'm running into behavior where it is simply not possible to delete the data even without a predicate. I was hoping for some sort of error message or log indicating the problem, but there's simply nothing from what I can see.
Please let me know how else I can help or provide more information. Thank you for your time.