[jira] [Updated] (SLIDER-265) Add role for HBase REST gateway

[ https://issues.apache.org/jira/browse/SLIDER-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated SLIDER-265: - Attachment: (was: AddHBaseRestSvc.patch) > Add role for HBase REST gateway >

[jira] [Updated] (SLIDER-265) Add role for HBase REST gateway

[ https://issues.apache.org/jira/browse/SLIDER-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated SLIDER-265: - Attachment: AddHBaseRestSvc.patch > Add role for HBase REST gateway > ---

[jira] [Updated] (SLIDER-265) Add role for HBase REST gateway

[ https://issues.apache.org/jira/browse/SLIDER-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sumit Mohanty updated SLIDER-265: - Attachment: AddHBaseRestSvc.patch Preliminary patch attached. > Add role for HBase REST gateway

[jira] [Commented] (SLIDER-273) Add ability to specify a port as shared across component instances or not

[ https://issues.apache.org/jira/browse/SLIDER-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084240#comment-14084240 ] ASF subversion and git services commented on SLIDER-273: Commit f6

[jira] [Commented] (SLIDER-219) A service may ask for more than one dynamically allocated port as part of the same configuration

[ https://issues.apache.org/jira/browse/SLIDER-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084238#comment-14084238 ] ASF subversion and git services commented on SLIDER-219: Commit c1

[jira] [Created] (SLIDER-273) Add ability to specify a port as shared across component instances or not

Sumit Mohanty created SLIDER-273: Summary: Add ability to specify a port as shared across component instances or not Key: SLIDER-273 URL: https://issues.apache.org/jira/browse/SLIDER-273 Project: Slid

[jira] [Created] (SLIDER-272) Application should specify the config types to publish

Sumit Mohanty created SLIDER-272: Summary: Application should specify the config types to publish Key: SLIDER-272 URL: https://issues.apache.org/jira/browse/SLIDER-272 Project: Slider Issue T

[jira] [Created] (SLIDER-271) When a container is releases the AppMaster should not monitor heartbeats from that container

Sumit Mohanty created SLIDER-271: Summary: When a container is releases the AppMaster should not monitor heartbeats from that container Key: SLIDER-271 URL: https://issues.apache.org/jira/browse/SLIDER-271

[jira] [Created] (SLIDER-270) Calling flex (down) the second time does not work

Sumit Mohanty created SLIDER-270: Summary: Calling flex (down) the second time does not work Key: SLIDER-270 URL: https://issues.apache.org/jira/browse/SLIDER-270 Project: Slider Issue Type:

Re: ALLOCATED_PORT appears in hbase-site.xml

+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

Re: ALLOCATED_PORT appears in hbase-site.xml

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 wrote: > > On Aug 3, 2014, at 3:40 PM, Ted Yu wrote: > > > This boils dow

Re: ALLOCATED_PORT appears in hbase-site.xml

On Aug 3, 2014, at 3:40 PM, Ted Yu 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

Re: ALLOCATED_PORT appears in hbase-site.xml

This boils down to expected usage of Slider deployed hbase. I think leaving it as 0 should be fine. 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 wrote: > This could be a bug w

Re: ALLOCATED_PORT appears in hbase-site.xml

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.

Re: ALLOCATED_PORT appears in hbase-site.xml

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

Re: ALLOCATED_PORT appears in hbase-site.xml

On Aug 3, 2014, at 11:37 AM, Ted Yu 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: > >

ALLOCATED_PORT appears in hbase-site.xml

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: hbase.regionserver.info.port${HBASE_REGIONSERVER.ALLOCATED_PORT