View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003616 | SymmetricDS | Bug | public | 2018-06-29 17:06 | 2018-07-23 15:13 |
| Reporter | mmichalek | Assigned To | mmichalek | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.8.31 | ||||
| Target Version | 3.8.37 | Fixed in Version | 3.8.37 | ||
| Summary | 0003616: Add better logging and handling for intermittent "Had trouble renaming file" message in the log | ||||
| Description | Clustered servers (with cluster.lock.enabled=true) using extract in background and a shared staging location will see sometimes see a message like this in the log: "Had trouble renaming file. The current name is \\fileserver\symmetric\corp\outgoing\common\0225632988.create and the desired state was DONE" The theory is that their is contention between the servers (which we guard against with atomic lock files), but the exact cause is not known. This change adds logging indicating if the target file already exists in this situation, and it's file size and modified time. If the 2 files' byte sizes match, the server will proceed assuming that another process already renamed the file. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2018-06-29 17:06 | mmichalek | New Issue | |
| 2018-06-29 17:06 | mmichalek | Status | new => assigned |
| 2018-06-29 17:06 | mmichalek | Assigned To | => mmichalek |
| 2018-06-29 17:07 | mmichalek | Status | assigned => resolved |
| 2018-06-29 17:07 | mmichalek | Resolution | open => fixed |
| 2018-06-29 17:07 | mmichalek | Fixed in Version | => 3.8.37 |
| 2018-06-29 17:08 | mmichalek | Issue cloned: 0003617 | |
| 2018-06-29 17:19 | mmichalek | Relationship added | related to 0003617 |
| 2018-06-29 18:00 | mmichalek | Changeset attached | => SymmetricDS 3.8 475a6c72 |
| 2018-07-23 15:13 | mmichalek | Status | resolved => closed |