On Sat, May 19, 2018 at 5:01 PM, Uwe Sauter wrote:
> The mistery is that these blocked requests occur numerously when at
> least
> one of the 6 servers is booted with kernel 4.15.17, if all are running
> 4.13.16 the number of blocked requests is infrequent and low.
S
Am 19.05.2018 um 01:45 schrieb Brad Hubbard:
On Thu, May 17, 2018 at 6:06 PM, Uwe Sauter wrote:
Brad,
thanks for the bug report. This is exactly the problem I am having (log-wise).
You don't give any indication what version you are running but see
https://tracker.ceph.com/issues/23205
t
On Thu, May 17, 2018 at 6:06 PM, Uwe Sauter wrote:
> Brad,
>
> thanks for the bug report. This is exactly the problem I am having (log-wise).
You don't give any indication what version you are running but see
https://tracker.ceph.com/issues/23205
>>>
>>>
>>> the cluster is an Proxmo
Brad,
thanks for the bug report. This is exactly the problem I am having (log-wise).
>>>
>>> You don't give any indication what version you are running but see
>>> https://tracker.ceph.com/issues/23205
>>
>>
>> the cluster is an Proxmox installation which is based on an Ubuntu kernel.
>>
>> # ceph
On Thu, May 17, 2018 at 4:16 PM, Uwe Sauter wrote:
> Hi,
>
>>> I'm currently chewing on an issue regarding "slow requests are blocked".
>>> I'd like to identify the OSD that is causing those events
>>> once the cluster is back to HEALTH_OK (as I have no monitoring yet that
>>> would get this info
Hi,
I'm currently chewing on an issue regarding "slow requests are blocked". I'd
like to identify the OSD that is causing those events
once the cluster is back to HEALTH_OK (as I have no monitoring yet that would
get this info in realtime).
Collecting this information could help identify agin
On Wed, May 16, 2018 at 6:16 PM, Uwe Sauter wrote:
> Hi folks,
>
> I'm currently chewing on an issue regarding "slow requests are blocked". I'd
> like to identify the OSD that is causing those events
> once the cluster is back to HEALTH_OK (as I have no monitoring yet that would
> get this info
On 05/16/2018 07:18 AM, Uwe Sauter wrote:
> Hi Mohamad,
>
>>
>> I think this is what you're looking for:
>>
>> $> ceph daemon osd.X dump_historic_slow_ops
>>
>> which gives you recent slow operations, as opposed to
>>
>> $> ceph daemon osd.X dump_blocked_ops
>>
>> which returns current blocked ope
Hi Mohamad,
>> I'm currently chewing on an issue regarding "slow requests are blocked". I'd
>> like to identify the OSD that is causing those events
>> once the cluster is back to HEALTH_OK (as I have no monitoring yet that
>> would get this info in realtime).
>>
>> Collecting this information
Hi,
On 05/16/2018 04:16 AM, Uwe Sauter wrote:
> Hi folks,
>
> I'm currently chewing on an issue regarding "slow requests are blocked". I'd
> like to identify the OSD that is causing those events
> once the cluster is back to HEALTH_OK (as I have no monitoring yet that would
> get this info in re
Hi folks,
I'm currently chewing on an issue regarding "slow requests are blocked". I'd
like to identify the OSD that is causing those events
once the cluster is back to HEALTH_OK (as I have no monitoring yet that would
get this info in realtime).
Collecting this information could help identify
11 matches
Mail list logo