DTM recovery causes issue if tables with outstanding transactions are dropped.
Bug #1395205 reported by
Guy Groulx
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Trafodion |
Fix Released
|
Critical
|
Sean Broeder | ||
Bug Description
Transaction recovery may not work properly if tables that have outstanding transactions are dropped.
Recovery includes information in zookeeper which may not be cleaned up if tables are dropped.
For recovery purposes, we dropped all trafodion tables via hbase and then issues initialize trafodion thinking we would start fresh. Since this did not clean up the info in zookeeper, the DTM recovery process ran into issues.
| Changed in trafodion: | |
| assignee: | nobody → Shang-Sheng Tung (shang-sheng-tung) |
| milestone: | none → r1.0 |
| Changed in trafodion: | |
| status: | New → In Progress |
Revision history for this message
| Atanu Mishra (atanu-mishra) wrote | #1 |
| Changed in trafodion: | |
| assignee: | Shang-Sheng Tung (shang-sheng-tung) → Sean Broeder (sean-broeder) |
| importance: | High → Critical |
Revision history for this message
| Sean Broeder (sean-broeder) wrote | #2 |
| Changed in trafodion: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Ensure this is addressed in r1.0