Description. This function is used to retrieve the cluster log severity filter currently in force.
The parameters and return type of this function changed significantly between MySQL 5.1.13 and 5.1.14. The changes are detailed in the Signature, Parameters, and Return Type sections that follow.
These changes were done in order to make this function thread-safe. The pre-5.1.14 version is still supported for backward compatibility, but you should protect it with a mutex if you intend to call it from more than one thread.
Signature. As of MySQL 5.1.14:
int ndb_mgm_get_clusterlog_severity_filter ( NdbMgmHandle
handle, struct ndb_mgm_severity*
severity, unsigned int
In MySQL 5.1.13 and earlier, this function took only a single parameter, as shown here:
const unsigned int* ndb_mgm_get_clusterlog_severity_filter ( NdbMgmHandle
Parameters. This function added two new parameters in MySQL 5.1.14.
All MySQL 5.1 releases:
Additionally, in MySQL 5.1.14 and later:
severity of seven
elements, each of which is an
ndb_mgm_severity structure, where
each element contains
1 if a
severity indicator is enabled and
if not. A severity level is stored at position
for example the error level is stored at position
first element (position
NDB_MGM_EVENT_SEVERITY_ON) in the
vector signals whether the cluster log is disabled or
size of the vector
Return value. This function's return type changed beginning with MySQL 5.1.14.
MySQL 5.1.13 and earlier: A
severity filter, which is a vector
containing 7 elements. Each element equals
1 if the corresponding severity
indicator is enabled, and
0 if it is
not. A severity level is stored at position
example, the “error” level is stored at
The first element in the vector
whether the cluster log is enabled or disabled.
MySQL 5.1.14 and later: The number of
returned severities, or
-1 in the event
of an error.