xact steps k8s follows manually to see
what exactly forces an active watcher after reboot.
Thank you
Serguei
On 2017-12-21, 5:49 AM, "Ilya Dryomov" wrote:
On Wed, Dec 20, 2017 at 6:20 PM, Serguei Bezverkhi (sbezverk)
wrote:
> It took 30 minutes for the Watcher to ti
On 2017-12-20, 11:17 AM, "Jason Dillaman" wrote:
On Wed, Dec 20, 2017 at 11:01 AM, Serguei Bezverkhi (sbezverk)
wrote:
> Hello Jason, thank you for your prompt reply.
>
> My setup is very simple, I have 1 Centos 7.4 VM which is a storage node
whic
It took 30 minutes for the Watcher to time out after ungraceful restart. Is
there a way limit it to something a bit more reasonable? Like 1-3 minutes?
On 2017-12-20, 12:01 PM, "Serguei Bezverkhi (sbezverk)"
wrote:
Ok, here is what I found out. If I gracefully kill a pod then wa
.
Thank you
Serguei
On 2017-12-20, 11:32 AM, "Serguei Bezverkhi (sbezverk)"
wrote:
On 2017-12-20, 11:17 AM, "Jason Dillaman" wrote:
On Wed, Dec 20, 2017 at 11:01 AM, Serguei Bezverkhi (sbezverk)
wrote:
> Hello Jason, thank yo
our settings to pick the deprecated v1 format?
[1]
https://github.com/kubernetes/kubernetes/pull/56651#issuecomment-352850884
[2] https://github.com/kubernetes/kubernetes/pull/51574
On Wed, Dec 20, 2017 at 10:24 AM, Serguei Bezverkhi (sbezverk)
wrote:
> Hello,
Hello,
I hit an issue with latest Luminous when a Watcher is not timing out when the
image is not mapped. It seems something similar was reported in 2016, here is
the link:
http://lists.ceph.com/pipermail/ceph-users-ceph.com/2016-August/012140.html
Has it been fixed? Appreciate some help here.
T
