Thanks for your answer Greg. Unfortunately, the three monitor were working perfectly for at least 30 minutes after the upgrade. I don't know their memory usage at the time. What I did was : upgrade mons, upgrade osds, upgrade mds (single mds), upgrade fuse clients. I checked that everything was ok (health OK and data available). Then I started a rsync of around 7TB of data, mostly files between 100KB and 10MB, with 6TB of data already in CephFS. Currently the memory usage of my mons is around 110MB (on 1GB of memory and 1GB of swap). I'll keep an eye on this. On another matter (maybe I should start another thread), sometimes I have : health HEALTH_WARN mds0: Client wimi-recette-files-nginx:recette-files-rw failing to respond to cache pressure; mds0: Client wimi-prod-backupmanager:files-rw failing to respond to cache pressure And two minutes later : health HEALTH_OK Cephfs fuse clients only. But everything is working well, so I'm not so worried. Regards, -- Thomas Lemarchand Cloud Solutions SAS - Responsable des systèmes d'information On lun., 2014-11-03 at 09:57 -0800, Gregory Farnum wrote: > On Mon, Nov 3, 2014 at 4:40 AM, Thomas Lemarchand > <thomas.lemarchand@xxxxxxxxxxxxxxxxxx> wrote: > > Update : > > > > /var/log/kern.log.1:Oct 31 17:19:17 c-mon kernel: [17289149.746084] > > [21787] 0 21780 492110 185044 920 240143 0 > > ceph-mon > > /var/log/kern.log.1:Oct 31 17:19:17 c-mon kernel: [17289149.746115] > > [13136] 0 13136 52172 1753 59 0 0 > > ceph > > /var/log/kern.log.1:Oct 31 17:19:17 c-mon kernel: [17289149.746126] Out > > of memory: Kill process 21787 (ceph-mon) score 827 or sacrifice child > > /var/log/kern.log.1:Oct 31 17:19:17 c-mon kernel: [17289149.746262] > > Killed process 21787 (ceph-mon) total-vm:1968440kB, anon-rss:740176kB, > > file-rss:0kB > > > > OOM kill. > > I have 1GB memory on my mons, and 1GB swap. > > It's the only mon that crashed. Is there a change in memory requirement > > from Firefly ? > > There generally shouldn't be, but I don't think it's something we > monitored closely. > More likely your monitor was running near its memory limit already and > restarting all the OSDs (and servicing the resulting changes) pushed > it over the edge. > -Greg > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |