# How to run conf file in two different machines/nodes? **URL:** \ **Category:** Logstash\ **Created:** [September 12, 2019, 6:36am UTC](https://discuss.elastic.co/t/how-to-run-conf-file-in-two-different-machines-nodes/199179 "2019-09-12T06:36:05Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![rkhapre](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rkhapre/32/48333_2.png) [@rkhapre](https://discuss.elastic.co/u/rkhapre)\ **Post date:** [September 12, 2019, 6:36am UTC](https://discuss.elastic.co/t/how-to-run-conf-file-in-two-different-machines-nodes/199179/1 "2019-09-12T06:36:05Z")
Hi All I have two conf file confile1.conf and confile2.conf The confile1.conf is sitting on Machine 1 The confile2.conf is sitting on Machine 2 Now i want to operate everything from Machine 1 From Machine 1 , i am able to run the "confile1.conf" as a service How can i run the "confile2.conf" from Machine 1 itself. ? I checked the docs, we have feature of node, but how both the nodes can communicate each other. **`--node.name NAME`** How to use this i am not sure. My end goal is to run the "confile2.conf" from machine 1. This i want to do because the volume of records is huge and it consumes lot of processing power.So i need one machine to run my conf file for various nodes. ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 14, 2019, 10:34am UTC](https://discuss.elastic.co/t/how-to-run-conf-file-in-two-different-machines-nodes/199179/2 "2019-09-14T10:34:23Z")
Logstash does not cluster so you need to move the config file over to the machine where you want to run it. ---
**Author:** ![rkhapre](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rkhapre/32/48333_2.png) [@rkhapre](https://discuss.elastic.co/u/rkhapre)\ **Post date:** [September 15, 2019, 2:52am UTC](https://discuss.elastic.co/t/how-to-run-conf-file-in-two-different-machines-nodes/199179/3 "2019-09-15T02:52:05Z")
Hi @Christian_Dahlqvist thanks for your response. I see in the yml file we have --node.name NAME --http.host HTTP\_HOST --http.port HTTP\_PORT I will keep the config file "confile2.conf" in machine 1 and run the command as usual but in my yml file i am trying to give value like this --node.name machine2\_node --http.host machine2\_host --http.port 7001 now basically i am running the conf file in machine1, and actually it will utilize the ressource of machine2, is this not possible? I feel this is something possible by looking the yml file. Currently i stuck with not able to bind the remote host, that is IP address of machine2 in yml file. Any idea on this This is more like a running a conf file from another machine, i just want to bind the host name, i think then it will work Thanks ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 15, 2019, 6:18am UTC](https://discuss.elastic.co/t/how-to-run-conf-file-in-two-different-machines-nodes/199179/4 "2019-09-15T06:18:11Z")
Logstash does not work in a clustered mode so that is not possible. The closest thing is probably [centralized pipeline management](https://www.elastic.co/guide/en/logstash/current/logstash-centralized-pipeline-management.html) where pipelines are managed through Kibana and Elasticsearch. ---
**Author:** ![rkhapre](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rkhapre/32/48333_2.png) [@rkhapre](https://discuss.elastic.co/u/rkhapre)\ **Post date:** [September 15, 2019, 1:49pm UTC](https://discuss.elastic.co/t/how-to-run-conf-file-in-two-different-machines-nodes/199179/5 "2019-09-15T13:49:13Z")
do we have any other solution to reach there.... ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 15, 2019, 2:19pm UTC](https://discuss.elastic.co/t/how-to-run-conf-file-in-two-different-machines-nodes/199179/6 "2019-09-15T14:19:14Z")
Why can you not copy the files onto the appropriate hosts? ---
**Author:** ![rkhapre](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rkhapre/32/48333_2.png) [@rkhapre](https://discuss.elastic.co/u/rkhapre)\ **Post date:** [September 15, 2019, 2:23pm UTC](https://discuss.elastic.co/t/how-to-run-conf-file-in-two-different-machines-nodes/199179/7 "2019-09-15T14:23:36Z")
like this i need to run lot of conf files in different machines, also i need to change the filters by date every week. So i want to manage everything centrally May be i will have to use some server level programming language to generate conf file from central machine to the remote machine I was thinking it will work like ES ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [September 15, 2019, 3:22pm UTC](https://discuss.elastic.co/t/how-to-run-conf-file-in-two-different-machines-nodes/199179/8 "2019-09-15T15:22:17Z")
If you have a large number of config files you could manage and deploy them using a orchestration tool, e.g. Ansible. > [@rkhapre](#): > > I was thinking it will work like ES It does not, but another option might be to have a look at ingest node pipelines and do the processing in Elasticsearch. Whether this is possible or not depends a lot on what input and output plugins you use. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 13, 2019, 3:22pm UTC](https://discuss.elastic.co/t/how-to-run-conf-file-in-two-different-machines-nodes/199179/9 "2019-10-13T15:22:18Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.