Issue Details (XML | Word | Printable)

Key: SCAR-1
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Sergio Bossa
Reporter: Sergio Bossa
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Scarlet - Clustering for Jira

During global re-indexing, users on other cluster nodes are able to access the Jira web interface.

Created: 01/Mar/08 05:26 AM   Updated: 04/Mar/08 04:16 AM
Component/s: Cluster
Affects Version/s: 1.0RC1
Fix Version/s: 1.0RC2

Time Tracking:
Not Specified

Issue Links:
Reference
 

Labels:


 Description  « Hide
In single-instance mode, during re-indexing users aren't able to access Jira web interface: they are redirected to a page saying that Jira is currently blocked because of a re-indexing.
With Scarlet, users are still able to access Jira on a different cluster node from the one that is actually executing the re-index operation, corrupting so the re-index operation by creating/modifying issues.
This is clearly wrong, so during re-indexing users on all nodes must be always redirected to the "blocking" page.

 All   Comments   Work Log   Change History   FishEye   Crucible   Builds      Sort Order: Ascending order - Click to sort in descending order
Sergio Bossa added a comment - 03/Mar/08 03:20 AM
The best option would be to share the collection of events into the JohnsonEventContainer, but it's currently impossible due to this Terracotta limitation: https://jira.terracotta.org/jira/browse/CDV-608.

Sergio Bossa added a comment - 04/Mar/08 03:49 AM
Sharing JohnsonEventContainer events (see SCAR-2) would solve this issue.

Sergio Bossa added a comment - 04/Mar/08 04:16 AM
Resolved as a consequence of the SCAR-2 fix.