# Sensu classic vs Sensu go scalability

**URL:** <https://discourse.sensu.io/t/sensu-classic-vs-sensu-go-scalability/2438>\
**Category:** Sensu Go\
**Created:** [February 8, 2021, 4:37pm UTC](https://discourse.sensu.io/t/sensu-classic-vs-sensu-go-scalability/2438 "2021-02-08T16:37:19Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jspaleta](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.sensu.io/jspaleta/32/141_2.png) [@jspaleta](https://discourse.sensu.io/u/jspaleta)\
**Post date:** [February 8, 2021, 11:56pm UTC](https://discourse.sensu.io/t/sensu-classic-vs-sensu-go-scalability/2438/3 "2021-02-08T23:56:43Z")

</div>

Hello,  
with regard to the external etcd, it looks like you’ve hitting a deficiency in the wrapper script logic used in the docker image to deal with the init.

The script currently uses `SENSU_HOSTNAME` for the for the init wait loop, which is probably inappropriate for the external etcd service in your configuration. You’ll probably need a custom docker image until we can get this sorted out in the official images.

Here’s a post from earlier this month where I walk through how I make custom changes to the entrypoint. Hopeful this will get you unstuck for now.

> [@Error starting etcd: multiple discovery or boot strap flags set](https://discourse.sensu.io/t/error-starting-etcd-multiple-discovery-or-boot-strap-flags-set/2369/7):
>
> I think this is a deficiency in the script logic in the official docker images preventing the etcd service discovery options from working. It appears that existing logic always sets SENSU\_BACKEND\_ETCD\_INITIAL\_CLUSTER envvar. I think the mitigation for now is going to be custom docker image with updated script logic to fix the problem. I’d offer you an alternative script to try, but I’m not confident I’d get the changes correct. You probably know what you need to get the etcd discovery to work …

---

_[View the full topic](https://discourse.sensu.io/t/sensu-classic-vs-sensu-go-scalability/2438)._