Is that a good practice to query ES during a Restore process?

yes I get this trace: when trying to ask ES if there's an index exists inside it, i get 404 for trying to request something from my ES like it died for some reason...

19/09/15 16:17:57.194 [main] INFO i.s.c.AbstractJestClient: Setting server pool to a list of 1 servers: [http://docker.local:9201]
19/09/15 16:17:57.194 [main] INFO i.s.c.JestClientFactory: Using multi thread/connection supporting pooling connection manager
19/09/15 16:17:57.241 [main] INFO i.s.c.JestClientFactory: Using default GSON instance
19/09/15 16:17:57.241 [main] INFO i.s.c.JestClientFactory: Node Discovery disabled...
19/09/15 16:17:57.241 [main] INFO i.s.c.JestClientFactory: Idle connection reaping disabled...
FlakyTestExtension: Iteration 3 failed.
org.junit.ComparisonFailure: expected:<[200]> but was:<[404]>
at sun.reflect.GeneratedConstructorAccessor48.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at com.logshero.gaia.demeter.itest.migrator.AccountsMigrationITest.assertEsSettings(AccountsMigrationITest.java:676)