Hi Jonathan, Thanks for the inputs. Actually we are not storing data in
/tmp/directory :-) .
Sure I'll update heap settings as advised.
--Senthil
On Wed, 4 Sep, 2019, 6:24 PM Jonathan Santilli,
wrote:
> Hello Senthil,
>
> I would recommend to not have the data in /tmp/data.
> Also as a
Thanks Karolis.
On Wed, 4 Sep, 2019, 5:57 PM Karolis Pocius,
wrote:
> I had the same issue which was solved by increasing max_map_count
> https://stackoverflow.com/a/43675621
>
>
> On Wed, Sep 4, 2019 at 2:59 PM SenthilKumar K
> wrote:
>
> > Hello Experts , We have deployed 10 node kafka
Thanks
On Wed, 4 Sep, 2019, 6:24 PM Jonathan Santilli,
wrote:
> Hello Senthil,
>
> I would recommend to not have the data in /tmp/data.
> Also as a recommendation, set to equal values the -Xmx and -Xms parameters.
>
>
> Cheers!
> --
> Jonathan
>
>
>
>
> On Wed, Sep 4, 2019 at 1:27 PM Karolis
HI All,
We have 3 nodes kafka 2.2 cluster and going to add 3 new nodes with 2.3
version. The goal is to kill the old servers as we are moving to a better
way of node provisioning. To make it happen we need to move all partitions
from old nodes to new ones. The question is: can we do it while new
Hello Senthil,
I would recommend to not have the data in /tmp/data.
Also as a recommendation, set to equal values the -Xmx and -Xms parameters.
Cheers!
--
Jonathan
On Wed, Sep 4, 2019 at 1:27 PM Karolis Pocius
wrote:
> I had the same issue which was solved by increasing max_map_count
>
I had the same issue which was solved by increasing max_map_count
https://stackoverflow.com/a/43675621
On Wed, Sep 4, 2019 at 2:59 PM SenthilKumar K
wrote:
> Hello Experts , We have deployed 10 node kafka cluster in production.
> Recently two of the nodes went down due to network problem and
Hello Experts , We have deployed 10 node kafka cluster in production.
Recently two of the nodes went down due to network problem and we brought
it up after 24 hours. At the time of bootstrapping the kafka service on
the failed nodes , we have seen the below error & broker failed to come up.
