View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002825 | SymmetricDS | Bug | public | 2016-09-22 19:59 | 2016-09-30 01:01 |
| Reporter | mmichalek | Assigned To | mmichalek | ||
| Priority | normal | ||||
| Status | closed | Resolution | fixed | ||
| Product Version | 3.8.5 | ||||
| Target Version | 3.8.5 | Fixed in Version | 3.8.5 | ||
| Summary | 0002825: Data with ID = 0 is routed perpetually when using DataGapFastDetector | ||||
| Description | In the unusual situation where a data has id of 0, SymmetricDS will route that piece of data over and over, creating a new batch ID each time. This only occurs when using the DataGapFastDetector. This bug was known to happen on HSQLDB, whose IDENTITY counter actually starts at 0 on sym_data. Probably most RDBMS' start at 1, which inherently works around this issue. The issue was that the RouterService would route the data with id 0, but when it tried to notify the ChannelRouterContext, the 0 data id was dropped because "lastDataId" variable was not initialized and was therefore already 0. So the next time around, the DataGapFastDetector didn't know that any data was found at 0, and presented a gap at 0 for the next routing query which would start the cycle over. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-09-22 19:59 | mmichalek | New Issue | |
| 2016-09-22 19:59 | mmichalek | Status | new => assigned |
| 2016-09-22 19:59 | mmichalek | Assigned To | => mmichalek |
| 2016-09-22 20:05 | mmichalek | Status | assigned => resolved |
| 2016-09-22 20:05 | mmichalek | Resolution | open => fixed |
| 2016-09-22 20:05 | mmichalek | Fixed in Version | => 3.8.5 |
| 2016-09-22 21:00 | mmichalek | Changeset attached | => SymmetricDS 3.8 780bb97c |
| 2016-09-30 01:01 | admin | Status | resolved => closed |