Yes, rolling restart should be fine for 1.0 -> 1.0.1 We can add "unclean.leader.election.enable=true" to server.properties. This requires broker restart to take effect.
On Tue, Apr 24, 2018 at 12:02 PM, Mika Linnanoja <mika.linnan...@rovio.com> wrote: > Morning, group. > > On Mon, Apr 23, 2018 at 11:19 AM, Mika Linnanoja <mika.linnan...@rovio.com > > > wrote > > > > If nothing else, let this incident of ours serve as a warning to do > > exactly as the book (upgrade guide) says, not sort of wing it. Thanks for > > fast replies, lively mailing list! > > > > Mika > > > > So yeah last night further 94 partitions became unavailable in the cluster. > Fix was the same as before. > > Was checking the logs, looks like at least one broker ran out of heap > memory, i.e. the 1.0 bug. > > We shall be upgrading to 1.0.1. That doesn't seem to have any special > instructions, so 1.0 -> 1.0.1 completely safe, no log/message/binary > version magics required, right? > > Btw is there any way to force `unclean.leader.election.enable=true` on all > brokers globally, like in a config file default? Setting it up via the > add-config for all of our ~200 topics is a bit annoying. How about new > topics? > > chrs, > Mika > > -- > *Mika Linnanoja* > Senior Cloud Engineer > Games Technology > Rovio Entertainment Corp > Keilaranta 7, FIN - 02150 Espoo, Finland > Mobile: + 358 (0)50 487 3211 > mika.linnan...@rovio.com > www.rovio.com > > *This message and its attachments may contain confidential information and > is intended solely for the attention and use of the named addressee(s). If > you are not the intended recipient and / or you have received this message > in error, please contact the sender immediately and delete all material you > have received in this message. You are hereby notified that any use of the > information, which you have received in error in whatsoever form, is > strictly prohibited. Thank you for your co-operation.* >
