|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 3365 | minor | always | 03-02-09 13:42 | 07-21-11 11:55 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | urgent | OS Version: | |||
| Status: | closed | Product Version: | 4.0.0 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.21 | ||
|
|
|||||
| Summary: | 0003365: Allow load balancer to only serve old messages | ||||
| Description: |
(rep by Cameron Stokes) I've been following the Resin 4.0 news coming out and had a question regarding the dynamic clustering capabilities of the new version. One thing we've been missing since moving to Resin was the ability to enable/disable instances in the cluster from receiving new sessions but allowing them to continue to service existing sessions. We would also like to be able to start an instance in this mode and be able to hit it with a particular URL, session ID, or some other manner but still not allow public traffic to hit the instance. Will the new features in Resin 4.0 support this? |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||