If its explicitly assigned "0" then Slider does not do anything.
When app wants Slider to do port allocation then there are several
possibilities:
* Simply ask for a port (not very likely unless app does not support
specifying "0")
* Ask for a port that is per component instance - the allocated port value
need not be shared with other instances (e.g. hbase_rs port)
** While the port may not be shared across, the component may still want to
advertise it (e.g. memcached)
* Ask for a port that is also shared with other instances and also
published (e.g. hbase_master)
There are some more capabilities as well
* Ask for a port but with a default value to be assigned if its free (can
come in handy during tests)
* Ask for a port but within a range (reduce chance of port clash)
On Mon, Aug 4, 2014 at 6:50 AM, Jon Maron <jma...@hortonworks.com> wrote:
> Just to be clear:
>
> To indicate a random value allocation, the specified config in
> appConfig.json will now be:
>
> “some.randomly.assigned.port”: “0”
>
> Or are we still indicating this with a flag and simply plugging in a 0
> during processing? Is that the implication of “do not propagate” (which in
> that instance perhaps should be “do not display”)?
>
> On Aug 3, 2014, at 7:13 PM, Sumit Mohanty <smoha...@hortonworks.com>
> wrote:
>
> > +1 to Ted's explanation.
> >
> > With two hbase masters its little more complicated. We need to figure out
> > how exactly a user can find out the currently active master.
> >
> > On that front, is the management UI and jmx endpoint the only reasons to
> > find the currently active master?
> >
> > -Sumit
> >
> >
> > On Sun, Aug 3, 2014 at 3:01 PM, Ted Yu <yuzhih...@gmail.com> wrote:
> >
> >> In this case whichever value is presented for
> hbase.regionserver.info.port
> >> would be misleading - not all region servers listen on that port.
> >> It's better to leave it as 0.
> >>
> >> Cheers
> >>
> >>
> >> On Sun, Aug 3, 2014 at 1:06 PM, Jon Maron <jma...@hortonworks.com>
> wrote:
> >>
> >>>
> >>> On Aug 3, 2014, at 3:40 PM, Ted Yu <yuzhih...@gmail.com> wrote:
> >>>
> >>>> This boils down to expected usage of Slider deployed hbase.
> >>>>
> >>>> I think leaving it as 0 should be fine.
> >>>
> >>> Setting these values to zero in the configuration implies that a random
> >>> port will be selected. I take it from the discussion below that HBASE
> is
> >>> responsible for registering the selected ports and subsequently making
> >> them
> >>> available for clients? Or is that what we’re trying to answer here?
> >>>
> >>>> What about HBASE_MASTER.ALLOCATED_PORT
> >>>> ? Similar issue may occur there - port of standby master is returned.
> >>>>
> >>>> Cheers
> >>>>
> >>>>
> >>>> On Sun, Aug 3, 2014 at 11:00 AM, Sumit Mohanty <
> >> smoha...@hortonworks.com
> >>>>
> >>>> wrote:
> >>>>
> >>>>> This could be a bug where HBASE_MASTER publishes the data before
> >>> HBASE_RS
> >>>>> can provide the port. The easiest way to fix is change the order of
> >>>>> INSTALL/START but this also brings out a larger problem.
> >>>>>
> >>>>> As all HBASE_RS may get allocated different ports, so what port
> number
> >>>>> should HBASE be registering. It might be easier to leave it as 0. Any
> >>> ideas
> >>>>> on this front?
> >>>>>
> >>>>>
> >>>>> On Sun, Aug 3, 2014 at 9:19 AM, Ted Yu <yuzhih...@gmail.com> wrote:
> >>>>>
> >>>>>> I used the following script to retrieve hbase-site.xml - so the
> value
> >>> in
> >>>>> my
> >>>>>> first email did come from Slider:
> >>>>>>
> >>>>>> tuple=`slider status $1 | grep "info.am.web.url"`
> >>>>>> echo $tuple
> >>>>>> FS=":"
> >>>>>> url=`echo $tuple | awk '{split($0,array,": ")} END{print array[2]}'`
> >>>>>> url="${url%,}"
> >>>>>> url="${url%\"}"
> >>>>>> url="${url#\"}"
> >>>>>> url="${url}ws/v1/slider/publisher/slider/hbase-site.xml"
> >>>>>> curl -k -o hbase-site.dnld $url
> >>>>>>
> >>>>>>
> >>>>>> On Sun, Aug 3, 2014 at 8:47 AM, Jon Maron <jma...@hortonworks.com>
> >>>>> wrote:
> >>>>>>
> >>>>>>>
> >>>>>>> On Aug 3, 2014, at 11:37 AM, Ted Yu <yuzhih...@gmail.com> wrote:
> >>>>>>>
> >>>>>>>> Hi,
> >>>>>>>> I specified the following in appConfig.json:
> >>>>>>>> "site.hbase-site.hbase.regionserver.info.port":
> >>>>>>>> "${HBASE_REGIONSERVER.ALLOCATED_PORT}",
> >>>>>>>>
> >>>>>>>> After fetching effective hbase-site.xml from Slider hbase
> >> instance, I
> >>>>>>>> noticed the following:
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> >>
> <property><name>hbase.regionserver.info.port</name><value>${HBASE_REGIONSERVER.ALLOCATED_PORT}</value><source/></property>
> >>>>>>>>
> >>>>>>>> Has anyone else noticed similar issue ?
> >>>>>>>
> >>>>>>> What happens if you fetch it from slider itself? Is that one
> >> correct?
> >>>>> I
> >>>>>>> wonder if the in memory version simply isn’t being persisted?
> >>>>>>>
> >>>>>>>>
> >>>>>>>> Cheers
> >>>>>>>
> >>>>>>>
> >>>>>>> --
> >>>>>>> CONFIDENTIALITY NOTICE
> >>>>>>> NOTICE: This message is intended for the use of the individual or
> >>>>> entity
> >>>>>> to
> >>>>>>> which it is addressed and may contain information that is
> >>> confidential,
> >>>>>>> privileged and exempt from disclosure under applicable law. If the
> >>>>> reader
> >>>>>>> of this message is not the intended recipient, you are hereby
> >> notified
> >>>>>> that
> >>>>>>> any printing, copying, dissemination, distribution, disclosure or
> >>>>>>> forwarding of this communication is strictly prohibited. If you
> have
> >>>>>>> received this communication in error, please contact the sender
> >>>>>> immediately
> >>>>>>> and delete it from your system. Thank You.
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>> --
> >>>>> CONFIDENTIALITY NOTICE
> >>>>> NOTICE: This message is intended for the use of the individual or
> >>> entity to
> >>>>> which it is addressed and may contain information that is
> >> confidential,
> >>>>> privileged and exempt from disclosure under applicable law. If the
> >>> reader
> >>>>> of this message is not the intended recipient, you are hereby
> notified
> >>> that
> >>>>> any printing, copying, dissemination, distribution, disclosure or
> >>>>> forwarding of this communication is strictly prohibited. If you have
> >>>>> received this communication in error, please contact the sender
> >>> immediately
> >>>>> and delete it from your system. Thank You.
> >>>>>
> >>>
> >>>
> >>> --
> >>> CONFIDENTIALITY NOTICE
> >>> NOTICE: This message is intended for the use of the individual or
> entity
> >> to
> >>> which it is addressed and may contain information that is confidential,
> >>> privileged and exempt from disclosure under applicable law. If the
> reader
> >>> of this message is not the intended recipient, you are hereby notified
> >> that
> >>> any printing, copying, dissemination, distribution, disclosure or
> >>> forwarding of this communication is strictly prohibited. If you have
> >>> received this communication in error, please contact the sender
> >> immediately
> >>> and delete it from your system. Thank You.
> >>>
> >>
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entity
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the reader
> > of this message is not the intended recipient, you are hereby notified
> that
> > any printing, copying, dissemination, distribution, disclosure or
> > forwarding of this communication is strictly prohibited. If you have
> > received this communication in error, please contact the sender
> immediately
> > and delete it from your system. Thank You.
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
--
thanks
Sumit
