Duplicate LexoRank

My JIRA instance is reporting this error - "com.atlassian.greenhopper.manager.lexorank.LexoRankIntegrityException: Expected exactly one rank row for issue[id=14426] for rank field[id=10010], but found 2 rows"

The customfieldtypekey and customfieldsearchkey for both the Rank field are different.  They are namely

                                      customfieldtypekey                                            customfieldsearchkey

  1.  Rank  - 'com.pyxis.greenhopper.jira:gh-lexo-rank'       'com.pyxis.greenhopper.jira:gh-lexo-rank-searcher'
  2.  Rank  - 'com.pyxis.greenhopper.jira:gh-global-rank'  'com.pyxis.greenhopper.jira:gh-global-rank-searcher'

Which one of the above is correct and should be used?  Can I safely remove the other field from DB?

Thanks and Regards,

Krishnan

2 answers

Which versions of JIRA and Agile are you running?  I was running JIRA 6.1.6 and agile 6.6 and encountered something similar.  Look at https://jira.atlassian.com/browse/GHS-10985 to see if you are running into this problem.  Also, you should check your logs at the system startup and look at the JIRA Agile upgrade task list.  It should look something like this:

*********************************************************************************
Atlassian GreenHopper v6.6.0 #93a1b57e25e0dce3 built 2014-09-04T23:33:50.168-05:00 - plugin starting...
*********************************************************************************

2015-01-05 07:17:36,419 localhost-startStop-1 INFO      [atlassian.plugin.util.WaitUntil] Plugins that have yet to be enabled: [com.pyxis.greenhopper.jira], 49 seconds remaining
2015-01-05 07:17:36,476 ThreadPoolAsyncTaskExecutor::Thread 10 INFO      [greenhopper.service.logging.LogSupport] 

JIRA Agile Run History

	JIRA Agile v6.0.3 (7c31b4aebd6b) started at 25 Sep 2012 11:28

	JIRA Agile v6.0.4 (6756d493ba04) started at 05 Oct 2012 09:05

	JIRA Agile v6.3.2.2 (e316d185c9bc) started at 15 Nov 2013 10:01

	JIRA Agile v6.3.8.1 (945bd0338f1552db) started at 24 Feb 2014 09:36

	JIRA Agile v6.3.9.2 (29c9aad9f89f10a2) started at 18 Mar 2014 10:02

	*JIRA Agile v6.6.0 (93a1b57e25e0dce3) started at 15 Sep 2014 08:11


2015-01-05 07:17:36,605 ThreadPoolAsyncTaskExecutor::Thread 10 INFO      [greenhopper.service.logging.LogSupport] 

