| commit | 45878d4363cfd50d218ff53c8aa3502b9d073016 | |
| author | Martin Schwenke <martin@meltin.net> | |
| Thu, 13 Jun 2013 01:56:25 +0000 (13 11:56 +1000) | ||
| committer | Martin Schwenke <martin@meltin.net> | |
| Fri, 14 Jun 2013 05:15:06 +0000 (14 15:15 +1000) | ||
| tree | 747836e2101fabcc5c9ba6812d25e21f75d92b43 | treesnapshot (tar.gz zip) |
| parent | f408caea2ad46dab3f8f19b97eda8c8652bd5ff4 | commitdiff |
eventscripts: New configuration varable $CTDB_NFS_DUMP_STUCK_THREADS
If some nfsd threads are still alive after a shutdown during a restart
then this indicates the maximum number of threads for which a stack
trace should be dumped. This can be useful for trying to determine
why nfsd is stuck.
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit 2503245db10d567af708a04edd3a3b488c24f401)
If some nfsd threads are still alive after a shutdown during a restart
then this indicates the maximum number of threads for which a stack
trace should be dumped. This can be useful for trying to determine
why nfsd is stuck.
Signed-off-by: Martin Schwenke <martin@meltin.net>
(This used to be ctdb commit 2503245db10d567af708a04edd3a3b488c24f401)
| ctdb/config/ctdb.sysconfig | diffblobblamehistory | |
| ctdb/config/functions | diffblobblamehistory |