[Gluster-devel] Check the possibility to incorporate DEBUG info permanently in build

ABHISHEK PALIWAL abhishpaliwal at gmail.com
Mon Oct 17 08:11:43 UTC 2016

Hi Vijay,

It is quite difficult to provide the exact instances but below are the two
mostly occurred cases.

1. Get duplicate peer entries in 'peer status' command
2. We lost sync between two boards due to gluster mount point is not
present at one of the board.


On Mon, Oct 17, 2016 at 6:40 AM, Vijay Bellur <vbellur at redhat.com> wrote:

> On 10/14/2016 04:30 AM, ABHISHEK PALIWAL wrote:
>> Hi Team,
>> As we are seeing many issues in gluster. And we are failing to address
>> most of the gluster issues due to lack of information for fault analysis.
>> And for the many issue unfortunately with the initial gluster logs we
>> get a very limited information which is not at all possible to find the
>> root cause/conclude the issue.
>> Every time enabling the LOG_LEVEL to DEBUG is not feasible and few of
>> the cases are very rarely seen.
>> Hence, I request you to check if there is a possibility  to incorporate
>> the debug information in build or check if its possible to introduce a
>> new debug level that can always be activated.
>> Please come back on this!
> Abhishek - please provide specific instances of the nature of logs that
> could have helped you better. The query posted by you is very broad based
> and such broad queries seldom helps us in achieving the desired outcome.
> Regards,
> Vijay


Abhishek Paliwal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.gluster.org/pipermail/gluster-devel/attachments/20161017/4cc5b849/attachment.html>

More information about the Gluster-devel mailing list