av9ash/GitBugs huggingface dataset:
Bug: Fix the shellcheck download url
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 14/Aug/20 03:11

*10:43:08* You are downloading ShellCheck from an outdated URL! *10:43:08* *10:43:08* Please update to the new URL: *10:43:08* [https://github.com/koalaman/shellcheck/releases/download/stable/shellcheck-stable.linux.x86_64.tar.xz] *10:43:08* *10:43:08* For more information, see: *10:43:08* [https://github.com/koalaman/shellcheck/issues/1871] *10:43:08* *10:43:08* PS: Sorry for breaking your build :( *10:43:08* You are downloading ShellCheck from an outdated URL!
Bug: Fix the flaky job url in hbase-personality.sh
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 13/Aug/20 03:02

 

I found that the precommit job of branch-2.2 still used the wrong url. See [https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2247/1/console]
{code:java}
16:56:14  [Wed Aug 12 08:56:14 UTC 2020 INFO]: Personality: patch unit
16:56:14  [Wed Aug 12 08:56:14 UTC 2020 INFO]: EXCLUDE_TESTS_URL=
16:56:14  [Wed Aug 12 08:56:14 UTC 2020 INFO]: INCLUDE_TESTS_URL=
16:56:14  --2020-08-12 08:56:14--  https://builds.apache.org/job/HBase-Find-Flaky-Tests/job/branch-2.2/lastSuccessfulBuild/artifact/excludes/
16:56:14  Resolving builds.apache.org (builds.apache.org)... 195.201.213.130, 2a01:4f8:c0:2cc9::2
16:56:14  Connecting to builds.apache.org (builds.apache.org)|195.201.213.130|:443... connected.
16:56:15  HTTP request sent, awaiting response... 404 
16:56:15  2020-08-12 08:56:15 ERROR 404: (no description).
16:56:15  
16:56:15  Wget error 8 in fetching excludes file from url https://builds.apache.org/job/HBase-Find-Flaky-Tests/job/branch-2.2/lastSuccessfulBuild/artifact/excludes/. Ignoring and proceeding.{code}
Bug: migrate website generation to new asf jenkins
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 12/Aug/20 03:01

Update our website generation so we can use it on the new jenkins ci server

* needs a job name that has no spaces (or fix the script to handle paths with spaces)
* needs to only run on nodes labeled git-websites (so it will have the creds to push updates)
* needs to set editable email notification on failure (details in comment)

Also we will need to converte to a pipeline DSL
* define tools, namely maven (alternative get [Tool Environment Plugin|https://plugins.jenkins.io/toolenv/])
* set timeout for 4 hours (alternative get [build timeout plugin|https://plugins.jenkins.io/build-timeout/])
* needs to clean worksapce when done (haven't found an alternatiave, maybe it's a default for non-pipeline jobs now?)
Bug: Previous RC Release notes are not removed
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 10/Jul/20 10:07

The update_releasenotes function does not remove previous RC's Release notes from RELEASENOTES.md file.

CHANGES.md does not have this issue.

[https://github.com/apache/hbase/blob/master/dev-support/create-release/release-util.sh#L493-L497]
Bug: Fix error prone error in FlushTableSubprocedure
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 11/Aug/20 14:00

{noformat}
[ERROR] /home/jenkins/jenkins-home/workspace/HBase_HBase_Nightly_master/component/hbase-server/src/main/java/org/apache/hadoop/hbase/procedure/flush/FlushTableSubprocedure.java:[105,30] error: [ArraysAsListPrimitiveArray] Arrays.asList does not autobox primitive arrays, as one might expect.
    (see https://errorprone.info/bugpattern/ArraysAsListPrimitiveArray)
  Did you mean 'families = Bytes.asList(Bytes.toBytes(family));'?
[INFO] 1 error
{noformat}
Bug: Error message is displayed in the UI of table's compaction state if any region of that table is not open.
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 10/Jul/20 12:11
Affects Version/s: 2.2.3

When a region of a table is in states closed, merging, splitting, etc, the table's compaction state displays error stack trace.

 

!ErrorMessageinUI.png!
Bug: Override CSP in our flaky dashboard html
Status: Resolved | Priority: Major | Resolution: Won't Fix
Created: 11/Aug/20 02:46

We got this on the new find flaky tests job.

{noformat}
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-NSQHKKs1VuvATRi81u9VAYWYDZfJrWTnQg5Ag4MxBQU='), or a nonce ('nonce-...') is required to enable inline execution.
{noformat}
Bug: Download Boost when DOWNLOAD_DEPENDENCIES flag is set
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 02/Aug/20 16:00
Affects Version/s: native-client-0.1.0

HBASE-24539 added a boost dependency on {{dll:program_location}} that is 1_61_0+. However the default boost installed by various package managers across linux distros is different. For ex: the docker that builds on top of ubuntu-16.04 pulls in 1_5x_x version of boost dev and that broke the build. The ask is to bring boost under DOWNLOAD_DEPENDENCIES flag so that we can standardize across versions easily.
Bug: Add Cell level TTL functionality at HBase Thrift1/Thrift2
Status: Open | Priority: Major | Resolution: 
Created: 07/Aug/20 10:09

Setting TTL at cell level can be done via Java Client, Hbase shell, but this funtionalty is missing at thrift server and client.

ref ticket : https://issues.apache.org/jira/browse/HBASE-11764
Bug: Avoid flooding replication source RSes logs when no sinks are available 
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 22/Jul/20 15:18
Affects Version/s: 2.2.5

On HBaseInterClusterReplicationEndpoint.replicate, if no sinks are returned by ReplicationSinkManager, say remote peer is not available, we log message below and return false to source shipper thread, which then keeps retrying, flooding source RS log with the below messages:

{noformat}
WARN org.apache.hadoop.hbase.replication.regionserver.HBaseInterClusterReplicationEndpoint: No replication sinks found, returning without replicating. The source should retry with the same set of edits.
{noformat}

This condition could also cause ReplicationSinkManager.chooseSinks to blow an NPE.
Bug: RegionMover should deal with unknown (split/merged) regions
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 29/Jul/20 17:36

For a cluster with very high load, it is quite common to see flush/compaction happening every minute on each RegionServer. And we have quite high chances of multiple regions going through splitting/merging.

RegionMover, while unloading all regions (graceful stop), writes down all regions to a local file and while loading them back (graceful start), ensures to bring every single region back from other RSs. While loading regions back, even if a single region can't be moved back, RegionMover considers load() failure. We miss out on possibilities of some regions going through split/merge process and the fact that not all regions written to local file might even exist anymore. Hence, RegionMover should gracefully handle moving any unknown region without marking load() failed.
Bug: HBaseTestingUtility.getConnection should be threadsafe
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 31/Jul/20 07:33

the current javadoc for getConnection carries a thread safety warning:
{code}
/**
    * Get a Connection to the cluster. Not thread-safe (This class needs a lot of work to make it
    * thread-safe).
    * @return A Connection that can be shared. Don't close. Will be closed on shutdown of cluster.
    */
   public Connection getConnection() throws IOException {
{code}

We then ignore that warning across our test base. We should make the method threadsafe since the intention is to share a single Connection across all users of the HTU instance.
Bug: Enhance ACL region initialization
Status: Open | Priority: Major | Resolution: 
Created: 30/Jul/20 12:24

RegionServer persist ACL table entries into Zookeeper during ACL region open,

{code}
      private void initialize(RegionCoprocessorEnvironment e) throws IOException {
    final Region region = e.getRegion();
    Configuration conf = e.getConfiguration();
    Map<byte[], ListMultimap<String, UserPermission>> tables = PermissionStorage.loadAll(region);
    // For each table, write out the table's permissions to the respective
    // znode for that table.
    for (Map.Entry<byte[], ListMultimap<String, UserPermission>> t:
      tables.entrySet()) {
      byte[] entry = t.getKey();
      ListMultimap<String, UserPermission> perms = t.getValue();
      byte[] serialized = PermissionStorage.writePermissionsAsBytes(perms, conf);
      zkPermissionWatcher.writeToZookeeper(entry, serialized);
    }
    initialized = true;
  }
{code}

Currently RegionServer send 2 RPC (one to create the table path and another to set the data) for each table sequentially.
{code}
 try {
      ZKUtil.createWithParents(watcher, zkNode);
      ZKUtil.updateExistingNodeData(watcher, zkNode, permsData, -1);
    } catch (KeeperException e) {
      LOG.error("Failed updating permissions for entry '" +
          entryName + "'", e);
      watcher.abort("Failed writing node "+zkNode+" to zookeeper", e);
    }
{code}

If a cluster have huge number of tables then ACL region open will take time. Example, it took ~9 min to write 60k tables ACL into ZK. 

We should send ZK Ops in a single multi() to enhance this.
Bug: FSHLog - close the current WAL file in a background thread
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 08/Jul/20 13:43

We have this as a TODO in code already
{code}
// It is at the safe point. Swap out writer from under the blocked writer thread.
      // TODO: This is close is inline with critical section. Should happen in background?
      if (this.writer != null) {
        oldFileLen = this.writer.getLength();
        try {
          TraceUtil.addTimelineAnnotation("closing writer");
          this.writer.close();
          TraceUtil.addTimelineAnnotation("writer closed");
          this.closeErrorCount.set(0);
        }
{code}
This close call in critical section and writes are blocked. Lets move this close call into another WALCloser thread.
Bug: [hbase-thirdparty] Ignore module-info and SubmissionPublisher in enforceBytecodeVersion rule
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 30/Jul/20 10:52

Got this when releasing thirdparty-3.4.0.

{noformat}
10:46:33 [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-maven-version) @ hbase-shaded-jersey ---
10:46:33 [INFO] Restricted to JDK 1.8 yet org.glassfish.jersey.core:jersey-common:jar:2.31:compile contains META-INF/versions/11/org/glassfish/jersey/internal/jsr166/SubmissionPublisher$1.class targeted to 55.0
10:46:33 [INFO] Restricted to JDK 1.8 yet jakarta.ws.rs:jakarta.ws.rs-api:jar:2.1.6:compile contains module-info.class targeted to JDK 1.9
10:46:33 [WARNING] Rule 1: org.apache.maven.plugins.enforcer.EnforceBytecodeVersion failed with message:
HBase has unsupported dependencies.
  HBase requires that all dependencies be compiled with version 1.8 or earlier
  of the JDK to properly build from source.  You appear to be using a newer dependency. You can use
  either "mvn -version" or "mvn enforcer:display-info" to verify what version is active.
  Non-release builds can temporarily build with a newer JDK version by setting the
  'compileSource' property (eg. mvn -DcompileSource=1.8 clean package).
Found Banned Dependency: org.glassfish.jersey.core:jersey-common:jar:2.31
Found Banned Dependency: jakarta.ws.rs:jakarta.ws.rs-api:jar:2.1.6
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
{noformat}
Bug: [hbase-operator-tools] Merging regions failed when the table is not default namespace
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 27/Jul/20 09:30
Affects Version/s: hbase-operator-tools-1.1.0

Suppose there is a table "test:test_table", if you want to merge regions and run the command:
{code:java}
/opt/hbase/bin/hbase org.apache.hbase.RegionsMerger test:test_table 10
{code}
Then you will get error:
{code:java}
[main] ERROR org.apache.hbase.RegionsMerger - Merging regions failed:[main] ERROR org.apache.hbase.RegionsMerger - Merging regions failed:java.lang.IllegalArgumentException: java.net.URISyntaxException: Relative path in absolute URI: test:test_table 
    at org.apache.hadoop.fs.Path.initialize(Path.java:259) ~[hadoop-common-3.2.0.jar:?] 
    at org.apache.hadoop.fs.Path.<init>(Path.java:217) ~[hadoop-common-3.2.0.jar:?] 
    at org.apache.hadoop.fs.Path.<init>(Path.java:125) ~[hadoop-common-3.2.0.jar:?] 
    at org.apache.hbase.RegionsMerger.getTablePath(RegionsMerger.java:93) ~[hbase-tools-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT] 
    at org.apache.hbase.RegionsMerger.mergeRegions(RegionsMerger.java:163) ~[hbase-tools-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT] 
    at org.apache.hbase.RegionsMerger.run(RegionsMerger.java:237) [hbase-tools-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT] 
    at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76) [hadoop-common-3.2.0.jar:?] 
    at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:90) [hadoop-common-3.2.0.jar:?] 
    at org.apache.hbase.RegionsMerger.main(RegionsMerger.java:247) [hbase-tools-1.1.0-SNAPSHOT.jar:1.1.0-SNAPSHOT]Caused by: java.net.URISyntaxException: Relative path in absolute URI: test:test_table 
    at java.net.URI.checkPath(URI.java:1823) ~[?:1.8.0_121] 
    at java.net.URI.<init>(URI.java:745) ~[?:1.8.0_121] 
    at org.apache.hadoop.fs.Path.initialize(Path.java:256) ~[hadoop-common-3.2.0.jar:?]
   ... 8 more
{code}
Bug: [Shell] processlist command fails with ERROR: Unexpected end of file from server when SSL enabled
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 14/Jul/20 08:23

HBase Shell command "processlist" fails with ERROR: Unexpected end of file from server when HBase SSL enabled.

 

Below code is commented since beginning, see HBASE-4368,

[https://github.com/apache/hbase/blob/8076eafb187ce32d4a78aef482b6218d85a985ac/hbase-shell/src/main/ruby/hbase/taskmonitor.rb#L85]
Bug: Update 2.1 documentation to 2.1.9 and remove direct link from main page
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 23/Jul/20 18:33

For the 2.1 release the available documentation points to 2.1.5. Since the release has reached EOL with 2.1.9 the documentation on the website should reflect this and a direct link to 2.1 should be removed.
Bug: Incorrect checksum calculation in saveVersion.sh
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 10/Jul/20 09:59

The saveVersion.sh file does not parse the srcChecksum correctly during the releasing process when dev-support/create-release/hbase-rm/Dockerfile is used. This results in missing Source Checksum.

Master UI displays this:
|HBase Source Checksum|(stdin)=|
Bug: Log an ERROR if HBaseSaslRpcServer initialisation fails with an uncaught exception
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 17/Jul/20 17:12
Affects Version/s: 2.3.1

In ServerRpcConnection.saslReadAndProcess, if an uncaught exception happens while initialising HBaseSaslRpcServer, the same gets swallowed inside netty and never explicitly logged on RegionServer logs. With the introduction of pluggable sasl server providers by HBASE-23347, this situation can become more frequent with the addition of custom providers, if those cause HBaseSaslRpcServer to fail, that should be logged in ServerRpcConnection.saslReadAndProces.
Bug: Distributing ROOT Region load
Status: Open | Priority: Major | Resolution: 
Created: 13/Jul/20 15:51

HBASE-11288 'Splittable Meta' progress keeps getting hung up on how to cache the 'root' table – the first table in the hierarchy of lookups locating user-data in a Table Region. The 'root' table is not splittable by design so its load can not be spread about the cluster by splitting the hot Region as we would usually do.

This issue is about listing out requirements, sketching possible approaches, and then getting agreement ahead of implementation as subtasks.

In particular, an approach that would work whether the Region to be cached is master-based or hosted by a RegionServer (see design attached to HBASE-11288 for elaboration) would be preferred since then we can separate discussion of cache from the HBASE-11288 'split meta' discussion.
Bug: Turn OFF Canary WebUI as default
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 08/Jul/20 22:22

See parent issue. There is a CLASSPATH issue when running against hadoop3 that needs resolving. Meantime, the canary fails to run with a cryptic message (mentioned in the parent in full but it is 'Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.hbase.shaded.org.eclipse.jetty.server.HttpConfiguration$Customizer' in short). This will surprise operators who are used to the canary's previous pure-cli experience. Let me make it so you ask for the canary webui; by default, it does not come up.
Bug: rename_rsgroup overwriting the existing rsgroup.
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 13/Jul/20 12:50

rename_rsgroup overwriting the current rsgroup.

Steps:

1)add_rsgroup 'RSG1' and 'RSG2'

2)move_servers_rsgroup 'RSG1',['server1:port']

3)rename_rsgroup 'RSG1','RSG2'

 After performing step3 RSG1 overwriting to RSG2 and region servers added in RSG1 are not available now.

Ideally system should show error message Group already exists: RSG2
Bug: [Flaky] TestMasterNoCluster.testStopDuringStart on master
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 10/Jul/20 10:12

We need to forward port HBASE-24656 to master branch.

The test logs from flaky report: 

[https://builds.apache.org/job/HBase-Flaky-Tests/job/master/6537/testReport/org.apache.hadoop.hbase.master/TestMasterNoCluster/testStopDuringStart/]

[https://builds.apache.org/job/HBase-Flaky-Tests/job/master/6530/testReport/org.apache.hadoop.hbase.master/TestMasterNoCluster/testStopDuringStart/]

 

2020-07-10 07:08:04,815 DEBUG [Time-limited test-EventThread] zookeeper.ZKWatcher(555): @Before-0x1010270f65d0001, quorum=127.0.0.1:59817, baseZNode=/hbase Received ZooKeeper Event, type=NodeChildrenChanged, state=SyncConnected, path=/hbase/backup-masters 2020-07-10 07:08:04,824 DEBUG [master/asf904:0:becomeActiveMaster] zookeeper.ZKUtil(358): master:44963-0x1010270f65d0000, quorum=127.0.0.1:59817, baseZNode=/hbase Set watcher on existing znode=/hbase/backup-masters/asf904.gq1.ygridcore.net,44963,1594364881716 2020-07-10 07:08:04,827 INFO [Time-limited test] zookeeper.ZKUtil(1809): multi exception: org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty; running operations sequentially (runSequentialOnMultiFailure=true);

 

org.apache.zookeeper.KeeperException$NotEmptyException: KeeperErrorCode = Directory not empty for /hbase/backup-masters at org.apache.hadoop.hbase.master.TestMasterNoCluster.tearDown(TestMasterNoCluster.java:98)
Bug: Do the error handling for replication admin failures
Status: Open | Priority: Major | Resolution: 
Created: 10/Jul/20 20:21

[listPeerConfigs()|https://github.com/apache/hbase/blob/branch-1/hbase-client/src/main/java/org/apache/hadoop/hbase/client/replication/ReplicationAdmin.java#L295] for getting the list of peers along with their configuration is not a reliable API.

It is not very robust to errors, logs FATAL and swallows the [exceptions|https://github.com/apache/hbase/blob/branch-1/hbase-client/src/main/java/org/apache/hadoop/hbase/replication/ReplicationPeersZKImpl.java#L254]

 

Snippet:


{code:java}
catch (KeeperException e) {
 this.abortable.abort("Cannot get the list of peers ", e);
} catch (ReplicationException e) {
 this.abortable.abort("Cannot get the list of peers ", e);
}
return peers;
{code}


 


The abortable (connection in this case) also doesn't abort the region server and just logs. This makes upstream believe that there is nothing wrong and proceed without any action which is not good.

 

 
{code:java}
2020-07-07 23:11:37,857 FATAL [14774961,peer_id] client.ConnectionManager$HConnectionImplementation - Cannot get the list of peersorg.apache.zookeeper.KeeperException$SessionExpiredException: KeeperErrorCode = Session expired for /hbase/replication/peersat org.apache.zookeeper.KeeperException.create(KeeperException.java:130)at org.apache.zookeeper.KeeperException.create(KeeperException.java:54)at org.apache.zookeeper.ZooKeeper.getChildren(ZooKeeper.java:1549)at org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper.getChildren(RecoverableZooKeeper.java:312)at org.apache.hadoop.hbase.zookeeper.ZKUtil.listChildrenNoWatch(ZKUtil.java:513)at org.apache.hadoop.hbase.replication.ReplicationPeersZKImpl.getAllPeerConfigs(ReplicationPeersZKImpl.java:249)at org.apache.hadoop.hbase.client.replication.ReplicationAdmin.listPeerConfigs(ReplicationAdmin.java:332)
{code}
Bug: Add procedure process time statistics UI
Status: Resolved | Priority: Major | Resolution: Fixed
Created: 01/Jul/20 01:32

Added in "Procedures & Locks" jsp.

For the first version UI, we care about the process time of ServerCrashProcedure, TRSP, OpenRegionProcedure and CloseRegionProcedure. Plan to show the avg/P50/P90/min/max process time of these procedures.
Bug: Fix Empty region in meta with read replica
Status: Open | Priority: Major | Resolution: 
Created: 09/Jul/20 18:35
Affects Version/s: 2.3.0

Currently, there is a case in CatalogJanitor which checks if the default region info is missing in metaRow, it is reporting it as EmptyRegionInfoList. 

 

For read replica, this entry needs to be dealt with. In hbase-1, this was caused by region server opens an orphan replica region. In hbase-2, it will not happen since checks are added to defend this case. The hback2 fix is still needed for upgrade. Issues could be brought into hbase-2 post upgrade, hbck2 needs to handle it.
Bug: When merging a non-empty region with empty regions, skip the reference creation to avoid compaction.
Status: Open | Priority: Major | Resolution: 
Created: 09/Jul/20 16:36
Affects Version/s: 2.3.0

Note here while I remember, for the case, there is snapshot, hfiles need to be moved to archive directory to avoid breaking snapshot, so at least one check is needed for this improvement.
Bug: Turn OFF Canary WebUI as default
Status: Resolved | Priority: Major | Resolution: Duplicate
Created: 08/Jul/20 22:45

See parent issue. There is a CLASSPATH issue when running against hadoop3 that needs resolving. Meantime, the canary fails to run with a cryptic message. This will surprise operators. Let me make it so you ask for the canary webui; by default, it does not come up.
Bug: Turn OFF Canary WebUI as default
Status: Resolved | Priority: Major | Resolution: Duplicate
Created: 08/Jul/20 22:40

See parent issue. There is a CLASSPATH issue when running against hadoop3 that needs resolving. Meantime, the canary fails to run with a cryptic message. This will surprise operators. Let me make it so you ask for the canary webui; by default, it does not come up.
Bug: Turn OFF Canary WebUI as default
Status: Resolved | Priority: Major | Resolution: Duplicate
Created: 08/Jul/20 22:29

See parent issue. There is a CLASSPATH issue when running against hadoop3 that needs resolving. Meantime, the canary fails to run with a cryptic message. This will surprise operators. Let me make it so you ask for the canary webui; by default, it does not come up.
Bug: Turn OFF Canary WebUI as default
Status: Resolved | Priority: Major | Resolution: Duplicate
Created: 08/Jul/20 22:25

See parent issue. There is a CLASSPATH issue when running against hadoop3 that needs resolving. Meantime, the canary fails to run with a cryptic message. This will surprise operators. Let me make it so you ask for the canary webui; by default, it does not come up.
Bug: Turn OFF Canary WebUI as default
Status: Resolved | Priority: Major | Resolution: Duplicate
Created: 08/Jul/20 22:24

See parent issue. There is a CLASSPATH issue when running against hadoop3 that needs resolving. Meantime, the canary fails to run with a cryptic message. This will surprise operators. Let me make it so you ask for the canary webui; by default, it does not come up.