| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
... also bumped version number
|
| |
|
|
|
|
|
|
| |
- bugfix: solved potential (temporary) stall of messages when the queue was
almost empty and few new data added (caused testbench to sometimes hang!)
- fixed some race condition in testbench
- added more elaborate diagnostics to parts of the testbench
- solved a potential race inside the queue engine
|
| |
|
|
| |
The enhanced testbench now runs without failures, again
|
| |
|
|
|
| |
also changed DA queue mode in that the regular workers now run
concurrently.
|
| |
|
|
|
| |
... and now make check fails again, we have obviously found some new
bugs thanks to the additional cases
|
| |
|
|
|
|
|
|
|
|
|
| |
... and also improved the test suite. There is a design issue in the
v3 queue engine that manifested to some serious problems with the new
processing mode. However, in v3 shutdown may take eternally if a queue
runs in DA mode, is configured to preserve data AND the action fails and
retries immediately. There is no cure available for v3, it would
require doing much of the work we have done on the new engine. The window
of exposure, as one might guess from the description, is very small. That
is probably the reason why we have not seen it in practice.
|
| |
|
|
|
|
| |
... needed to split the old single counter into two. I wouldn't bet that
I made some mistakes while doing so, but at least some ad-hoc tests plus
the testbench do no longer indicate errors.
|
| | |
|
|
|
The problem is that the rsyslog engine writes messages too quickly, so
that the queue never enters DA mode. We still have some look contemption.
One possible solution (hopefully) is to finally move the parser code out
of imtcp and onto the next thread. Need to address these issues first, then
come back to the test case.
|
