Vertx MN is loosing events in publish/subscribe tests

reTHINK-project / dev-msg-node-vertx

Apache License 2.0

0 stars 2 forks source link

Vertx MN is loosing events in publish/subscribe tests #52

Open sdruesedow opened 7 years ago

sdruesedow commented 7 years ago

The MN tests in performance-publish.spec.js fail in approx. 90% of the test-runs, because not all subscribed listeners receive an event notification.

If the number of listeners is reduced down to 10 it seems to work reliable. For listener numbers from 20 up to 200 nearly all tests fail with variying numbers of lost events (between 1-of-20 to 9-of-200). In former tests for D6.3 this was still working well in Vertx.

sdruesedow commented 7 years ago

I'm documenting the situation for D6.4 as it is

emmelmann-fokus commented 7 years ago

Hi,

From WP-6 perspective, I am fine with this as we have to only assess the work in WP-6 and provide feedback to the technical WPs.

But from an overall perspective, this will raise issues in the final review, i.e.,

that a technical issue, that features having had worked before, were not working any more,
that this situation had been reported to the technical WPs, and
that a solution was not found within a month, nor was there a documented follow-up discussion.

Just my two cents.

pchainho commented 7 years ago

@luistduarte , is looking on this one.

sdruesedow commented 7 years ago

I noticed that the develop branch was updated with a version that uses a newer Vertx release. I repeated the tests based on this but there is no difference. Still not all subscribers receive an event.

sdruesedow commented 7 years ago

The current situation is now documented in D6.4.

sdruesedow commented 7 years ago

argumentations:

due to new requirements since D6.3 several new sub-systems have been added, e.g. persistency, policy engine, redundancy etc.
the complexity of the MN has been markedly raised due to that
this error happens under stress tests, relevance for daily use in the testbeds is relatively low