# Reindex whitelist on the fly?

**URL:** <https://discuss.elastic.co/t/reindex-whitelist-on-the-fly/198470>\
**Category:** Elasticsearch\
**Created:** [September 6, 2019, 6:44pm UTC](https://discuss.elastic.co/t/reindex-whitelist-on-the-fly/198470 "2019-09-06T18:44:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![linkerc](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@linkerc](https://discuss.elastic.co/u/linkerc)\
**Post date:** [September 6, 2019, 6:44pm UTC](https://discuss.elastic.co/t/reindex-whitelist-on-the-fly/198470/1 "2019-09-06T18:44:13Z")

</div>

I know there was a closed thread discussing this already, but I still want to make a feature request for this.

> [@Possibility of modifying "reindex.remote.whitelist" via API call?](https://discuss.elastic.co/t/possibility-of-modifying-reindex-remote-whitelist-via-api-call/74693):
>
> Would it be possible to have the "reindex.remote.whitelist" setting modifiable via the HTTP API instead of having to specify it in the elasticsearch.yml config? I realize this setting currently most likely requires a cluster restart, although it would be great if this could simply be implemented as a settings lookup each time the "/\_reindex" endpoint is called. If you agree and this is a reasonable request, I'd gladly create an issue in the github project to have the included in a future versi…

The problem with having it in yml file is it'll stay with the new cluster forever unless I restart the new cluster once reindex is done. This is very intrusive. I don't really know when I need to reindex from the old cluster. We have tons of data and I'm not going to reindex unless I really need it. And the requirement might change.  
Having whitelist in yml is not really offering security either. It's a configuration on the initiator.  
Anybody can create a new cluster with the whitelist and reindex that way.

I really need an easy way to get data from old cluster and that's it. The need to restart cluster is too intrusive. Both clusters are within the same network. Is security really a concern here?  
Please reconsider allowing reindex on the fly. Maybe change security to something like setting up a temporary secret in the old cluster and the new cluster needs this secret for reindex, etc.  
Owner of old cluster can always remove the secret afterward. I believe this provides a much better security (which I don't believe is a concern in the first place), and also allow reindex on the fly.  
Restarting cluster is not a good solution in general. If I have access to the new cluster, I can always query the old cluster.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 4, 2019, 6:44pm UTC](https://discuss.elastic.co/t/reindex-whitelist-on-the-fly/198470/2 "2019-10-04T18:44:16Z")

</div>

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