Navigation :
test ../../ test data-connectors-overview.html
Atoti Data Connectors Overview
test ../../ test data-connectors-overview/tracing.html
- Tracing
test ../../ test changelog.html
Release and migration notes
test ../../ test dee-overview.html
Data Extraction Engine
test ../../ test dlc-overview.html
Data Load Controller
test ../../ test dlc-overview/getting-started.html
- Getting Started
test ../../ test dlc-overview/operations.html
-
Operations
test ../../ test dlc-overview/request-api.html
-
Request API
test ../../ test dlc-overview/configuration.html
-
Configuration
test ../../ test dlc-overview/components.html
-
Components
test ../../ test dlc-overview/functional.html
-
Functional
test ../../ test dlc-overview/functional/configurations-flow.html
-- Configuration Flow
test ../../ test dlc-overview/functional/garbage-collection.html
-- Garbage Collection
test ../../ test dlc-overview/functional/scope-parameters.html
-- Scope Parameters
test ../../ test dlc-overview/functional/source-to-topic-matching.html
-- Source to Topic Matching
test ../../ test dlc-overview/extensions.html
-
Extensions
Garbage Collection
Garbage Collection
info
Performing Garbage Collections in the JVM is not guaranteed.
It is up to the JVM to determine if it will perform a GC on our request or not.
Garbage Collection may need to be performed before or after executing an Operation . This can be done by adding
one of the following values to your DLC request:
{
"operation" : "LOAD" ,
"topics" : [ "trades" ],
"performGcOnStart" : true ,
"performGcOnCompletion" : true
}
These properties run a GC request as follows:
"performGcOnStart"
: before the Operation is executed.
"performGcOnCompletion"
: after the Operation is completed.