[bug #19306] No logging of node failures

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



URL:
  <http://savannah.nongnu.org/bugs/?19306>

                 Summary: No logging of node failures
                 Project: Gluster
            Submitted by: rjhuijsman
            Submitted on: Sunday 03/11/2007 at 21:55
                Category: GlusterFS
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
        Operating System: GNU/Linux

    _______________________________________________________

Details:

When a client-to-server connection fails, the error that is written to the
log by the client (when in NORMAL mode) does not specify which server it
failed to connect to. In DEBUG mode it is possible to trace which server it
failed to connect to (though it's very difficult), but most systems do not
run in DEBUG mode. There is however no other way of detecting and tracing
node failures.

It would be nice if node failures could be detected and traced more easily.
For example by specifying in the client logs which servers could not be
reached or stopped responding.




    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?19306>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/





[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux