| Summary: | Allow write through commits on FailOverParticipant (load balancing) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Erwin Betschart <erwin> | ||||||
| Component: | cdo.core | Assignee: | Eike Stepper <stepper> | ||||||
| Status: | CLOSED FIXED | QA Contact: | Eike Stepper <stepper> | ||||||
| Severity: | enhancement | ||||||||
| Priority: | P3 | Keywords: | noteworthy | ||||||
| Version: | 4.0 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | Power to the People | ||||||||
| Attachments: |
|
||||||||
|
Description
Erwin Betschart
Created attachment 174716 [details]
Idea with a WriteThroughCommitContext
I'd prefer to use the remote session of the BACKUP's repository synchronizer directly to open a transaction on the MASTER. Please test if that suits your need and we can close this as WORKSFORME.
Please reopen if the approach in comment #1 is not adequate for you. Your proposal has two main drawbacks in our case: 1. On state change of the repository the remote session gets deactivated / activated. Therefore I would have to rebuild the data structure on state change. 2. The remote session does not cache the revisions. Created attachment 176102 [details]
Patch v2 - for future reference
This new feature must be explicitely enabled in CDOServerUtil.createFailoverParticipant(), see last parameter "allowBackupCommits".
Committed to HEAD Available in R20110608-1407 |