RAID10 for kafka cluster

[Mich Talebzadeh <mi...@gmail.com>]

is RAID 10 (mirrored and striped) essential for kafka cluster with three
nodes in DEV as I have been told that disk failures can shutdown the whole
kafka clusters? this is a non-prod environment

thanks

Dr Mich Talebzadeh



LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
<https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>*



http://talebzadehmich.wordpress.com


*Disclaimer:* Use it at your own risk. Any and all responsibility for any
loss, damage or destruction of data or any other property which may arise
from relying on this email's technical content is explicitly disclaimed.
The author will in no case be liable for any monetary damages arising from
such loss, damage or destruction.

Re: RAID10 for kafka cluster

[Gerrit Jansen van Vuuren <ge...@gmail.com>]

in my opinion for production I would run with raid10, its true that kafka
has durability as to shutdown of brokers, there are exceptions or hiccups,
if you want to avoid tons of movement between brokers and connection errors
on the clients (which may or not depending on how loaded your cluster is
cause issues) due to disk failures, raid10 is the way to go, you'll have a
much more stable cluster all round.

For development it depends, I run a vagrant instance locally on my laptop
for development :/




On Tue, Mar 7, 2017 at 9:52 AM, Mich Talebzadeh <mi...@gmail.com>
wrote:

> is RAID 10 (mirrored and striped) essential for kafka cluster with three
> nodes in DEV as I have been told that disk failures can shutdown the whole
> kafka clusters? this is a non-prod environment
>
> thanks
>
> Dr Mich Talebzadeh
>
>
>
> LinkedIn * https://www.linkedin.com/profile/view?id=
> AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
> <https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCd
> OABUrV8Pw>*
>
>
>
> http://talebzadehmich.wordpress.com
>
>
> *Disclaimer:* Use it at your own risk. Any and all responsibility for any
> loss, damage or destruction of data or any other property which may arise
> from relying on this email's technical content is explicitly disclaimed.
> The author will in no case be liable for any monetary damages arising from
> such loss, damage or destruction.
>