On Mon, Apr 15, 2019 at 11:08 AM Pranith Kumar Karampuri <
pkara...@redhat.com> wrote:
>
>
> On Thu, Apr 11, 2019 at 2:59 PM Xavi Hernandez
> wrote:
>
>> On Wed, Apr 10, 2019 at 7:25 PM Xavi Hernandez
>> wrote:
>>
>>> On Wed, Apr 10, 2019 at 4:01 PM Atin Mukherjee
>>> wrote:
>>>
And now
On Thu, Apr 11, 2019 at 2:59 PM Xavi Hernandez wrote:
> On Wed, Apr 10, 2019 at 7:25 PM Xavi Hernandez
> wrote:
>
>> On Wed, Apr 10, 2019 at 4:01 PM Atin Mukherjee
>> wrote:
>>
>>> And now for last 15 days:
>>>
>>>
>>> https://fstat.gluster.org/summary?start_date=2019-03-25_date=2019-04-10
>>>
Ok, I got your point, thanks for responding!
cynthia
From: Raghavendra Gowdappa
Sent: Monday, April 15, 2019 4:36 PM
To: Zhou, Cynthia (NSB - CN/Hangzhou)
Cc: gluster-devel@gluster.org
Subject: Re: glusterd stuck for glusterfs with version 3.12.15
On Mon, Apr 15, 2019 at 12:52 PM Zhou,
On Mon, Apr 15, 2019 at 12:52 PM Zhou, Cynthia (NSB - CN/Hangzhou) <
cynthia.z...@nokia-sbell.com> wrote:
> Hi,
>
> The reason why I move event_handled to the end of socket_event_poll_in is
> because if event_handled is called before rpc_transport_pollin_destroy, it
> allowed another round of
Hi,
The reason why I move event_handled to the end of socket_event_poll_in is
because if event_handled is called before rpc_transport_pollin_destroy, it
allowed another round of event_dispatch_epoll_handler happen before
rpc_transport_pollin_destroy, in this way, when the latter poll in goes
