Bug 1008333 – Impact of Indices applied on JBPM tables

Bug 1008333 - Impact of Indices applied on JBPM tables

Summary:	Impact of Indices applied on JBPM tables

Status:	NEW

Aliases:	None

Product:	JBoss Enterprise SOA Platform 4
Classification:	JBoss
Component:	JBPM - within SOA (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	unspecified Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Default User
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2013-09-16 03:55 EDT by jadhavpprasad
Modified:	2013-10-24 00:26 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	Task
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description jadhavpprasad 2013-09-16 03:55:42 EDT

I found deadlock issue while deleting process instance in multi-user environment.
As suggested one of the forum of RED-HAT i have created indices. here is URL of forum
https://access.redhat.com/site/documentation/en-US/JBoss_Enterprise_SOA_Platform/4.2/html/4.2.CP04_Release_Notes/sect-manually_create_jBPM_indexes_when_upgrading.html

After applying these indices deadlock issue resolved for me.

My questions are:
1. How much database size will increase after applying these indices?
2. What will be impact on insertion operations such as Create Process Instance and Execute Transitions operations?

Note You need to log in before you can comment on or make changes to this bug.