Clarify and simplify network names and socket binding
-----------------------------------------------------
Key: SEQUOIA-804
URL: https://forge.continuent.org/jira/browse/SEQUOIA-804
Project: Sequoia
Type: Improvement
Components: Core
Versions: Sequoia 2.10, Sequoia 2.9
Reporter: Marc Herbert
It's currently very difficult to understand the code that handle controller
names, JDBC and JMX IP addresses.
Besides long term maintenance issues, a more short term issue is that
configuring only a controller name,
(without any JDBC or JMX binding) does not work (backuper breaks).
To get an idea of the complexity and of the sheer volume of code have a look
here;
- RmiConnector#createJRMPAdaptor()
- ControllerConfiguration#setupJmx() #setUp()
- ControllerParser#configureController()
- ControllerServerThread(Controller controller)
This clean-up is also required if we ever want to support IPv6 (BTW "0.0.0.0"
is not an IPv6 address).
Another related issue is the generalized use of untyped String IP addresses
instead of proper Java objects
(script-style programming), never knowing for instance whether the string holds
an hostname or a quad-dotted
address.
A related issue is that the backuper does not re-use the group communication IP
address.
See this related blurb:
<http://article.gmane.org/gmane.comp.db.sequoia.general/286>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
