cluding attachments, is
intended only for the person(s) or entity to which it is addressed and may
contain confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. I
| | | | | | + 0.50% bool
> >>>>>>> std::has_facet >>>>>>> std::char_traits > > >(std::locale const&)
> >>>>>>>| | | | | | | | + 0.40% bool
> >>>>>>> std::has_facet >
>>>>| | | | | + 1.80%
> PyFormatter::open_array_section(char const*)
> >>>>>>> | | | | | | + 1.60% PyList_New
> >>>>>>>| | | | | | | + 1.60%
> _PyObject
| | | | | | + 0.20%
>>>>>>>> std::num_get>>>>>>> std::char_traits > > const& std::use_facet>>>>>>> std::istreambuf_iterator > >
>>>>>>>> >(std::locale const&)
>>>>>>>>
> std::ios_base::_M_init()
>>>>>>>| | | | | | + 0.50%
>>>>>>> tcmalloc::ThreadCache::FetchFromCentralCache(unsigned int, int)
>>>>>>>| | | | | | + 0.40%
>>>>>>>
| | | | | + 0.60% dictresize
> >>>>>| | | | | | | | + 0.30%
> >>>>> PyString_FromString
> >>>>>| | | | | | | | + 0.20% PyDict_SetItem
> >>>>> | |
| | | | + 1.60% collect
>>>>>| | | | | | | + 0.80% dict_traverse
>>>>>| | | | | | | + 0.10%
>>>>> subtype_traverse
>>>>>| | |
> std::ostreambuf_iterator >
> >> > >::do_put(std::ostreambuf_iterator >,
> >> > std::ios_base&, char, long) const
> >> >| | | | | | + 0.30%
> >> > std::basic_ostream >&
> >> > std::__ostream_insert
> >> > >(std::basic_ostream >&
| | | + 0.10%
>> > PyFormatter::open_object_section(char const*)
>> >| | | + 2.70%
>> > PyFormatter::finish_pending_streams()
>> >| | | | + 1.00%
>> > std::_Li
_wait@@GLIBC_2.2.5
> >| | | + 1.10%
> __new_sem_wait_slow.constprop.0
> >| | | + 1.10%
> do_futex_wait.constprop.1
> >| | + 2.90% frame_dealloc
> > | |
vileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
destroy any copies of this information.
We'd let to verify it the network ping time monitoring feature in
14.2.5 is attributing to this problem.
It'd be great if someone could try
https://tracker.ceph.com/issues/43364#note-3 and let us know.
Thanks,
Neha
On Thu, Dec 19, 2019 at 8:48 AM Mark Nelson wrote:
>
> If you can get a
If you can get a wallclock profiler on the mgr process we might be able
to figure out specifics of what's taking so much time (ie processing
pg_summary or something else). Assuming you have gdb with the python
bindings and the ceph debug packages installed, if you (are anyone)
could try
We're also seeing unusually high mgr CPU usage on some setups, the only
thing they have in common seem to > 300 OSDs.
Threads using the CPU are "mgr-fin" and and "ms_dispatch"
Paul
--
Paul Emmerich
Looking for help with your Ceph cluster? Contact us at https://croit.io
croit GmbH
On Dec 18, 2019, at 1:48 PM, e...@lapsus.org wrote:
>
> That sounds very similar to what I described there:
> https://tracker.ceph.com/issues/43364
I would agree that they're quite similar if not the same thing! Now that you
mention it I see the thread is named mgr-fin in 'top -H' as well. I
Hey,
That sounds very similar to what I described there:
https://tracker.ceph.com/issues/43364
Best,
Eric
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
16 matches
Mail list logo
