View Revisions: Issue #5625
Summary | 0005625: Stack overflow while extracting batch containing a table removed from replication | ||
---|---|---|---|
Revision | 2022-12-13 21:13 by elong | ||
Description | If a table is removed from replication while there are outstanding batches for it, the extraction of batches containing that table can get a stack overflow. Data extractor service looks up the trigger router for each change it extracts. If it can't find a trigger router, it will skip the change and move on to the next. However, the logic is written to skip by calling the current method recursively. So, it can only skip as many rows as the stack size allows. See stack trace below with recursive calls that caused an overflow. Work around the error by removing the table from sym_data: delete from sym_data where table_name = 'table_removed_from_replication'; |
||
Revision | 2022-12-12 20:56 by elong | ||
Description | If a table is removed from replication while there are outstanding batches for it, the extraction of batches containing that table can get a stack overflow. Data extractor service looks up the trigger router for each change it extracts. If it can't find a trigger router, it will skip the change and move on to the next. However, the logic is written to skip by calling the current method recursively. So, it can only skip as many rows as the stack size allows. See additional stack trace with over 600 recursive calls that caused an overflow. |