] Re: Timeout with live migration
Nice, thanks.
Did that solve your problem? Did you migrate the volume?
On Tue, Oct 13, 2015 at 7:00 PM, Ryan Farrington
wrote:
> Issue #1) Terrible parameter names
> https://issues.apache.org/jira/browse/CLOUDSTACK-8946
>
> Issue #2) Wait value for M
the next ACS
release (4.7?), or even 4.6 if the PR gets accepted.
Please send me the jira ticket as soon as you open it.
On Tue, Oct 13, 2015 at 5:33 PM, Ryan Farrington
wrote:
> Looks like whatever change I made actually resulted in a change in
> behavior. Prior to the change we were se
936343: No more commands found
2015-10-13 15:27:13,397 DEBUG [c.c.a.t.Request] (Job-Executor-1:ctx-8e0ebced
ctx-f49e7503) Seq 38-1788936343: Received: { Ans: , MgmtId: 42756806312036,
via: 38, Ver: v1, Flags: 110, { MigrateVolumeAnswer } }
From: Rafael Weingärtner [
eason that I do not understand, the code is
multiplying the value from that parameter by 2, something like 18000 should
do the tricky
On Tue, Oct 13, 2015 at 12:15 AM, Ryan Farrington wrote:
> Yes i can open JIRA tickets. What would you like for me to do?
>
> I'll be happy to cha
12, 2015 at 11:51 PM, Ryan Farrington wrote:
> wait is currently configured to be 3600
>
>
>
>
> From: Rafael Weingärtner [rafaelweingart...@gmail.com]
> Sent: Monday, October 12, 2015 9:46 PM
> To: users@cloudstack.apache.org
>
check the parameter called "wait", what value is it using ?
On Mon, Oct 12, 2015 at 10:54 PM, Ryan Farrington wrote:
> Yes the parameter was set long ago and the management server has been
> restarted numerous time over the past few days as we played with other
> para
meter is set to 36000 (10 hours) I do not see why you are
getting the exception after 2 hours.
Did you restart the management servers after you changed the parameter?
On Mon, Oct 12, 2015 at 10:31 PM, Ryan Farrington wrote:
> Here is the full log, including the stack for the exception, that
r message you posted does not seem to be related to the
migration timeout; hence, in the code if the copy times out the message
would be:
"Async " + timeout/1000 + " seconds timeout for task " + task.toString()"
Maybe because it throws a "Types.BadAsyncResult(msg)"
e you migrating that volume to a different cluster? or just a different
storage in the same cluster?
What hypervisor are you using ?
On Mon, Oct 12, 2015 at 9:47 PM, Ryan Farrington
wrote:
> Live migrating a data volume. We are purely on shared storage so no loca
: Timeout with live migration
Are you live migrating a VM, or migrating a volume of a stopped VM to a
different primary storage?
If it is a running VM, is the VM allocated in a shared storage or local
storage?
On Mon, Oct 12, 2015 at 9:17 PM, Ryan Farrington
wrote:
> The slow transfer is related
, Jan-Arve Nygård
wrote:
> What version are you running? Check if the copy.volume.wait setting is set
> to 7200 and increase it. If not you could also check
> job.cancel.threshold.minutes and job.expire.minutes.
>
> -Jan-Arve
>
> 2015-10-13 0:46 GMT+02:00 Ryan Farrington :
>
&g
What version are you running? Check if the copy.volume.wait setting is set
to 7200 and increase it. If not you could also check
job.cancel.threshold.minutes and job.expire.minutes.
-Jan-Arve
2015-10-13 0:46 GMT+02:00 Ryan Farrington :
> We are experiencing a failure in cloudstack waiting for
We are experiencing a failure in cloudstack waiting for an async job performing
a live migration of a volume to finish. I've copied the relevant log entries
below.We acknowledge that the migration will take a few hours based on the
volume of the data and we are looking for a way to increase the
13 matches
Mail list logo