The following JIRA Agile upgrade tasks have been run on this system

	JAG UpgradeTask  12 started at 25 Sep 2012 11:28 within JAG v6.0.3 (7c31b4aebd6b)
	JAG UpgradeTask  12 ended   at 25 Sep 2012 11:28 within JAG v6.0.3 (7c31b4aebd6b) and took 16025 ms
	JAG UpgradeTask  13 started at 25 Sep 2012 11:28 within JAG v6.0.3 (7c31b4aebd6b)
	JAG UpgradeTask  13 ended   at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b) and took 48102 ms
	JAG UpgradeTask  14 started at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b)
	JAG UpgradeTask  14 ended   at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b) and took 0 ms
	JAG UpgradeTask  15 started at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b)
	JAG UpgradeTask  15 ended   at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b) and took 971 ms
	JAG UpgradeTask  16 started at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b)
	JAG UpgradeTask  16 ended   at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b) and took 6 ms
	JAG UpgradeTask  17 started at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b)
	JAG UpgradeTask  17 ended   at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b) and took 917 ms
	JAG UpgradeTask  18 started at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b)
	JAG UpgradeTask  18 ended   at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b) and took 2 ms
	JAG UpgradeTask  19 started at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b)
	JAG UpgradeTask  19 ended   at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b) and took 25 ms
	JAG UpgradeTask  20 started at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b)
	JAG UpgradeTask  20 ended   at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b) and took 4 ms
	JAG UpgradeTask  21 started at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b)
	JAG UpgradeTask  21 ended   at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b) and took 4 ms
	JAG UpgradeTask  22 started at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b)
	JAG UpgradeTask  22 ended   at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b) and took 60 ms
	JAG UpgradeTask  23 started at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b)
	JAG UpgradeTask  23 ended   at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b) and took 3 ms
	JAG UpgradeTask  24 started at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b)
	JAG UpgradeTask  24 ended   at 25 Sep 2012 11:29 within JAG v6.0.3 (7c31b4aebd6b) and took 4 ms
	JAG UpgradeTask  25 started at 15 Nov 2013 10:01 within JAG v6.3.2.2 (e316d185c9bc)
	JAG UpgradeTask  25 ended   at 15 Nov 2013 10:01 within JAG v6.3.2.2 (e316d185c9bc) and took 1270 ms
	JAG UpgradeTask  26 started at 15 Nov 2013 10:01 within JAG v6.3.2.2 (e316d185c9bc)
	JAG UpgradeTask  26 ended   at 15 Nov 2013 10:02 within JAG v6.3.2.2 (e316d185c9bc) and took 69029 ms
	JAG UpgradeTask  27 started at 15 Nov 2013 10:02 within JAG v6.3.2.2 (e316d185c9bc)
	JAG UpgradeTask  27 ended   at 15 Nov 2013 10:02 within JAG v6.3.2.2 (e316d185c9bc) and took 1110 ms
	JAG UpgradeTask  28 started at 15 Nov 2013 10:02 within JAG v6.3.2.2 (e316d185c9bc)
	JAG UpgradeTask  28 ended   at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc) and took 68163 ms
	JAG UpgradeTask  29 started at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc)
	JAG UpgradeTask  29 ended   at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc) and took 1236 ms
	JAG UpgradeTask  30 started at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc)
	JAG UpgradeTask  30 ended   at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc) and took 10 ms
	JAG UpgradeTask  31 started at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc)
	JAG UpgradeTask  31 ended   at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc) and took 689 ms
	JAG UpgradeTask  32 started at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc)
	JAG UpgradeTask  32 ended   at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc) and took 31905 ms
	JAG UpgradeTask  33 started at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc)
	JAG UpgradeTask  33 ended   at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc) and took 1004 ms
	JAG UpgradeTask  34 started at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc)
	JAG UpgradeTask  34 ended   at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc) and took 5655 ms
	JAG UpgradeTask  35 started at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc)
	JAG UpgradeTask  35 ended   at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc) and took 1067 ms
	JAG UpgradeTask  36 started at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc)
	JAG UpgradeTask  36 ended   at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc) and took 6 ms
	JAG UpgradeTask  37 started at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc)
	JAG UpgradeTask  37 ended   at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc) and took 3725 ms
	JAG UpgradeTask  38 started at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc)
	JAG UpgradeTask  38 ended   at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc) and took 15 ms
	JAG UpgradeTask  39 started at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc)
	JAG UpgradeTask  39 ended   at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc) and took 484 ms
	JAG UpgradeTask  40 started at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc)
	JAG UpgradeTask  40 ended   at 15 Nov 2013 10:04 within JAG v6.3.2.2 (e316d185c9bc) and took 3674 ms
	JAG UpgradeTask  41 started at 24 Feb 2014 09:36 within JAG v6.3.8.1 (945bd0338f1552db)
	JAG UpgradeTask  41 ended   at 24 Feb 2014 09:36 within JAG v6.3.8.1 (945bd0338f1552db) and took 1846 ms
	JAG UpgradeTask  42 started at 18 Mar 2014 10:06 within JAG v6.3.9.2 (29c9aad9f89f10a2)
	JAG UpgradeTask  42 ended   at 18 Mar 2014 10:06 within JAG v6.3.9.2 (29c9aad9f89f10a2) and took 2997 ms
	JAG UpgradeTask  43 started at 15 Sep 2014 08:13 within JAG v6.6.0 (93a1b57e25e0dce3)
	JAG UpgradeTask  43 ended   at 15 Sep 2014 08:13 within JAG v6.6.0 (93a1b57e25e0dce3) and took 52 ms
	JAG UpgradeTask  44 started at 15 Sep 2014 08:13 within JAG v6.6.0 (93a1b57e25e0dce3)
	JAG UpgradeTask  44 ended   at 15 Sep 2014 08:13 within JAG v6.6.0 (93a1b57e25e0dce3) and took 14310 ms
	JAG UpgradeTask  45 started at 15 Sep 2014 08:13 within JAG v6.6.0 (93a1b57e25e0dce3)
	JAG UpgradeTask  45 ended   at 15 Sep 2014 08:13 within JAG v6.6.0 (93a1b57e25e0dce3) and took 1163 ms

If you had a failed upgrade, then you should see an UpgradeTask that was started, but never ended.

This kb page also has some instructions for identifying which lexo rank field is trying to be used, so it may be of some help as well.  Cannot reindex jira due to Expected exactly 2 rows the maximum marker row and the lowest ranked row for rank field

0 vote

Ok, there's a couple of things...

First, have a look at the versions of Java, JIRA and Agile in use - you may be being affected by https://jira.atlassian.com/browse/JRA-36857

Secondly, see https://confluence.atlassian.com/display/AGILEKB/Indexing+Failed+with+RuntimeException+Expected+exactly+one+rank for identifying and fixing it, even if you aren't hit by that bug.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Sunday in Agility

You asked for it, so we delivered: images on issues have arrived

A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...

793 views 3 11
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you