0006296: dynamic elastic servers should respect allow-non-reserved-ip configuration

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0006296

[Resin]

minor

always

11-20-19 00:19

12-13-19 16:56

Reporter

nam

View Status

public

Assigned To

ferg

Priority

normal

Resolution

no change required

Status

closed

Product Version

4.0.63

Summary

0006296: dynamic elastic servers should respect allow-non-reserved-ip configuration

Description

(rep by Y. Guedj)

Set the cluster in a hub-and-spoke topology which, unfortunately, we could not do due to the triad requesting a private IP for the machines on the spoke.

None of our servers are AWS elastic servers, they’re all dedicated servers and therefore have a public IP.

    <server-multi id-prefix="app-"
                           address-list="${app_servers}"
                           port="6800"
                           allow-non-reserved-ip="true"/>

Additional Information

Attached Files

Relationships

Notes
(0006931) ferg 12-13-19 16:56	A dynamic server will use the address given by InetAddress.getLocalHost() by default. If that value is 127.0.0.1, then it will search the network addresses and choose the first. If that algorithm chooses the wrong address, you can use --address on the command line to specify the IP address to use.

Issue History
Date Modified	Username	Field	Change
11-20-19 00:19	nam	New Issue
12-13-19 16:56	ferg	Note Added: 0006931
12-13-19 16:56	ferg	Assigned To	=> ferg
12-13-19 16:56	ferg	Status	new => closed
12-13-19 16:56	ferg	Resolution	open => no change required
12-13-19 16:56	ferg	Fixed in Version	=> 4.0.65

Mantis 1.0.0rc3[^]

29 total queries executed.
26 unique queries executed.