Abstract: A node failure detector for use in a distributed database that is accessed through a plurality of interconnected transactional and archival nodes. Each node is selected as an informer node that tests communications with each other node. Each informer node generates a list of suspicious nodes that is resident in one node designated as a leader node. The leader node analyzes the data from all of the informer nodes to designate each node that should be designated for removal with appropriate failover procedures.

Abstract: A node failure detector for use in a distributed database that is accessed through a plurality of interconnected transactional and archival nodes. Each node is selected as an informer node that tests communications with each other node. Each informer node generates a list of suspicious nodes that is resident in one node designated as a leader node. The leader node analyzes the data from all of the informer nodes to designate each node that should be designated for removal with appropriate failover procedures.

Abstract: A node failure detector for use in a distributed database that is accessed through a plurality of interconnected transactional and archival nodes. Each node is selected as an informer node that tests communications with each other node. Each informer node generates a list of suspicious nodes that is resident in one node designated as a leader node. The leader node analyzes the data from all of the informer nodes to designate each node that should be designated for removal with appropriate failover procedures.

Abstract: The method determines whether a particular process is currently executing or not executing. The method embeds process identification information and a process name in a process pathname that binds to a socket. The method creates a socket and binds to the socket a process name and associated process identifier if that process is currently executing. A status file may store the socket pathnames of those processes currently executing. A socket pathname appears in the status file if a corresponding process is executing, but does not appear in the status file if the process is not executing. To determine if a particular process is currently executing, the method tests the status file to determine if the status file contains a match for the socket pathname associated with the particular process under test. The presence of a match for the socket pathname in the status file indicates that the particular process associated therewith is currently executing.

Abstract: The method determines whether a particular process is currently executing or not executing. The method embeds process identification information and a process name in a process pathname that binds to a socket. The method creates a socket and binds to the socket a process name and associated process identifier if that process is currently executing. A status file may store the socket pathnames of those processes currently executing. A socket pathname appears in the status file if a corresponding process is executing, but does not appear in the status file if the process is not executing. To determine if a particular process is currently executing, the method tests the status file to determine if the status file contains a match for the socket pathname associated with the particular process under test. The presence of a match for the socket pathname in the status file indicates that the particular process associated therewith is currently executing.