If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 09/Jan/17 04:18 PM
Updated: 09/Jan/17 04:18 PM
|
|
Component/s: |
None
|
Affects Version/s: |
6.1.23
|
Fix Version/s: |
None
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
I found a case where the configuration can end up in error (it will run forever with an error on the configuration).
I have a resource that i use which is linked to a cloudprofile.
My configuration is running 2 parallel tasks at the same time thus spawning 2 VM with the same configuration (so 2 nodes in QB).
The idle time on the CloudProfile is 1h.
The thing is that one process is really longer than the other.
So what happens is :
- 2 nodes are spawned
- Node A is running a very long step / Node B is running on parallel a slightly shorter
- Node B finishes its step and is now idle
- Noda A runs an extra 1h so Node B gets terminated
And now the configuration cannot find Node B anymore and is in error
|
Description
|
I found a case where the configuration can end up in error (it will run forever with an error on the configuration).
I have a resource that i use which is linked to a cloudprofile.
My configuration is running 2 parallel tasks at the same time thus spawning 2 VM with the same configuration (so 2 nodes in QB).
The idle time on the CloudProfile is 1h.
The thing is that one process is really longer than the other.
So what happens is :
- 2 nodes are spawned
- Node A is running a very long step / Node B is running on parallel a slightly shorter
- Node B finishes its step and is now idle
- Noda A runs an extra 1h so Node B gets terminated
And now the configuration cannot find Node B anymore and is in error
|
Show » |
No work has yet been logged on this issue.
|
|