[
https://issues.apache.org/jira/browse/HBASE-20224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442875#comment-16442875
]
stack commented on HBASE-20224:
-------------------------------
bq. This change caused Phoenix's test build to break pretty badly (makes the
parallel tests act as single-threaded, failing all of those trying to run
concurrently)
Because phoenix tests put up a standalone hbase? They don't use
HBaseTestingUtility to start clusters?
bq. I would have thought that a less intrusive fix would be to change the
standalone cluster's hbase-site.xml than change the default value for
hbase.localcluster.assign.random.ports. Is there a reason to not do that?
We want random assignment in tests, no? So, we can have parallelism?
Thanks [~elserj]
> Web UI is broken in standalone mode
> -----------------------------------
>
> Key: HBASE-20224
> URL: https://issues.apache.org/jira/browse/HBASE-20224
> Project: HBase
> Issue Type: Bug
> Components: UI, Usability
> Affects Versions: 2.0.0-beta-2
> Reporter: Umesh Agashe
> Assignee: Umesh Agashe
> Priority: Blocker
> Fix For: 2.0.0
>
> Attachments:
> 0001-HBASE-20224-Web-UI-is-broken-in-standalone-mode-ADDE.ADDENDUM.patch,
> 20224-addendum.3.txt, 20224.addendum.4, 20224.addendum.5, 20224.addendum.6,
> hbase-20224.master.001.patch, hbase-20224.master.002.patch,
> hbase-20224.master.003.patch, hbase-20224.master.addendum.patch
>
>
> Web UI doesn't show up in standalone mode on default port. This can be seen
> on master and branch-2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
