| TERRSRV-346
|
TERR service now writes to log files following the same layout pattern that the Node Manager uses.
|
| TERRSRV-439
|
In version 1.2.0, the service had an engine startup timeout that could cancel an engine startup and provide non-informative
WARN or
ERROR messages. Now, if the engine is cancelled due to a timeout, the error message is clearly communicated to the administrator through the Web UI and the log files.
|
| TERRSRV-440
|
The Docker image is now built at service startup, before any engines are created.
In version 1.2.0, the service had a startup timeout that could prematurely end the Docker image build with non-informative
WARN or
ERROR messages. This change prevents the engine startup timeout from interfering with Docker image builds when they are required.
Deleting or removing the Docker image on the
TERR service node while the service is running causes a loss in functionality. This issue can be fixed by stopping and restarting the service.
|
| TERRSRV-451
|
Calling Open Source R using the RinR package could have issues if your script has Windows line endings. This issue has been resolved.
|
| TERRSRV-472
|
The port range properties in
custom.properties have been changed from 61000-63000 to 61000-62000 so it does not potentially conflict with other services.
|
| TERRSRV-477
|
The service can now be set to disable session pruning using the
custom.properties file. Set
engine.session.maxtime to
-1 to allow this behavior.
# The maximum time for a session to live, in seconds. Set to -1 to disable session pruning.
engine.session.maxtime: 120
|
| TERRSRV-503
|
The TERR Service now correctly handles temporary work directories for Windows users with user names longer than 8 characters.
|
| TERRSRV-518
|
The service now determines the max sessions and engine queue size variables to be ""one less than the number of logical processors."" Previously, these values were equal to the number of logical processors. This change was made to conform with TIBCO Spotfire® Statistics Services' defaults. The engine queue size is now capped at 10 by default. Previously, this value was equal to the number of logical processors on the machine with no cap. As a result, some highly-provisioned machines would have too many
TERR service engines inactive in the queue, which became a drain on system resources. This property can be set manually to a value higher than 10.
|
| TERRSRV-526
|
Warnings during package loading are now suppressed, unless data function debugging is set.
|
| TERRSRV-599
|
If the
engine.session.max value was not explicitly set in a custom configuration, the
TERR service would report the default capacity of 5 concurrent sessions to the server. This resulted in routing problems when the server and the service were out of sync with how many sessions were available.
|
| TERRSRV-561
|
The service now updates the
last used timestamp much more frequently. This change reduces the occurrence of certain edge cases in which the idle timeout would cancel data functions that involve long upload times.
|
