[
https://issues.apache.org/jira/browse/HBASE-18889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186447#comment-16186447
]
Biju Nair commented on HBASE-18889:
-----------------------------------
In a multi namenode scenario (which will be HDFS HA), it would be better use
the HDFS service name instead of the individual NN hostnames since any one can
be an active NN. By using the HDFS service name, is this still an issue?
> Different namenodes url but the same location in are treated differently
> ------------------------------------------------------------------------
>
> Key: HBASE-18889
> URL: https://issues.apache.org/jira/browse/HBASE-18889
> Project: HBase
> Issue Type: Bug
> Reporter: Vishal Khandelwal
>
> I tried to create a full backup like this which passed:
> {code} ./bin/hbase backup create full hdfs://localhost:8020/backup1 -t test1
> {code}
> and incremental by following
> {code} ./bin/hbase backup create incremental hdfs://<hostname>:8020/backup1
> -t test1 {code}
> 2017-09-27 10:34:45,010 ERROR [main] backup.BackupDriver: Error running
> command-line tool
> java.io.IOException: Incremental backup table set contains no tables. You
> need to run full backup first on test1
> at
> org.apache.hadoop.hbase.backup.impl.BackupAdminImpl.backupTables(BackupAdminImpl.java:536)
> at
> org.apache.hadoop.hbase.backup.impl.BackupCommands$CreateCommand.execute(BackupCommands.java:336)
> at
> org.apache.hadoop.hbase.backup.BackupDriver.parseAndRun(BackupDriver.java:137)
> at
> org.apache.hadoop.hbase.backup.BackupDriver.doWork(BackupDriver.java:170)
> at
> org.apache.hadoop.hbase.backup.BackupDriver.run(BackupDriver.java:203)
> at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
> at
> org.apache.hadoop.hbase.backup.BackupDriver.main(BackupDriver.java:178)
> In production in case of multiple namenode, we can use different way to start
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
