2021-08-12 11:39:56 -07:00
---
description: >-
2021-08-12 20:59:34 +00:00
This installation doc will help you start a OpenMetadata instances on your
production.
2021-08-12 11:39:56 -07:00
---
2021-08-12 20:59:34 +00:00
# Run in Production
2021-08-12 11:39:56 -07:00
2021-10-19 12:31:25 +00:00
Please refer to the previous section [Run Openmetadata ](run-openmetadata.md ) for configuring OpenMetadata.
2021-08-12 11:39:56 -07:00
{% hint style="info" %}
**Prerequisites**
2021-10-14 22:31:26 +00:00
* MySQL >= 8.x
* ElasticSearch >= 7.x
2021-08-12 11:39:56 -07:00
* Airflow or other schedulers to run Ingestion Connectors
{% endhint %}
## Start OpenMetadata
2021-08-12 20:59:34 +00:00
OpenMetadata release ships with `./bin/openmetadata` init.d style script.
2021-08-12 11:39:56 -07:00
2021-10-14 22:31:26 +00:00
```
2021-10-20 03:02:00 +00:00
cd openmetdata-0.5.0
2021-08-12 11:39:56 -07:00
./bin/openmetdata start
```
2021-10-14 22:31:26 +00:00
We recommend configuring serviced to monitor the OpenMetadata command to restart in case of any failures.
2021-08-12 11:39:56 -07:00
## Running with a load balancer
2021-08-12 21:14:42 +00:00
One or more OpenMetadata instances can be put behind a load balancer for reverse proxying, in that case, an appropriate OpenMetdata URL must be mentioned in the load balancer's configuration file.
2021-08-12 11:39:56 -07:00
2021-08-12 20:59:34 +00:00
For example, in case Apache mod proxy the VirtualHost tag in the configuration file should be edited out with the following
2021-08-12 11:39:56 -07:00
2021-10-14 22:31:26 +00:00
```
2021-08-12 11:39:56 -07:00
< VirtualHost * :80 >
< Proxy balancer: / / mycluster >
BalancerMember http://127.0.0.1:8585 <!-- First OpenMetadata server -->
BalancerMember http://127.0.0.2:8686 <!-- Second OpenMetadata server -->
< / Proxy >
ProxyPreserveHost On
ProxyPass / balancer://mycluster/
ProxyPassReverse / balancer://mycluster/
< / VirtualHost >
2021-08-12 20:59:34 +00:00
```