-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
False
-
False
-
-
With a large number of schemas (1k of 50tables each) Debezium can take an excessively long time to start up while waiting for metadata from the DB. This was tested on postgres with the latest 1.6 and 1.7 dbz releases. The behaviour seen is compounded when the db has performance issues, as the meta data query is being run for each schema and table rather than getting everything in a single query. eg, in an online production environment this startup could take a couple days or more.
Primary Issues
- metadata query is different and slower when table.exclude.list is included.
- metadata is retrieved multiple times during startup/snapshot
- metadata query is executing for each table rather than all at once or with schema filter in query.
To see difference, compare time with table.exclude.list and without.