Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Delete large amount of worflow instances

Avatar

Avatar
Validate 10
Level 3
anilkum
Level 3

Likes

3 likes

Total Posts

65 posts

Correct Reply

1 solution
Top badges earned
Validate 10
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 10
Level 3
anilkum
Level 3

Likes

3 likes

Total Posts

65 posts

Correct Reply

1 solution
Top badges earned
Validate 10
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
anilkum
Level 3

29-12-2016

Hi,

I am planning to delete large amount of workflow instances. When I had tried this earlier it had taken more than 17 hours to delete 14506560 nodes. Is there way to speed this up? I was told that this is because of incremental reindexing.. Can we stop incremental reindexing 

Thanks,

Anil

Replies

Avatar

Avatar
Level 1
raja_vijay_sing
Level 1

Likes

0 likes

Total Posts

6 posts

Correct Reply

0 solutions
View profile

Avatar
Level 1
raja_vijay_sing
Level 1

Likes

0 likes

Total Posts

6 posts

Correct Reply

0 solutions
View profile
raja_vijay_sing
Level 1

29-12-2016

Try the jmx console for workflow maintenance, it gives you option to purge workflows

http://localhost:4502/system/console/jmx/com.adobe.granite.workflow%3Atype%3DMaintenance

Avatar

Avatar
Validate 10
Level 3
anilkum
Level 3

Likes

3 likes

Total Posts

65 posts

Correct Reply

1 solution
Top badges earned
Validate 10
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 10
Level 3
anilkum
Level 3

Likes

3 likes

Total Posts

65 posts

Correct Reply

1 solution
Top badges earned
Validate 10
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
anilkum
Level 3

30-12-2016

I tried this and options to count the active, completed workflow. It worked great for those. But I am getting GATEWAY TIMEOUT error in middle of purge operation. I have about a million completed workflows.

Avatar

Avatar
Validate 1
MVP
Runal_Trivedi
MVP

Likes

45 likes

Total Posts

153 posts

Correct Reply

68 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Validate 1
MVP
Runal_Trivedi
MVP

Likes

45 likes

Total Posts

153 posts

Correct Reply

68 solutions
Top badges earned
Validate 1
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile
Runal_Trivedi
MVP

30-12-2016

Not sure if you have tried this, but finish all the running workflows don't trigger any new ones for some time and block all external excess to your server.

Now, go to http://<ip>:<port>/crx/explorer and then make a note of following node /etc/workflow/instances/server0, take a note of all properties on your server<num-val> sling folder node and delete it using crx/explorer view. You can also delete date folders one at a time or delete the parent node which is server<num-val> sling folder.

Considering the number of the nodes you have, the time it will take to delete all the instances of workflow will be high, so make sure you do this using the ip and port URL and not through apache URL if you have one. Apache is probably the one forcing you the gateway timeout error as apache expects the response in timely order.

Once deletion succeeds, then crx/explorer will enable the "Save All" button. Click on "Save all".

Now recreate the folder server<num-val> with exact same properties as were there earlier, ideally only one property needs to be right which is slingId.

Trigger any workflow to make sure that new instances are getting created fine under the newly created folder.

-- Runal