|
Artur Hefczyc opened 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. |
||||||
|
|
Yes, we can postpone it for next version. |
||||||
|
Wojciech Kapcia (Tigase) batch edited 11 months ago
|
| Type |
Task
|
| Priority |
Blocker
|
| Assignee | |
| RedmineID |
2066
|
| Version |
Candidate for next major release
|
Iterations
Issue Votes (0)
Watchers (2)
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.