Project

Profile

Help

Issue #943

Btree::insert: key too large to index

Added by Ben.Stanley over 6 years ago. Updated over 2 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
3. High
Version:
2.5
Platform Release:
2.6.1
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
Quarter:

Description

This is a re-bash of an old issue that has already been done to death, but it appears that it is still a problem.

When synching epel on 1 May 2015 I encountered the
Btree::insert: key too large to index
problem.

This issue has been discussed previously:

[[https://bugzilla.redhat.com/show_bug.cgi?id=1175616]]
[[https://bugzilla.redhat.com/show_bug.cgi?id=1178127]]
[[https://bugzilla.redhat.com/show_bug.cgi?id=1161277]]
[[https://fedorahosted.org/epel/ticket/26]]

(I might have missed some links...)

Previous tickets have been CLOSED NOTABUG.
I see now that there is a workaround, which I have not yet tried.

This problem with epel seems to occur regularly. It seems that pulp should handle it, instead of just saying it's somebody else's problem. This just makes pulp a fragile system that needs babysitting, instead of being a responsible and mature product that is able to function robustly come what may.

Robustness is a big issue for me. I currently have ~350 repos. I need pulp to just work, not throw strange error messages hidden deep in the log file that need deep investigation on a regular basis.

epel is an important repo. Pulp itself depends on it. Problems with epel can block upgrading pulp itself.

History

#1 Updated by mhrivnak over 6 years ago

This is actually fixed in 2.6.1, which will be released very soon. It looks like the bug state on this:

https://bugzilla.redhat.com/show_bug.cgi?id=1175616

... is incorrect, and should reflect that it's been fixed. Because of its incorrect state, it looks like it didn't get migrated to redmine when we made that switch recently, so I'm going to leave this open for the moment until we figure out the best way to reconcile the bug states.

#2 Updated by mhrivnak over 6 years ago

  • Status changed from NEW to 6
  • Assignee set to bcourt
  • Priority changed from Normal to High
  • Severity changed from 2. Medium to 3. High
  • Triaged changed from No to Yes
  • Platform Release set to 2.6.1

#3 Updated by dkliban@redhat.com over 6 years ago

  • Status changed from 6 to CLOSED - CURRENTRELEASE

#4 Updated by rbarlow about 6 years ago

  • Project changed from Pulp to RPM Support

#6 Updated by bmbouter over 2 years ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF