13:39:24 <Smithx10> Anyone have LX core dump with redis?
14:02:00 <Smithx10> got some core dumps :(
14:13:56 <Smithx10> @bahamat  @danmcd  https://us-east-storage.solutions.iqvia.com/bruce_dev/public/core.redis-server.825763  
15:19:36 <danmcd> @teutat3s may have some useful information about this.
15:21:29 <teutat3s> Smithx10 (LIBERA-IRC):  Yeah this came up before on the mailing list:  and on their GH issue tracker 
15:21:31 <teutat3s> https://smartdatacenter.topicbox.com/groups/sdc-discuss/Te49b8ca17c162420-M75685540777f2f32e43cde32
15:21:37 <teutat3s> https://github.com/redis/redis/issues/6176#issuecomment-668861069
15:22:25 <teutat3s> I didn't look into it enough to be able to say if it's the same kind of crash though.
15:22:59 <teutat3s> My approach to avoid redis crashing in LX was to use redis in a native zone instead
15:27:25 <jperkin> nbjoerg: hg stuck again
16:00:25 * nbjoerg uses a bigger hammer
16:05:38 <Smithx10> haha teutat3s  
16:06:03 <Smithx10> probably whats gonna happen,  but it looks like they set a mem limit,  do you know what they may have done?
16:06:56 <Smithx10> I don't think I was at the limit tho,  let me double check
16:08:13 <teutat3s> Smithx10 (LIBERA-IRC): It sounds like they set maxmemory in the redis config
16:08:14 <teutat3s> https://redis.io/docs/management/config/#configuring-redis-as-a-cache
16:08:47 <Smithx10> Nice,  Ill give that a go and watch the mem usage*
17:40:56 <Smithx10> teutat3s:   congrats on the hire :) 
18:19:15 <teutat3s> Smithx10 (LIBERA-IRC): thank you! (: