Comments on: MySQL Docker Containers: Quick Async Replication Test Setup

By: Arunjith Aravindan

Arunjith Aravindan — Thu, 09 Jan 2020 17:13:21 +0000

In reply to carehart. Changed the text for better clearly, all set! Thanks.

By: carehart

carehart — Wed, 08 Jan 2020 13:39:50 +0000

In reply to Arunjith A. Ok, so it's not really that it "it IS not suitable to production", but rather that it "may not be". I gather you won't be changing it, but I offer this for the sake of other readers, barring any additional clarification from you or others. (Your concluding point about testing is understood and doesn't counter what I'd said). Finally, you still haven't explained your last point, that this "will not be supported for production use by Docker". Can you please elaborate? I'm sorry if it seems I'm "looking a gift horse in the mouth", in pressing these points. But they seem reasonable ones, given how the article kind of turned on a dime with that last sentence. It's just not clear that things are as firm as you said, without more clarification.

By: Arunjith A

Arunjith A — Wed, 08 Jan 2020 04:56:18 +0000

In reply to Charlie Arehart. Hi Charlie, Thanks for the response. The aforesaid details are the basics to get a test instance running quickly and easily including the async replication and not for a production setup. It is clearly a technical point, it does not match a typical production install and you need to test it well before any other use.

By: Jojo Thomas

Jojo Thomas — Mon, 30 Dec 2019 17:43:00 +0000

In reply to Jojo Thomas. Got it: ❯ brew install mysql-client ❯ brew link mysql-client ❯ echo 'export PATH="/usr/local/opt/mysql-client/bin:$PATH"' >> ~/.zshrc ❯ . ~/.zshrc

By: Jojo Thomas

Jojo Thomas — Mon, 30 Dec 2019 13:01:48 +0000

Can you also advice on the steps to get a local mysql install on my MacBook Pro

—-
❯ mysql -h127.0.0.1 -uroot -p -P3308 -e “show master status;”
zsh: command not found: mysql

By: Charlie Arehart

Charlie Arehart — Sat, 28 Dec 2019 14:09:57 +0000

Thanks for that, Arunjith. I’m sure many will appreciate the succinct steps.

That said, I think many others would benefit if you could elaborate on the last sentence. First, what makes this configuration “not suitable for production”? Is that a licensing point, or some other legal or technical point?

If you may be implying merely that this one image (without orchestration) might not stand up to load, that could still “work” as production for some implementations, who without docker may also be only one instance. Heck, just adding replication will be a step up for some.

Of course, I appreciate the real value such a docker-based configuration adds for development and testing. I just really seek your clarification on what does make this NOT suitable for production.

Finally, still more curious, you add that it would “not be supported for production use by Docker”? That too is a point I’d think many would benefit hearing elaborated. Thanks.