Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

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

Solved Go to solution

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

New Contributor

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

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

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

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

View solution in original post

3 REPLIES 3
Highlighted

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

Mentor

best answered by @stevel

Highlighted

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

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

View solution in original post

Highlighted

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

New Contributor

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.

Don't have an account?
Coming from Hortonworks? Activate your account here