morningman opened a new issue #2577: [Tablet Report] Tablet report process 
throw NPE and cause report task pile up
URL: https://github.com/apache/incubator-doris/issues/2577
 
 
   **Describe the bug**
   Report tasks pile up in FE and log shows:
   
   `the report queue size exceeds the limit: 100. current: 101`
   
   And NPE:
   
   ```
   2019-12-25 10:02:53,638 ERROR 71 [Daemon.run():118] daemon thread got 
exception:
   java.lang.NullPointerException
           at 
org.apache.doris.catalog.TabletInvertedIndex.tabletReport(TabletInvertedIndex.java:203)
 ~[palo-fe.jar:?]
           at 
org.apache.doris.master.ReportHandler.tabletReport(ReportHandler.java:271) 
~[palo-fe.jar:?]
           at 
org.apache.doris.master.ReportHandler.access$400(ReportHandler.java:92) 
~[palo-fe.jar:?]
           at 
org.apache.doris.master.ReportHandler$ReportTask.exec(ReportHandler.java:235) 
~[palo-fe.jar:?]
           at 
org.apache.doris.master.ReportHandler.runOneCycle(ReportHandler.java:1031) 
~[palo-fe.jar:?]
           at org.apache.doris.common.util.Daemon.run(Daemon.java:116) 
[palo-fe.jar:?]
   ```
   
   **Why**
   
   When processing tablet reports, some tablets carry transaction information.
   This information is used by the FE to determine whether to publish these
   transactions or clear these transactions.
   
   During this process, Doris may try to obtain the commit information of some
   deleted partitions, resulting in a null pointer exception. And NPE will stop 
the 
   process thread for 30 seconds, cause the tasks piling up.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to