Project

General

Profile

Actions
Copy link

Bug #4943

closed

[Workbench] [Performance] Combining big collections should start returning a response faster (currently you can get a 502 proxy error even if the collection still combines)

Added by Bryan Cosca almost 10 years ago. Updated 9 months ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
Workbench
Target version:
Future
Story points:
-
Release:
Postponed
Release relationship:
Auto

Description

i.e. I combined qr1hi-4zz18-ms5x87xf1389ldv + qr1hi-4zz18-0q225z4ktr432mg + qr1hi-4zz18-i5o4ba4mmxub69b and encountered a bad gateway error but then i found qr1hi-4zz18-7c0e8fyo871279e in my project.

I thought this was interesting because if I encountered any error while doing this, I thought the whole process would stop... but it didn't.

Proposed resolution

Once #5781 closes, Workbench should use those new API methods instead of [using the Ruby SDK] to manipulate the manifest itself.

Related issues

Related to Arvados - Bug #4953: [Workbench] [dup] Time out error for renaming a collection with a lot (300+?) filesResolved01/09/2015Actions
Related to Arvados - Bug #5096: [Workbench] Avoid passing manifest_text around the network too much when updating and merging large collections.ResolvedRadhika Chippada02/14/2015Actions
Related to Arvados - Feature #5104: [SDKs] Add Ruby SDK methods for manipulating collection contents (rename, delete, copy file from another collection)ResolvedBrett Smith03/08/2015Actions
Related to Arvados - Bug #5614: [Workbench] 504 error returned when trying to create a large new collectionNewActions
Blocked by Arvados - Idea #5781: [API] [DRAFT] Provide API methods for manipulating and combining collectionsResolved04/21/2015Actions
Actions
Copy link
 #1

Updated by Bryan Cosca almost 10 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Tom Clegg almost 10 years ago

  • Subject changed from Combining big collections results in a 502 error but the collection still combines to [Workbench] Combining big collections should be faster (currently you can get a 502 proxy error even if the collection still combines)
Actions
Copy link
 #3

Updated by Brett Smith almost 10 years ago

  • Subject changed from [Workbench] Combining big collections should be faster (currently you can get a 502 proxy error even if the collection still combines) to [Workbench] Combining big collections should start returning a response faster (currently you can get a 502 proxy error even if the collection still combines)
  • Category set to Workbench
  • Target version set to Bug Triage
Actions
Copy link
 #4

Updated by Brett Smith almost 10 years ago

  • Target version deleted (Bug Triage)
Actions
Copy link
 #5

Updated by Tom Clegg almost 10 years ago

  • Tracker changed from Idea to Bug
Actions
Copy link
 #6

Updated by Tom Clegg over 9 years ago

  • Target version set to Arvados Future Sprints
Actions
Copy link
 #7

Updated by Tom Clegg over 9 years ago

  • Description updated (diff)
Actions
Copy link
 #8

Updated by Radhika Chippada over 9 years ago

  • Subject changed from [Workbench] Combining big collections should start returning a response faster (currently you can get a 502 proxy error even if the collection still combines) to [Workbench] [Performance] Combining big collections should start returning a response faster (currently you can get a 502 proxy error even if the collection still combines)
Actions
Copy link
 #9

Updated by Ward Vandewege over 3 years ago

  • Target version deleted (Arvados Future Sprints)
Actions
Copy link
 #10

Updated by Peter Amstutz almost 2 years ago

  • Release set to 60
Actions
Copy link
 #11

Updated by Peter Amstutz 9 months ago

  • Target version set to Future
Actions
Copy link
 #12

Updated by Peter Amstutz 9 months ago

  • Status changed from New to Closed
Actions
Copy link

Also available in: Atom PDF