On Fri, 3 May 2019 at 16:07, Amar Tumballi Suryanarayan
wrote:
>
>
> On Fri, May 3, 2019 at 3:17 PM Atin Mukherjee wrote:
>
>>
>>
>> On Fri, 3 May 2019 at 14:59, Xavi Hernandez wrote:
>>
>>> Hi Atin,
>>>
>>> On Fri, May 3, 2019 at 10:57 AM Atin Mukherjee
>>> wrote:
>>>
I'm bit puzzled on
On Fri, May 3, 2019 at 3:17 PM Atin Mukherjee wrote:
>
>
> On Fri, 3 May 2019 at 14:59, Xavi Hernandez wrote:
>
>> Hi Atin,
>>
>> On Fri, May 3, 2019 at 10:57 AM Atin Mukherjee
>> wrote:
>>
>>> I'm bit puzzled on the way coverity is reporting the open defects on GD1
>>> component. As you can
On Fri, 3 May 2019 at 14:59, Xavi Hernandez wrote:
> Hi Atin,
>
> On Fri, May 3, 2019 at 10:57 AM Atin Mukherjee
> wrote:
>
>> I'm bit puzzled on the way coverity is reporting the open defects on GD1
>> component. As you can see from [1], technically we have 6 open defects and
>> all of the
Hi Atin,
On Fri, May 3, 2019 at 10:57 AM Atin Mukherjee wrote:
> I'm bit puzzled on the way coverity is reporting the open defects on GD1
> component. As you can see from [1], technically we have 6 open defects and
> all of the rest are being marked as dismissed. We tried to put some
>
I'm bit puzzled on the way coverity is reporting the open defects on GD1
component. As you can see from [1], technically we have 6 open defects and
all of the rest are being marked as dismissed. We tried to put some
additional annotations in the code through [2] to see if coverity starts
feeling
On 30/04/19 6:59 PM, Strahil Nikolov wrote:
Hi,
I'm posting this again as it got bounced.
Keep in mind that corosync/pacemaker is hard for proper setup by new
admins/users.
I'm still trying to remediate the effects of poor configuration at work.
Also, storhaug is nice for hyperconverged
On 30/04/19 6:41 PM, Renaud Fortier wrote:
IMO, you should keep storhaug and maintain it. At the beginning, we
were with pacemaker and corosync. Then we move to storhaug with the
upgrade to gluster 4.1.x. Now you are talking about going back like it
was. Maybe it will be better with
