Question: How can this case happen for the 1PBE case when there is only one
user thread using the sqlite instance ?
Another relevant question is why/when do you observe this now ?
The test case or test setup must be special somehow.
With only one thread this case should be impossible.
It suggest heap correuption could be the cause.
Some years ago we did see problems although not exactly this kind, in
conjunction with
repeated failovers, where the new PBE managed to start while the old PBE (on
the other SC) was
still executing (slow to terminate). But the distributes file level protection
uses file system locking
and the symptoms should be different.
---
** [tickets:#1526] imm: exit the 1PBE when pbeBeginTrans sees db as locked**
**Status:** review
**Milestone:** 4.5.2
**Created:** Wed Oct 07, 2015 09:43 AM UTC by Neelakanta Reddy
**Last Updated:** Thu Oct 08, 2015 07:21 AM UTC
**Owner:** Neelakanta Reddy
when the disk is full the sqlite will return error.
Sep 18 13:42:02 SC-2 osafimmpbed: ER SQL statement ('COMMIT TRANSACTION')
failed because: disk I/O error
Sep 18 13:42:02 SC-2 osafimmnd[13067]: NO Invalid error reported implementer
'OpenSafImmPBE', Ccb 321 will be aborted
Sep 18 13:42:02 SC-2 osafimmnd[13067]: NO Ccb 321 ABORTED (TraceC)
Sep 18 13:42:02 SC-2 osafimmpbed: WA Failed to find CCB object for 141/321
Due to continoues CCB operations (even though disk is full) the 1PBE is seeing
the following mesages for more than 3 hours:
messages:Sep 18 17:58:46 SC-2 osafimmpbed: WA Sqlite db locked by other thread.
messages:Sep 18 17:58:46 SC-2 osafimmpbed: WA Sqlite db locked by other thread.
messages:Sep 18 17:58:47 SC-2 osafimmpbed: WA Sqlite db locked by other thread.
messages:Sep 18 17:58:47 SC-2 osafimmpbed: WA Sqlite db locked by other thread.
----
----
----
messages.7:Sep 18 14:22:22 SC-2 osafimmpbed: WA Sqlite db locked by other
thread.
messages.7:Sep 18 14:22:23 SC-2 osafimmpbed: WA Sqlite db locked by other
thread.
messages.7:Sep 18 14:22:23 SC-2 osafimmpbed: WA Sqlite db locked by other
thread.
messages.7:Sep 18 14:22:24 SC-2 osafimmpbed: WA Sqlite db locked by other thread
After freeing the space still the PBE is got struck in Sqlite db locked by
other thread.
This is preventing any further operations.
once the PBE is killed, the imm.db re-generated and the CCB operations are
applied.
Solution(1PBE):
For the 1PBE case, which is not multi threaded, if the sqlite db locked case is
reached abort the PBE and let the PBE be re-generated(instead of blocking the
PBE process).
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
