Jeremy,
When I applied the recommended configuration (especially: "command_timeout:
600") to allow sufficient time to merge some of the really large keys that became an
issue earlier this year, I noticed a significant memory spike (I think SKS was actively
merging one of those large keys at th
So I have all my nodes synced with around 5445343 keys after disabling
all external peering and letting the 4 nodes get in sync. I then added a
single external peer and then my SKS DB process goes into a funky state
once it begins peering externally. I installed strace and when I ran a
'strace -q -
Has anyone else been monitoring the memory pattern for SKS and
noticed an exceedingly high memory usage pattern? My secondary nodes are
generally showing < 11% of the instance memory used but for some reason
I'm seeing my primary node using nearly 100% of memory, and CPU for that
matter. My pri
