segment_allocator.cc:24] address_table_ map is growing too large: 4129 about dragonfly HOT 5 CLOSED

@Qubitium is there a reason you are not using a later version ? 1.19 for example? Could you also plz try using a later version and let me know if the issue still persists?

from dragonfly.

@kostasrim After correctly upgrading from 1.13.0 to 1.19.0 all previous warn/errors logs are gone after restart (save and reload).

from dragonfly.

The first few warnings are mimalloc. This is probably a warning that we are reaching a limit on the segment size (I will need to check further for why this is).

The last log is a hard crash and it should not happen. It means we violated something we shouldn't and df crashed. Again this is something I will need to debug.

Is there an easy way to reproduce this?

Also which version of dragonfly are you running on

from dragonfly.

Also which version of dragonfly are you running on

[EDIT: WRONG INFO] This is was upgrade log from 1.13.0 to 1.14.6

I simply restarted the instance which was still 1.13.0

from dragonfly.

@Qubitium Lit lit lit 🔥

from dragonfly.