From: Jean-Daniel TISSOT <Jean-Daniel.Tissot@univ-fcomte.fr>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] ProxmoxVE6.3/CEPH Octopus 15.2.6 was Python problem with upgrade to proxmoxVE6.3/ CEPH Nautilus 14.2.15
Date: Fri, 27 Nov 2020 18:12:11 +0100 [thread overview]
Message-ID: <327d2503-b906-5e09-d81a-20fd2f64a638@univ-fcomte.fr> (raw)
In-Reply-To: <843b2e4d-ff82-bbdd-6906-8e6ff90bcc96@odiso.com>
Sorry to steal the thread.
In fact before upgrading to Octopus, I don't remember any warning.
I upgrade Proxmox an follow the wiki to upgrade CEPH. All things seam
working (I don't test HA by migrate a VM work perfectly.
I have just the warning on pool rdb (1 pools have too many placement
groups Pool rbd has 128 placement groups, should have 32)
Le 27/11/2020 à 17:59, alexandre derumier a écrit :
> >>1 pools have too many placement groups Pool rbd has 128 placement
> groups, should have 32
> >>
> >>I don't find any way to reduce placement groups tu 32
> >>
> >>Any help welcome.
>
> you can't reduce PG on nautilus, only since octopus. (and ceph is
> able to do it automataaly with new pg autoscaler)
>
> I think it's a warning introduced in last nautilus update.
>
> If I remember, they are an option to disable this warning, (but I
> don't remember it)
>
>
> On 27/11/2020 17:29, Jean-Daniel TISSOT wrote:
>> Hi,
>>
>> I have another problem
>>
>> root@dmz-pve1:~ # ceph health HEALTH_WARN 1 pools have too many
>> placement groups root@dmz-pve1:~ # pveceph pool ls
>> ┌───────────────────────┬──────┬──────────┬────────┬───────────────────┬─────────────────┬──────────────────────┬──────────────┐
>> │ Name │ Size │ Min Size │ PG Num │ PG Autoscale
>> Mode │ Crush Rule Name │ %-Used │ Used │
>> ╞═══════════════════════╪══════╪══════════╪════════╪═══════════════════╪═════════════════╪══════════════════════╪══════════════╡
>> │ device_health_metrics │ 3 │ 2 │ 1 │
>> on │ replicated_rule │ 4.19273845864154e-07 │ 4534827
>> │
>> ├───────────────────────┼──────┼──────────┼────────┼───────────────────┼─────────────────┼──────────────────────┼──────────────┤
>> │ rbd │ 3 │ 2 │ 128 │
>> warn │ replicated_rule │ 0.0116069903597236 │
>> 127014329075 │
>> └───────────────────────┴──────┴──────────┴────────┴───────────────────┴─────────────────┴──────────────────────┴──────────────┘
>>
>>
>> In the GUI :
>>
>> 1 pools have too many placement groups Pool rbd has 128 placement
>> groups, should have 32
>>
>> I don't find any way to reduce placement groups tu 32
>>
>> Any help welcome.
>>
>> Best regards,
>>
>> Le 27/11/2020 à 14:07, Lindsay Mathieson a écrit :
>>> On 27/11/2020 9:47 pm, Jean-Luc Oms wrote:
>>>> Upgrading to last Proxmox VE / Ceph nautilus from the last 6.2 proxmox
>>>> VE seems to introduce a python 2/3 version problem, dashboard healt
>>>> stops working.
>>>
>>> Was just about to report that :)
>>>
>>>
>>> Same here.
>>>
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
--
Bien cordialement,
Jean-Daniel Tissot - IE CNRS http://chrono-environnement.univ-fcomte.fr
UMR 6249 - Laboratoire Chrono-environnement UMR CNRS-UFC
Université de Franche-Comté, 16 route de Gray, 25030 Besançon Cedex, FRANCE
Jean-Daniel.Tissot@univ-fcomte.fr tel:+33 3 81 666 440
Alabama, Mississippi, Minnesota, South Carolina, Oregon... not so sweet home
Black Panther Party, renaît de tes cendres et reviens les aider
https://www.youtube.com/watch?v=ZvilFSMVHTs
next prev parent reply other threads:[~2020-11-27 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 11:47 [PVE-User] " Jean-Luc Oms
2020-11-27 13:07 ` Lindsay Mathieson
[not found] ` <47b5a337-b2ca-ce6d-37c5-e904db8d6e03@univ-fcomte.fr>
2020-11-27 16:59 ` alexandre derumier
2020-11-27 17:12 ` Jean-Daniel TISSOT [this message]
2020-11-27 21:17 ` Lindsay Mathieson
2020-11-27 17:06 ` Marco M. Gabriel
2020-11-27 17:08 ` alexandre derumier
2020-11-27 17:18 ` Jean-Daniel TISSOT
2020-11-27 15:15 ` Jean-Luc Oms
2020-11-27 16:45 ` Marco M. Gabriel
2020-11-28 3:23 ` Lindsay Mathieson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=327d2503-b906-5e09-d81a-20fd2f64a638@univ-fcomte.fr \
--to=jean-daniel.tissot@univ-fcomte.fr \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.