nsteinmetz
commented
4 years ago Weird thing I see in logs for the query :
FROM crntgitlab..diskwhy 2 points ?
Closed nsteinmetz closed 4 years ago
nsteinmetz
commented
4 years ago Weird thing I see in logs for the query :
FROM crntgitlab..diskwhy 2 points ?
nsteinmetz
commented
4 years ago Seems the autogen is missing
2.0.1, I can see:
FROM crntbackup.autogen.disk
or
FROM comptaonline.\"default\".disk
timhallinflux
commented
4 years ago queries like FROM crntgitlab..disk are syntactically correct. That says... use the default retention policy (RP) as opposed to typing it out. Similarly, the default RP can be leveraged for writes...if it is NOT specified by the writer (i.e. the writer only specifies the DB).
docmerlin
commented
4 years ago @nsteinmetz can you run from 2.0.2
influx v1 dbrp list --db=comptaonline --default=true
If that doesn't return anything can you please run for me:
influx v1 dbrp list --db=comptaonline
timhallinflux
commented
4 years ago Looks like the upgrade step did not create the appropriate DBRP mappings.
nsteinmetz
commented
4 years ago As seen on slack:
With a influxdb server running 2.0.1 version but using 2.0.2 binaries for command below, get all dbrp policies:
First, get your list of db with influx bucket list
for db in <list of db from above - limiting to 1.x db>; do
echo $db;
influx v1 dbrp list --db=<db> --default=true
done
ID Database Bucket ID Retention Policy Default Organization ID
06a59835c0505000 <db> default true
[...]You will notice that bucket id is null.
Delete the dbrp:
for id in <list of dbrp ids from above>; do echo ${id}; influx v1 dbrp delete --id=${id}; doneThen stop influxdb server with 2.0.1 and start server with 2.0.2 binaries.
From now, you can create new dbrp ; db and bucket-id used below are the ones from influx bucket list
influx v1 dbrp create --bucket-id=<bucket-id> --db=<db> --rp=autogen --default=trueIf you do again the command below, you will see a bucket id for each db.
for db in <list of db from above - limiting to 1.x db>; do
echo $db;
influx v1 dbrp list --db=<db> --default=true
doneFrom now, I no longer have panic messages.
To be noticed:
dbrp list and dbrp delete commands will only working using 2.0.2 binaries against a server using 2.0.1dbrp create commands will only working using 2.0.2 binaries against a server using 2.0.2Otherwise you will have this error as output ; I guess it's due to object constraints in the doc and the bucket id beeing null.
Error: Attempted to unmarshal error as JSON but failed: "unexpected end of JSON input":.
Thnaks @timhallinflux @docmerlin for your kind and prompt support !
docmerlin
commented
4 years ago OK, the problem with the empty buckets was fixed in 2.0.2.
docmerlin
commented
4 years ago The problem was the influxd upgrade command was making DBRPs with empty bucket IDs.
This was fixed in 2.0.2.
If you get caught with this problem https://github.com/influxdata/influxdb/issues/20121#issuecomment-731403423 Is how to get yourself in a better state.
As this appears to be resolved, I am closing this issue.
Steps to reproduce: List the minimal actions needed to reproduce the behavior.
Expected behavior:
InfluxDB 1.x endpoints should continue to work as expected
Actual behavior:
and for query:
Environment info:
Config: