search

CBIIT / R-cometsAnalytics

R package development for COMETS Analytics
12 stars 10 forks source link

COMETS 1.3. Amazon queue not managed correctly if 3+ jobs #60

Closed steven-moore closed 6 years ago

steven-moore commented 6 years ago

I tested this by running two jobs, logging out, and testing a third job. The first two ran fine, but the third did not, and returned the error below the dotted line. I have tested this a few times today with consistent results.

If the system is maxed out, we should at least send a different, more specific e-mail message. Along the lines of "Apologies, but the queue for data analysis in COMETS-Analytics was at its maximum capacity when you submitted your data. Please try again."

Dear COMETS user,

Due to an unexpected error, no meaningful results could be provided. Please contact the COMETS Web Tool team for assistance in resolving the issue.

Respectfully,

COMETS Web Tool

kailingchen commented 6 years ago

Noted. Will have Brian investigate and also change the email text for clarity.

steven-moore commented 6 years ago

The management of competing tasks on the test site is different than for the production site. This should be fixed when switching to production.

Thus, this is to be retested after production of COMETS 1.3 and, if the issue continues, would be fixed in COMETS 1.4.

kailingchen commented 6 years ago

As described by Steve above, this issue should not happen in production. The production environment has 2 servers , one is the web server to process website requests and one is the queue processor to process supper-batch job. All the super-batch jobs will be queued and processed sequentially so it will never exceed the number of concurrent processes. In the test site, there is only one server to process both website requests and super-batch jobs.