[DOCU-8] Add clustering documentation Created: 23/Jan/05 Updated: 21/Jan/08 Resolved: 10/May/05 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Angus Mezick | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
I installed author on 8081 |
| Comments |
| Comment by Angus Mezick [ 23/Jan/05 ] |
|
Here is how I have configured the server.xml for my 3 instances. |
| Comment by Angus Mezick [ 23/Jan/05 ] |
|
Ok. I have this running now. I did three things between the last test and now. 1) changed the cache port. I still have some confusing with the documentation of the activation. I think all this stems from the fact that I am still trying to figure out how to get this system integrated with our dev/qa/production environment. Nothing gets on the dev server (that can have a bug) that doesn't first get cleanly built from the source to the qa server for testing. When we do the QA build, we also create production jars from that code so that we are sure what those jars contain and no label sillyness has taken place. |
| Comment by Boris Kraft [ 24/Jan/05 ] |
|
1) do I have to name them 0001, 0002, 0003, ....? No, name them anything you like. 2) How does this 0001 relate to all the other 0001's? doesn't 3) Can I activate only one server in a cluster (Testing vs production) Activation goes to all subscribers at once 4) Maybe this is the answer to #3: How would I set up a 3 stage deploy? Maybe I am just waiting for workflows. author -> test -> live First you activate from author to test, then from test to live. |
| Comment by Michael Aemisegger [ 24/Jan/05 ] |
|
A boolean property isActive might simplify administration. Instead of adding and deleting subscribers nodes you simply could change the isActive property. |
| Comment by Sameer Charles [ 24/Jan/05 ] |
|
I agree, will implement this soon |
| Comment by Sameer Charles [ 10/May/05 ] |
|
this is already implemented by fabrizio |