Change cluster commands handling from ClusterConnectionManager to component (#348)

Artur Hefczyc opened 1 decade ago

Right now, the current implementation causes cluster commands to be executed within ClucsterConnectionManager threads, even though they are processed within a component context. If there is any blocking, IO, DB in the processing this may impact ClusterConnectionManager functioning and cause clustering problems.

A new way to handle data must be implemented so the cluster commands are processed within component thread pool.

Related
- Remove interface: XMPPPresenceUpdateProcessorIfc (#254) Closed

Activities

Artur Hefczyc commented 1 decade ago

I think you already started work on this, so I am assigning this task to you. Please talk to Andrzej as it seems to me he had some thoughts and suggestions on this as well.
Artur Hefczyc commented 9 years ago

Yes, we can postpone it for next version.
Wojciech Kapcia (Tigase) batch edited 2 years ago
Name Previous Value Current Value
Iterations
empty
Candidate for next major release
Login to comment

Name	Previous Value	Current Value
Iterations	empty	Candidate for next major release

Type	Task
Priority	Blocker
Assignee	Wojciech Kapcia (Tigase)
RedmineID	2066
Version	Candidate for next major release

Iterations

Candidate for next major release Open

Issue Votes (0)

Watchers (2)

Reference

tigase/_server/server-core#348