Teddy Choi created HIVE-26601:
---------------------------------

             Summary: Fix NPE encountered in second load cycle of optimised 
bootstrap 
                 Key: HIVE-26601
                 URL: https://issues.apache.org/jira/browse/HIVE-26601
             Project: Hive
          Issue Type: Bug
            Reporter: Teddy Choi
            Assignee: Teddy Choi


After creating reverse replication policy  after failover is completed from 
Primary to DR cluster and DR takes over. First dump and load cycle of optimised 
bootstrap is completing successfully, Second dump cycle on DR is also completed 
which does selective bootstrap of tables that it read from table_diff 
directory. However we observed issue with Second load cycle on Primary Cluster 
side which is failing with following exception logs that needs to be fixed.
{code:java}
[Scheduled Query Executor(schedule:repl_vinreverse, execution_id:421)]: 
Exception while logging metrics 
java.lang.NullPointerException: null
        at 
org.apache.hadoop.hive.ql.parse.repl.metric.ReplicationMetricCollector.reportStageProgress(ReplicationMetricCollector.java:192)
 ~[hive-exec-3.1.3000.7.1.8.0-801.jar:3.1.3000.7.1.8.0-801]
        at 
org.apache.hadoop.hive.ql.exec.repl.ReplStateLogWork.replStateLog(ReplStateLogWork.java:145)
 ~[hive-exec-3.1.3000.7.1.8.0-801.jar:3.1.3000.7.1.8.0-801]
        at 
org.apache.hadoop.hive.ql.exec.repl.ReplStateLogTask.execute(ReplStateLogTask.java:39)
 [hive-exec-3.1.3000.7.1.8.0-801.jar:3.1.3000.7.1.8.0-801]
        at org.apache.hadoop.hive.ql.exec.Task.executeTask(Task.java:213) 
[hive-exec-3.1.3000.7.1.8.0-801.jar:3.1.3000.7.1.8.0-801]
        at 
org.apache.hadoop.hive.ql.exec.TaskRunner.runSequential(TaskRunner.java:105) 
[hive-exec-3.1.3000.7.1.8.0-801.jar:3.1.3000.7.1.8.0-801]
        at org.apache.hadoop.hive.ql.Executor.launchTask(Executor.java:357) 
[hive-exec-3.1.3000.7.1.8.0-801.jar:3.1.3000.7.1.8.0-801]
        at org.apache.hadoop.hive.ql.Executor.launchTasks(Executor.java:330) 
[hive-exec-3.1.3000.7.1.8.0-801.jar:3.1.3000.7.1.8.0-801]
        at org.apache.hadoop.hive.ql.Executor.runTasks(Executor.java:246) 
[hive-exec-3.1.3000.7.1.8.0-801.jar:3.1.3000.7.1.8.0-801]
        at org.apache.hadoop.hive.ql.Executor.execute(Executor.java:109) 
[hive-exec-3.1.3000.7.1.8.0-801.jar:3.1.3000.7.1.8.0-801]
        at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:749) 
[hive-exec-3.1.3000.7.1.8.0-801.jar:3.1.3000.7.1.8.0-801]
        at org.apache.hadoop.hive.ql.Driver.run(Driver.java:504) 
[hive-exec-3.1.3000.7.1.8.0-801.jar:3.1.3000.7.1.8.0-801]
        at org.apache.hadoop.hive.ql.Driver.run(Driver.java:498) 
[hive-exec-3.1.3000.7.1.8.0-801.jar:3.1.3000.7.1.8.0-801]
        at 
org.apache.hadoop.hive.ql.reexec.ReExecDriver.run(ReExecDriver.java:166) 
[hive-exec-3.1.3000.7.1.8.0-801.jar:3.1.3000.7.1.8.0-801]
        at 
org.apache.hadoop.hive.ql.reexec.ReExecDriver.run(ReExecDriver.java:232) 
[hive-exec-3.1.3000.7.1.8.0-801.jar:3.1.3000.7.1.8.0-801]
        at 
org.apache.hadoop.hive.ql.scheduled.ScheduledQueryExecutionService$ScheduledQueryExecutor.processQuery(ScheduledQueryExecutionService.java:240)
 [hive-exec-3.1.3000.7.1.8.0-801.jar:3.1.3000.7.1.8.0-801]
        at 
org.apache.hadoop.hive.ql.scheduled.ScheduledQueryExecutionService$ScheduledQueryExecutor.run(ScheduledQueryExecutionService.java:193)
 [hive-exec-3.1.3000.7.1.8.0-801.jar:3.1.3000.7.1.8.0-801]
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[?:1.8.0_232]
        at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
[?:1.8.0_232]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[?:1.8.0_232]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[?:1.8.0_232]
        at java.lang.Thread.run(Thread.java:748) [?:1.8.0_232]{code}
 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to