Project

General

Profile

Actions
Copy link

Bug #4953

closed

[Workbench] [dup] Time out error for renaming a collection with a lot (300+?) files

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

Status:
Resolved
Priority:
Normal
Assigned To:
-
Category:
Workbench
Target version:
-
Story points:
0.5

Description

Renaming collection qr1hi-4zz18-tcnxylwkxg0nfhi

Refreshing the browser resolves the error.

Files

Download all files
timeouterror.png (12.1 KB) timeouterror.png Bryan Cosca, 01/09/2015 07:17 PM
unparsable-response-big-collection.png (18.5 KB) unparsable-response-big-collection.png Bryan Cosca, 01/09/2015 07:45 PM

Related issues 2 (0 open — 2 closed)

Related to Arvados - Bug #4943: [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)ClosedActions
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
Actions
Copy link
 #1

Updated by Bryan Cosca almost 10 years ago

  • Subject changed from Time out error for renaming a collection with 300+ files to Time out error for renaming a collection with a lot (300+?) files
Actions
Copy link
 #2

Updated by Bryan Cosca almost 10 years ago

It ends up working though by just refreshing the browser

Actions
Copy link
 #3

Updated by Bryan Cosca almost 10 years ago

Actions
Copy link
 #4

Updated by Tim Pierce almost 10 years ago

  • Category set to Workbench
  • Target version set to Bug Triage
Actions
Copy link
 #5

Updated by Tim Pierce almost 10 years ago

  • Subject changed from Time out error for renaming a collection with a lot (300+?) files to [API] Time out error for renaming a collection with a lot (300+?) files
  • Category changed from Workbench to API
Actions
Copy link
 #6

Updated by Tim Pierce almost 10 years ago

  • Description updated (diff)
Actions
Copy link
 #7

Updated by Bryan Cosca almost 10 years ago

some more data points with this collection.

Actions
Copy link
 #8

Updated by Tom Clegg almost 10 years ago

  • Story points set to 0.5
Actions
Copy link
 #9

Updated by Tom Clegg almost 10 years ago

First suspect: Workbench's Collection model should avoid sending the entire manifest_text in the update call, if it hasn't changed. (It might be possible/easier to generalize this to all attributes of all models.)

There might be a JSON encoding/decoding issue as well (although that shouldn't be as big a deal if we aren't passing the manifest_text around needlessly): perhaps Workbench isn't using Oj. See 1974e0e.

Actions
Copy link
 #10

Updated by Tom Clegg almost 10 years ago

  • Category changed from API to Workbench
Actions
Copy link
 #11

Updated by Brett Smith almost 10 years ago

  • Subject changed from [API] Time out error for renaming a collection with a lot (300+?) files to [Workbench] Time out error for renaming a collection with a lot (300+?) files
Actions
Copy link
 #12

Updated by Tom Clegg almost 10 years ago

  • Target version changed from Bug Triage to 2015-02-18 sprint
Actions
Copy link
 #13

Updated by Tom Clegg almost 10 years ago

  • Target version deleted (2015-02-18 sprint)
Actions
Copy link
 #14

Updated by Tom Clegg almost 10 years ago

  • Subject changed from [Workbench] Time out error for renaming a collection with a lot (300+?) files to [Workbench] [dup] Time out error for renaming a collection with a lot (300+?) files
Actions
Copy link
 #15

Updated by Radhika Chippada over 9 years ago

  • Status changed from New to Resolved

This issue as such is resolved by #5218, where the manifest_text is not sent to server when only a name (or description) is being updated.

However, it is still hard to see that name change actually works because the display of the collection itself times out more often than not. #5556 is created regarding the timeout error for collection view itself.

Actions
Copy link

Also available in: Atom PDF