[Enterprise] Restore doesn't work if meta node auth is enabled

,
1

I’m trying to restore single retention policy into Enterprise cluster from backup, which was made on InfluxDB OSS with -portable option, version 1.5.2 is used in both OSS and Enterprise. Authentication is enabled in cluster and I confirm it works with both basic and JWT (internal-shared-secret option is set):

influxd-ctl -auth-type jwt -secret mysecret show

Data Nodes
==========
ID TCP Address Version
4 data-01:8088 1.5.2-c1.5.2
5 data-02:8088 1.5.2-c1.5.2
6 data-03:8088 1.5.2-c1.5.2
7 data-04:8088 1.5.2-c1.5.2

Meta Nodes
==========
TCP Address Version
meta-01:8091 1.5.2-c1.5.2
meta-02:8091 1.5.2-c1.5.2
meta-03:8091 1.5.2-c1.5.2

Though when I try to restore a backup, I get "unable to parse authentication credentials" error, which basically means influxd-ctl command doesn’t see any credentials at all:

influxd-ctl -auth-type jwt -secret mysecret restore -db app_metrics -rp app_metrics_rp 20180531/app_metrics/by_rp/app_metrics_rp/

Using backup directory: 20180531/app_metrics/by_rp/app_metrics_rp/
Using meta backup: 20180531T070534Z.meta
Restoring meta data… 2018-05-31T16:52:24.893759Z info Meta client error {“log_id”: “08Pmg0i0002”, “error”: “unable to parse authentication credentials”, “retrying_after”: “20.000ms”}
2018-05-31T16:52:24.914387Z info Meta client error {“log_id”: “08Pmg0i0002”, “error”: “unable to parse authentication credentials”, “retrying_after”: “400.000ms”}
2018-05-31T16:52:25.315518Z info Meta client error {“log_id”: “08Pmg0i0002”, “error”: “unable to parse authentication credentials”, “retrying_after”: “3333.333ms”}
2018-05-31T16:52:28.649719Z info Meta client error {“log_id”: “08Pmg0i0002”, “error”: “unable to parse authentication credentials”, “retrying_after”: “3333.333ms”}
2018-05-31T16:52:31.983813Z info Meta client error {“log_id”: “08Pmg0i0002”, “error”: “unable to parse authentication credentials”, “retrying_after”: “3333.333ms”}
Error.
restore: operation timed out with error: unable to parse authentication credentials

I was able to make restore work only with disabled meta nodes authentication. When it’s enabled, all the commands work as expected (including backup), but not restore.

Is this a bug?

2

Hi Siarhei–

Sorry this was missed until now. Did you figure this out? When you set the meta node internal-shared-secret, did you also set the data nodes’ meta.met-internal-shared-secret? I am looking to get this tested with restore soon.

Steve

3

Hi Steve,

Yes, figured it out. It’s a bug and it was fixed in version 1.5.4.

4

Thanks – as you said, I found out that your restore issue was fixed. I’ll be updating the docs with corrections and more insights on internal-shared-secret and intra-node communication.