On Wed, Feb 11, 2015 at 5:30 AM, Dennis Kramer (DT) wrote:
> After setting the debug level to 2, I can see:
> 2015-02-11 13:36:31.922262 7f0b38294700 2 mds.0.cache check_memory_usage
> total 58516068, rss 57508660, heap 32676, malloc 1227560 mmap 0, baseline
> 39848, buffers 0, max 67108864, 8656
On Wed, 11 Feb 2015, Wido den Hollander wrote:
On 11-02-15 12:57, Dennis Kramer (DT) wrote:
On Fri, 7 Nov 2014, Gregory Farnum wrote:
Did you upgrade your clients along with the MDS? This warning
indicates the
MDS asked the clients to boot some inboxes out of cache and they have
taken
too lon
On 11-02-15 12:57, Dennis Kramer (DT) wrote:
> On Fri, 7 Nov 2014, Gregory Farnum wrote:
>
>> Did you upgrade your clients along with the MDS? This warning
>> indicates the
>> MDS asked the clients to boot some inboxes out of cache and they have
>> taken
>> too long to do so.
>> It might also just
On Fri, 7 Nov 2014, Gregory Farnum wrote:
Did you upgrade your clients along with the MDS? This warning indicates the
MDS asked the clients to boot some inboxes out of cache and they have taken
too long to do so.
It might also just mean that you're actively using more inodes at any given
time th
Did you upgrade your clients along with the MDS? This warning indicates the
MDS asked the clients to boot some inboxes out of cache and they have taken
too long to do so.
It might also just mean that you're actively using more inodes at any given
time than your MDS is configured to keep in memory.