question Re: Why only host:port export allowed at component level export level ? in Archives of Support Questions (Read Only)

Why only host:port export allowed at component level export level ?

manojsameltech — Fri, 16 Sep 2022 15:16:26 GMT

Hello,

Can some explain the documented limitation in http://slider.incubator.apache.org/docs/slider_specs/specifying_exports.html

In the section on exporting data at component level, "Currently, only the host name and dynamically allocated port values can be exported"

Why only host/port exports are allowed @ component level ?

Thanks, Manoj

Re: Why only host:port export allowed at component level export level ?

aervits — Thu, 24 Dec 2015 11:14:01 GMT

best answered by @stevel

Re: Why only host:port export allowed at component level export level ?

stevel — Thu, 24 Dec 2015 18:52:35 GMT

that doc is a bit confusion: I read it myself and wasn't too sure. I've file a JIRA on reviewing and updating it.

Bearing in mind the python agent-side code is not something I know my way around, I think that comment about hostname:port is actually describing how site configurations can be built up.

I believe that python installation code running in a container can actually push out any quicklink values it wants. Client apps do have to be aware that (a) that data isn't there until the container is up and running, (b) after failover the outdated entries will hang around until replaced

Re: Why only host:port export allowed at component level export level ?

manojsameltech — Fri, 25 Dec 2015 02:38:04 GMT

Thanks Steve. I am aware of your points "a" and "b" - we also discussed "b" on the dev d-list on the thread between two of us and Jon.