|
Andrzej Wójcik (Tigase) opened 9 years ago
|
|
|
I already implemented automatic addition of JIDs of EventBusComponent from other cluster nodes to affiliations with owner affiliation. %wojtek - what do you think about adding EventBusComponent to list of always active components? (active by default) |
|
Andrzej Wójcik wrote:
I think it's a good idea - I was under the impression (based on previous discussions) it was already included as one of the default components. |
|
|
I added EventBusComponent to list of components started by default |
|
|
With the latest fix from Bartek eventbus now works correctly and doesn't fall into infinite loop in cluster. I also works correctly while being loaded by default. |
|
Why is this changed back to QA? |
|
|
Because it turned out there is still some problems with duplicating events in cluster. |
|
|
commit:0c185d26f9aaab580fb79a6bf6dde67d2868f72d resolved the issue, hopefully for good this time. |
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| RedmineID |
3688
|
| Version |
tigase-server-7.1.0
|
| Spent time |
97h 30m
|
When using EventBusComponent in cluster mode there are a few issues:
component needs to be manually added (I think it should be added and started when we use Tigase XMPP Server in cluster mode)
component do not add component JID on other cluster nodes to affiliations so events from other cluster nodes are lost (dropped with error forbidden).