| Bug #11019 | mgmapi start backup in some cases returns wrong backupid | ||
|---|---|---|---|
| Submitted: | 1 Jun 2005 16:02 | Modified: | 13 Jun 2005 17:35 |
| Reporter: | Tomas Ulin | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
| Version: | 5.0 -> | OS: | Any (any) |
| Assigned to: | Tomas Ulin | CPU Architecture: | Any |
[1 Jun 2005 21:13]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/25482
[1 Jun 2005 21:15]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/25483

Description: int rtc = ndb_mgm_start_backup(h, 0, &backup_id, &reply); returns wrong backup_id workaround, use: int rtc = ndb_mgm_start_backup(h, 1, &backup_id, &reply); or int rtc = ndb_mgm_start_backup(h, 2, &backup_id, &reply); The above will not be fixed... but documentaion will be updated. Behaviour will change as not to update the backup_id at all in the first case How to repeat: see above