[
https://issues.apache.org/jira/browse/HBASE-20224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442926#comment-16442926
]
Josh Elser commented on HBASE-20224:
------------------------------------
{quote}Because phoenix tests put up a standalone hbase? They don't use
HBaseTestingUtility to start clusters?
{quote}
No, they do use HBaseTestingUtility. Let me show the relevant stacktrace:
{noformat}
2018-04-18 13:13:51,500 ERROR [main]
org.apache.hadoop.hbase.MiniHBaseCluster(269): Error starting cluster
java.lang.RuntimeException: Failed construction of Master: class
org.apache.hadoop.hbase.master.HMasternull
at
org.apache.hadoop.hbase.util.JVMClusterUtil.createMasterThread(JVMClusterUtil.java:136)
at
org.apache.hadoop.hbase.LocalHBaseCluster.addMaster(LocalHBaseCluster.java:212)
at
org.apache.hadoop.hbase.LocalHBaseCluster.<init>(LocalHBaseCluster.java:159)
at org.apache.hadoop.hbase.MiniHBaseCluster.init(MiniHBaseCluster.java:250)
at
org.apache.hadoop.hbase.MiniHBaseCluster.<init>(MiniHBaseCluster.java:121)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniHBaseCluster(HBaseTestingUtility.java:1042)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:988)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:859)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:841)
at
org.apache.hadoop.hbase.HBaseTestingUtility.startMiniCluster(HBaseTestingUtility.java:823)
at org.apache.phoenix.query.BaseTest.initMiniCluster(BaseTest.java:525)
at org.apache.phoenix.query.BaseTest.setUpTestCluster(BaseTest.java:431)
at
org.apache.phoenix.query.BaseTest.checkClusterInitialized(BaseTest.java:417)
at org.apache.phoenix.query.BaseTest.setUpTestDriver(BaseTest.java:499)
at org.apache.phoenix.query.BaseTest.setUpTestDriver(BaseTest.java:494)
at
org.apache.phoenix.end2end.ParallelStatsDisabledIT.doSetup(ParallelStatsDisabledIT.java:37){noformat}
{quote}We want random assignment in tests, no? So, we can have parallelism?
{quote}
Yeah, that's the gist of why I was surprised. It seems odd to me to _not_ force
random ports in a unit testing structure. For example, take a user with some
software that uses HBaseTestingUtility for testing their application with HBase
and also have a version of HBase running locally. 2.0.0 will require them to
set this extra configuration property over something that would just work for
HBase 1.x.**
It just seemed odd to me to fix this issue this way (instead of making a change
specific to the standalone mode). I'll admit, I am half bringing this up
because I thought I might just be missing something..
Given my current understanding, we absolutely need better release notes on this
change (but will wait to make that RN change until we decide what we should do).
> 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)
