Can't load in an index / snapshot into3 node ES cluster

Any thoughts on this one

I have a cluster split across 3 machines

When I start the cluster I see an error but eventually the cluster goes GREEN with all existing snapshot / indices STARTED

[2019-06-04T11:51:21,156][WARN ][o.e.c.s.ClusterService ] [] failed to notify ClusterStateListener
java.lang.NullPointerException: null
at org.elasticsearch.common.settings.IndexScopedSettings.( ~[elasticsearch-5.1.1.jar:5.1.1]

Then later I attempt to load a s3 snapshot where XXXXXX is the snapshot I'm trying to load and is what you'd call the master node

[2019-06-05T10:44:26,029][WARN ][c.f.s.c.PrivilegesEvaluator] XXXXXXX does not exist in cluster metadata
[2019-06-05T10:44:26,029][WARN ][c.f.s.c.PrivilegesEvaluator] XXXXXX does not exist in cluster metadata
[2019-06-05T10:44:26,029][WARN ][c.f.s.c.PrivilegesEvaluator] XXXXXX does not exist in cluster metadata
[2019-06-05T10:44:26,029][WARN ][c.f.s.c.PrivilegesEvaluator] XXXXXXXX does not exist in cluster metadata
[2019-06-05T10:44:55,757][WARN ][c.f.s.h.SearchGuardHttpServerTransport] [] Someone (/ speaks http plaintext instead of ssl, will close the channel
[2019-06-05T10:44:56,982][INFO ][o.e.r.RepositoriesService] [] update repository [XXXXXXX]
[2019-06-05T10:44:57,971][WARN ][r.suppressed ] path: /_snapshot/XXXXXXXX, params: {repository=XXXXXXXX}
org.elasticsearch.repositories.RepositoryVerificationException: [XXXXXXXX] path [XXXXXXXX] is not accessible on master node
at org.elasticsearch.repositories.blobstore.BlobStoreRepository.startVerification( ~[elasticsearch-5.1.1.jar:5.1.1]
at org.elasticsearch.repositories.RepositoriesService.verifyRepository( [elasticsearch-5.1.1.jar:5.1.1]
at org.elasticsearch.repositories.RepositoriesService$VerifyingRegisterRepositoryListener.onResponse( [elasticsearch-5.1.1.jar:5.1.1]

What I really don't understand is that of course XXXXXX doesn't exist - I'm asking you to load it just now - confused :frowning:

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.