View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0005642 | SymmetricDS Pro | Bug | public | 2022-12-23 18:19 | 2022-12-27 17:25 |
Reporter | pmarzullo | Assigned To | pmarzullo | ||
Priority | normal | ||||
Status | closed | Resolution | fixed | ||
Product Version | 3.14.3 | ||||
Target Version | 3.14.4 | Fixed in Version | 3.14.4 | ||
Summary | 0005642: Console Table Stats inserts do not take into account a clustered environment | ||||
Description | When the ProConsoleService saves the sym_console_table_stats, it always inserts records, assuming that no other node in the cluster is saving the same record (for the same table/event type/start and end time). The service should either catch the duplicate key exception and try an update, adding the new values with the existing values in the database, or the service should attempt an update and if it does not update any rows, then it attempts an insert. I am leaning toward the insert first, catch duplicate key exception, then update. | ||||
Steps To Reproduce | 1. Set up a clustered environment. 2. Synch an insert into a table to a target node from one of the nodes in the cluster. 3. Synch another insert into a table to a target node from the other node in the cluster within the same time interval (every 5 minutes). 4. Duplicate key exception should occur when the statistics are flushed to the database. | ||||
Tags | statistics | ||||
Date Modified | Username | Field | Change |
---|---|---|---|
2022-12-23 18:19 | pmarzullo | New Issue | |
2022-12-23 18:19 | pmarzullo | Status | new => assigned |
2022-12-23 18:19 | pmarzullo | Assigned To | => pmarzullo |
2022-12-23 18:19 | pmarzullo | Tag Attached: statistics | |
2022-12-23 18:25 | pmarzullo | Steps to Reproduce Updated | View Revisions |
2022-12-27 17:25 | pmarzullo | Status | assigned => resolved |
2022-12-27 17:25 | pmarzullo | Resolution | open => fixed |
2022-12-27 17:25 | pmarzullo | Fixed in Version | => 3.14.4 |
2023-01-16 20:59 | admin | Status | resolved => closed |