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
System info: [Include InfluxDB version, operating system name, and other relevant details]
InfluxDB 1.1 on Redhat Enterprise 6.8
Steps to reproduce:
sudo service influxdb stop # instance must be stopped to restore
su - influxdb
# Restore the meta store first
influxd restore -metadir /var/lib/influxdb/meta/ /path/to/backup
influxd restore -database db1 -datadir /var/lib/influxdb/data /path/to/backup
influxd restore -database db2 -datadir /var/lib/influxdb/data /path/to/backup
sudo chown -R influxdb:influxdb /var/lib/influxdb
sudo service influxdb start
Expected behavior: [What you expected to happen]
All databases restore as exist on the instance the backup was taken from. When doing a "SHOW SERIES" in a user database the _internal series should not appear.
Actual behavior: [What actually happened]
Series from _internal database appear in user database as well as in the _internal database
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had recent activity. Please reopen if this issue is still important to you. Thank you for your contributions.
Bug report
System info: [Include InfluxDB version, operating system name, and other relevant details]
InfluxDB 1.1 on Redhat Enterprise 6.8
Steps to reproduce:
Expected behavior: [What you expected to happen]
All databases restore as exist on the instance the backup was taken from. When doing a "SHOW SERIES" in a user database the _internal series should not appear.
Actual behavior: [What actually happened]
Series from _internal database appear in user database as well as in the _internal database
https://community.influxdata.com/t/-internal-series-appearing-in-user-database/672
The text was updated successfully, but these errors were encountered: