Data Infrastructure Management Software Discussions

Re: Slow workflow execution

Hi Sinaa,

Was there a change on Netappp side? I have to change to v3.0 because compatibility with ocum 6.2 and the slowdown problem reoccurs, event certificate unchecked.

I tried to play with bug solution 802749 and standalone-full.xml. When I removed lines, the WFA server service won't to start any more.

For HTTP: <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" executor="http-executor"/>
For HTTPS: <connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true" executor="http-executor">

 

 

François

Re: Slow workflow execution

Francois:

 

Thanks for your reply.

Are you still facing the slow execution problem with WFA 3.0?


Regards

Abhi

Re: Slow workflow execution

Hello abhit,

 

Yes the problem reappears since ver 3.0, the workaround worked for 2.x version but not works in the last version.

An example for a simple clone take 98 sec to complete., before in 10 sec.

 

09:36:01.626 INFO [ITS Clone volume on Last Snapshot] ### Command 'ITS Clone volume on Last Snapshot' ### 09:36:03.048 INFO [ITS Clone volume on Last Snapshot] Get-WfaCredentials -Host 10.139.32.75

09:36:03.126 INFO [ITS Clone volume on Last Snapshot] Credentials successfully provided for '10.139.32.75'

09:36:03.235 INFO [ITS Clone volume on Last Snapshot] Connect-NaController (with credentials) -Name 10.139.32.75 -Timeout 60000 -ErrorAction Stop -HTTP 09:36:04.188 INFO [ITS Clone volume on Last Snapshot] Connected to controller 09:36:54.345 INFO [ITS Clone volume on Last Snapshot] Create a clone for Volume sge_fcp_mssql_gdc01467_01 , named sge_fcp_mssql_gdc01840_01_clone

09:37:40.049 INFO [ITS Clone volume on Last Snapshot] Command completed, took 98423 milliseconds

 

François

Re: Slow workflow execution

Hi Francois:

 

Sorry to hear that the issue is reappearing.

We have opened a bug in our tracking system.

The number is 909331.

We have not observed this internally, so we may ask you to share

some more information if we require.

 

Regards

Abhi

Re: Slow workflow execution

Francois,

          I've not tried removing the http-executors in wfa3.0. If that is the case, I'm not sure.

 

 I can suggest another thing which has worked for some others.

 

Upgrade your .NET version to 4.5 or later. Then after run the .NET repair tool from here.

 

http://www.microsoft.com/en-us/download/details.aspx?id=30135

 

Do it even if the .NET upgrade went fine and didn't throw any errors. Just download the repair tool and run it

 

 

sinhaa

 

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Re: Slow workflow execution

Hello sinhaa,

Yes I did, but after removing this key, I cannot start WFA server service any more.

For .NET I run WFA on W2K12R2 so 4.5 is installed as feature already.

François

Re: Slow workflow execution

 

Re: Slow workflow execution

Francois,

 

         Run the .NET repair tool and see if it helps.

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

Re: Slow workflow execution

NetApp

Hi Franc,

 

This is a custom command. Is it possible to provide the custom command? This will help with RCA.

Re: Slow workflow execution

Hi,

I did some new tests again and it'seems the speed is back to normal now,  probably the FAS6240 has to much activities during the first of test.

WFA is not involved in the slowness.

 

14:38:48.051 INFO [Clone volume] ### Command 'Clone volume' ### 14:38:49.395 INFO [Clone volume] Using cached controller connection 14:38:51.098 INFO [Clone volume] Create a clone for Volume vol_source , named vol_source_clone 14:38:52.145 INFO [Clone volume] Command completed, took 4094 milliseconds

 

Apologize, my mistake.

 

François

Forums