The release 21.23 introduces new features for component developers and high-end integration projects.
We continue the work dedicated to defining and setting custom timeout intervals.
In this round we extended the capability to include verify credentials, select model
and dynamic data processes. We call them one-time executions. To define a custom
interval for one-time executions set the newly introduced environment variable
SCHEDULED_EXECUTION_TIMEOUT (seconds) in the component repository. If the variable
is not set the platform will use the system defined value.
With 21.23 we are happy to introduce the project dedicated to providing a high availability of integration flow steps by scaling them to replica sets.
Please Note : Most integration scenarios do not require step scaling Using this feature might cause high costs.
The implementation has specific guidelines:
To set number of replicas for the integration flow step use the API call to PATCH v2/flows/:id
endpoint. Here is an example of body for API call.
{
"data": {
"type": "flow",
"id": "",
"attributes": {
"nodes_config": {
"step_1": {
"replicas": 3
}
}
}
}
}
Some OAuth2 providers supply one access token and no refresh token. These are the cases of infinity tokens. To support these cases we extend the functionality of Secrets feature. We implemented the following changes in the Secrets feature:
We released a new Java Sailor 3.3.6 which introduces a parallel processing of messages.
All components written in Java using the new sailor version (3.3.6+) can use newly introduced
environment variable ELASTICIO_CONSUMER_THREAD_POOL_SIZE to set the size
of thread pool for AMQP consumer. If not specified (by default) it equals Prefetch
Count value.
With introduction of SCHEDULED_EXECUTION_TIMEOUT and DEBUG_TASK_TIMEOUT (last release),
we also implemented a validation mechanism for them.
DEBUG_TASK_TIMEOUT and SCHEDULED_EXECUTION_TIMEOUT environment variables.DEBUG_TASK_TIMEOUT and SCHEDULED_EXECUTION_TIMEOUT values have maximum values controlled by the system defined MAX_FORCE_DESTROY_DEBUG_TASK_TIMEOUT_SEC and MAX_FORCE_DESTROY_ONE_TIME_EXEC_SEC parameter values.LOG_LEVEL, PREFETCH and AMQP_PUBLISH_CONFIRM_ENABLED previously defined environment variables. These variables MUST be deleted from the component repositories if they exist.News in this section are for our customers who use OEM version of the elastic.io platform.
The platform deployments migrated to HELM3 from the Ksonnet (last deployment 21.19). Since the intermediate release 21.21 deployments done with HELM3. The current 21.23 release is the second successful deployment using HELM3 charts.
We are using Helm OCI Registry, credentials available upon request.
2.6.24.component.json.