| Key: |
QB-3156
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Mike Cordeiro
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 26/Mar/18 12:35 PM
Updated: 27/Mar/18 05:58 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
8.0.0
|
| Fix Version/s: |
8.0.1
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
File Attachments:
|
1.
loop.txt (5 kb)
|
|
Environment:
|
Windows Server, SQL Server
|
|
|
We ran into an issue upgrading to 8.0 this weekend. It appears that there was not enough memory in the JVM to run the database backup. As a fail safe, QB seems to attempt to reduce the number of rows in a query to attempt to load less into the JVM. However, It seems that even 1 row was too big, which put the backup into an infinite loop writing rows "(17->16)" over and over to a backup file. I would have expected the backup to fail once the end of the range was smaller than the start.
I will attach the relevant portion of the output logs.
|
|
Description
|
We ran into an issue upgrading to 8.0 this weekend. It appears that there was not enough memory in the JVM to run the database backup. As a fail safe, QB seems to attempt to reduce the number of rows in a query to attempt to load less into the JVM. However, It seems that even 1 row was too big, which put the backup into an infinite loop writing rows "(17->16)" over and over to a backup file. I would have expected the backup to fail once the end of the range was smaller than the start.
I will attach the relevant portion of the output logs. |
Show » |
|
Upgrade Failed due to loop in backup