Internal server error with non-default replication borders
Details
| Detail name | Value |
|---|---|
| Changelog Number | 5095 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | EXASolution 5.0.0 |
| Fix Versions | Exasol 6.1.0 |
| Resolution Date | 2017-11-09 |
Synopsis
In the case when the values of the -soft_replicationborder_in_numrows and -hard_replicationborder_in_numrows command-line parameters are too close, queries may fail to execute and return Internal server error messages.
Details
This bug is caused by an inconsistency in our system which involves the process of deciding whether to replicate tables where in one case the actual number of rows is considered (without the rows marked as deleted) and in the other case the number of rows including the ones marked as deleted is considered.
Workaround
- We suggest that the value of -hard_replicationborder_in_numrows to always be at least 25% higher than the value of -soft_replicationborder_in_numrows, where the 25% are the system's default threshold for table reorganization. This requires a restart of the database.
- In specific cases, manually removing deleted rows using REORGANIZE TABLE <..> ENFORCE can fix the problem. Check for tables being used in the query, with number of rows around the replication border and a significant DELETE_PERCENTAGE in EXA_DBA_TABLES.
