Anonymous | Login | Signup for a new account | 12-17-2024 12:00 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0001259 | [Resin] | minor | always | 07-19-06 09:06 | 05-24-07 09:50 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 3.1.2 | Product Version | |||||
Product Build | |||||||||
Summary | 0001259: disable selected ports for Resin | ||||||||
Description |
(rep by Bryan Choate) Is there a ways to take a node out of the cluster definition, such that it?s still accessible through its own http port but not via the LoadBalanceServlet running on a front end instance? Basically, we have a cluster with multiple front-end instances and multiple back-end instances, and when starting nodes we?d like to be able to test the functionality on each node ourselves, and then flip a switch to release it to the world, so to speak. Is there a built-in method of doing this? |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed. 25 unique queries executed. |