You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi
Have Jira software Installed in my 1 production and 1 development environment I would like to know how to import production Insights into the development environment. When I try to do it through the normal step-by-step (Object Schema Import) I get the message
" Insight batch process(es) in progress. Is aware that update, disable or uninstall the Insight can cause data inconsistency. Please wait until the processes are completed before making modifications to the Insight. "
Resource: insight-reindex (reindex), Description: Insight Reindex, Percentage: 0%
And do not get out of this can help me.
Awaiting
João Bispo
If i'm not wrong, this is due to Insight Indexing during every restart of Jira.
Insight batch process(es) are running. Be aware that upgrading, disabling or uninstalling Insight may cause data inconsistency please wait until the process(es) are completed before performing any of these changes to Insight.
Resource: freetext-reindex (freetext), Description: Re-index, Percent: 30%
On Jira shutdown Insight persists the index on disk for faster startup. In large instances, the index file fails to be saved on disk in time before the force shutdown command is sent. This will cause Insight to do a database reindex on each startup. To prevent this change, you need to change the timeout on force shutdown in the stop-jira script.
Change the value 20 (the unit is seconds) to a value that is more reasonable based on the amount of data in your installation. Below is a snippet from the standard Jira stop-jira.sh and it is the value 20 that should be changed at two places.
if [ -z "$JIRA_USER" ] || [ $(id -un) == "$JIRA_USER" ]; then
echo executing as current user
exec $PRGDIR/shutdown.sh 20 -force $@
elif [ $UID -ne 0 ]; then
echo JIRA has been installed to run as $JIRA_USER so please sudo run this to enable switching to that user
exit 1
else
echo executing using dedicated user
if [ -x "/sbin/runuser" ]; then
sucmd="/sbin/runuser"
else
sucmd="su"
fi
$sucmd -m $JIRA_USER -c "$PRGDIR/shutdown.sh 20 -force $@"
fi
Having this checked out on our install, see if it makes an improvement :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.