[jira] [Closed] (AIRAVATA-3464) Experiment id lengths can grow exponentially causing other services to crash

[ https://issues.apache.org/jira/browse/AIRAVATA-3464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-3464. - Resolution: Fixed > Experiment id lengths can grow exponentially causing other

[jira] [Created] (AIRAVATA-3464) Experiment id lengths can grow exponentially causing other services to crash

Dimuthu Upeksha created AIRAVATA-3464: - Summary: Experiment id lengths can grow exponentially causing other services to crash Key: AIRAVATA-3464 URL: https://issues.apache.org/jira/browse/AIRAVATA-3464

[jira] [Closed] (AIRAVATA-3391) Groovey variables not resolved in Environment variable section but only in Prejob Command

[ https://issues.apache.org/jira/browse/AIRAVATA-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-3391. - Assignee: Dimuthu Upeksha Resolution: Fixed > Groovey variables not resolved in

[jira] [Commented] (AIRAVATA-3391) Groovey variables not resolved in Environment variable section but only in Prejob Command

[ https://issues.apache.org/jira/browse/AIRAVATA-3391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17239842#comment-17239842 ] Dimuthu Upeksha commented on AIRAVATA-3391: --- Fixed in 

[jira] [Closed] (AIRAVATA-3378) Standard out and error file names mentioned in batch scripts contains invalid characters

[ https://issues.apache.org/jira/browse/AIRAVATA-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-3378. - Resolution: Fixed > Standard out and error file names mentioned in batch scripts

[jira] [Commented] (AIRAVATA-3378) Standard out and error file names mentioned in batch scripts contains invalid characters

[ https://issues.apache.org/jira/browse/AIRAVATA-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17213470#comment-17213470 ] Dimuthu Upeksha commented on AIRAVATA-3378: --- Fixed in 

[jira] [Created] (AIRAVATA-3378) Standard out and error file names mentioned in batch scripts contains invalid characters

Dimuthu Upeksha created AIRAVATA-3378: - Summary: Standard out and error file names mentioned in batch scripts contains invalid characters Key: AIRAVATA-3378 URL:

[jira] [Commented] (AIRAVATA-3372) BUG: Saved experiment cannot be edited and launch

[ https://issues.apache.org/jira/browse/AIRAVATA-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17201664#comment-17201664 ] Dimuthu Upeksha commented on AIRAVATA-3372: --- Restart helix stack ./helix-stop.sh

[jira] [Resolved] (AIRAVATA-3300) Implement the new XSEDE usage reporting in Helix

[ https://issues.apache.org/jira/browse/AIRAVATA-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-3300. --- Resolution: Fixed > Implement the new XSEDE usage reporting in Helix >

[jira] [Commented] (AIRAVATA-3300) Implement the new XSEDE usage reporting in Helix

[ https://issues.apache.org/jira/browse/AIRAVATA-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17050554#comment-17050554 ] Dimuthu Upeksha commented on AIRAVATA-3300: --- Fixed in 

[jira] [Updated] (AIRAVATA-3300) Implement the new XSEDE usage reporting in Helix

[ https://issues.apache.org/jira/browse/AIRAVATA-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha updated AIRAVATA-3300: -- Attachment: image-2020-03-03-15-51-02-840.png > Implement the new XSEDE usage

[jira] [Updated] (AIRAVATA-3300) Implement the new XSEDE usage reporting in Helix

[ https://issues.apache.org/jira/browse/AIRAVATA-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha updated AIRAVATA-3300: -- Attachment: Screen Shot 2020-03-03 at 3.48.05 PM.png > Implement the new XSEDE

[jira] [Created] (AIRAVATA-3293) Job - JobStatus entity mapping issue

Dimuthu Upeksha created AIRAVATA-3293: - Summary: Job - JobStatus entity mapping issue Key: AIRAVATA-3293 URL: https://issues.apache.org/jira/browse/AIRAVATA-3293 Project: Airavata Issue

[jira] [Created] (AIRAVATA-3292) Post workflow manager fails to poll from kafka

Dimuthu Upeksha created AIRAVATA-3292: - Summary: Post workflow manager fails to poll from kafka Key: AIRAVATA-3292 URL: https://issues.apache.org/jira/browse/AIRAVATA-3292 Project: Airavata

[jira] [Commented] (AIRAVATA-3276) BUG: non uploaded files argument appears in command-line in job script

[ https://issues.apache.org/jira/browse/AIRAVATA-3276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17007712#comment-17007712 ] Dimuthu Upeksha commented on AIRAVATA-3276: --- Fixed in 

[jira] [Commented] (AIRAVATA-3287) Evict failed SSH connections from connection pool

[ https://issues.apache.org/jira/browse/AIRAVATA-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17007673#comment-17007673 ] Dimuthu Upeksha commented on AIRAVATA-3287: --- Fixed in 

[jira] [Resolved] (AIRAVATA-3287) Evict failed SSH connections from connection pool

[ https://issues.apache.org/jira/browse/AIRAVATA-3287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-3287. --- Resolution: Fixed > Evict failed SSH connections from connection pool >

[jira] [Created] (AIRAVATA-3287) Evict failed SSH connections from connection pool

Dimuthu Upeksha created AIRAVATA-3287: - Summary: Evict failed SSH connections from connection pool Key: AIRAVATA-3287 URL: https://issues.apache.org/jira/browse/AIRAVATA-3287 Project: Airavata

[jira] [Commented] (AIRAVATA-3282) To get output files not at a top level and preserve the hierarchy potentially

[ https://issues.apache.org/jira/browse/AIRAVATA-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16990146#comment-16990146 ] Dimuthu Upeksha commented on AIRAVATA-3282: --- Fixed in 

[jira] [Resolved] (AIRAVATA-3259) Implement: Increase the maximum size restriction fro Archive directory and also show in MB

[ https://issues.apache.org/jira/browse/AIRAVATA-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-3259. --- Resolution: Fixed > Implement: Increase the maximum size restriction fro Archive

[jira] [Commented] (AIRAVATA-3259) Implement: Increase the maximum size restriction fro Archive directory and also show in MB

[ https://issues.apache.org/jira/browse/AIRAVATA-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16966827#comment-16966827 ] Dimuthu Upeksha commented on AIRAVATA-3259: --- [Fixed in

[jira] [Created] (AIRAVATA-3170) Multiple Zookeeper client connections are created when WorkflowCancellationTask is initialized

Dimuthu Upeksha created AIRAVATA-3170: - Summary: Multiple Zookeeper client connections are created when WorkflowCancellationTask is initialized Key: AIRAVATA-3170 URL:

[jira] [Commented] (AIRAVATA-3051) Output files configured with wildcard is not brought back and displayed in the Django summary page.

[ https://issues.apache.org/jira/browse/AIRAVATA-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16854145#comment-16854145 ] Dimuthu Upeksha commented on AIRAVATA-3051: --- Fixed in 

[jira] [Assigned] (AIRAVATA-3051) Output files configured with wildcard is not brought back and displayed in the Django summary page.

[ https://issues.apache.org/jira/browse/AIRAVATA-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha reassigned AIRAVATA-3051: - Assignee: Dimuthu Upeksha (was: Marcus Christie) > Output files configured

[jira] [Commented] (AIRAVATA-2829) Job and experiment both completed as expected but STDOUT is not available as an output in the gateway

[ https://issues.apache.org/jira/browse/AIRAVATA-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832664#comment-16832664 ] Dimuthu Upeksha commented on AIRAVATA-2829: --- [~eroma_a] can you verify this with latest

[jira] [Closed] (AIRAVATA-2807) Helix: use groupResourceProfileId on ProcessModel

[ https://issues.apache.org/jira/browse/AIRAVATA-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-2807. - Resolution: Fixed > Helix: use groupResourceProfileId on ProcessModel >

[jira] [Commented] (AIRAVATA-2749) Experiment status not updated, but job is COMPLETED and outputs are staged.

[ https://issues.apache.org/jira/browse/AIRAVATA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832643#comment-16832643 ] Dimuthu Upeksha commented on AIRAVATA-2749: --- Fixed in latest improvements. Please reopen if

[jira] [Closed] (AIRAVATA-2749) Experiment status not updated, but job is COMPLETED and outputs are staged.

[ https://issues.apache.org/jira/browse/AIRAVATA-2749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-2749. - Resolution: Fixed > Experiment status not updated, but job is COMPLETED and outputs

[jira] [Closed] (AIRAVATA-2955) Helix controller does not get stopped when server is stopped. Had to kill the process to stop the server

[ https://issues.apache.org/jira/browse/AIRAVATA-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-2955. - Resolution: Fixed > Helix controller does not get stopped when server is stopped. Had

[jira] [Commented] (AIRAVATA-2955) Helix controller does not get stopped when server is stopped. Had to kill the process to stop the server

[ https://issues.apache.org/jira/browse/AIRAVATA-2955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832641#comment-16832641 ] Dimuthu Upeksha commented on AIRAVATA-2955: --- Fixed in 

[jira] [Closed] (AIRAVATA-3022) When an experiment is launched twice (user clicks Launch button twice) the experiment is tagged as FAILED where as the job submission proceeds.

[ https://issues.apache.org/jira/browse/AIRAVATA-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-3022. - Resolution: Fixed > When an experiment is launched twice (user clicks Launch button

[jira] [Commented] (AIRAVATA-3022) When an experiment is launched twice (user clicks Launch button twice) the experiment is tagged as FAILED where as the job submission proceeds.

[ https://issues.apache.org/jira/browse/AIRAVATA-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832591#comment-16832591 ] Dimuthu Upeksha commented on AIRAVATA-3022: --- Fixed in 

[jira] [Closed] (AIRAVATA-2738) Experiments are not actually LAUNCHED from orchestrator and not in zookeeper queue

[ https://issues.apache.org/jira/browse/AIRAVATA-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-2738. - Resolution: Fixed > Experiments are not actually LAUNCHED from orchestrator and not

[jira] [Commented] (AIRAVATA-2738) Experiments are not actually LAUNCHED from orchestrator and not in zookeeper queue

[ https://issues.apache.org/jira/browse/AIRAVATA-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831962#comment-16831962 ] Dimuthu Upeksha commented on AIRAVATA-2738: --- Fixed by moving zk level metadata storage to

[jira] [Commented] (AIRAVATA-2815) First experiment fails after API server restart

[ https://issues.apache.org/jira/browse/AIRAVATA-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831959#comment-16831959 ] Dimuthu Upeksha commented on AIRAVATA-2815: --- Fixed in

[jira] [Commented] (AIRAVATA-2884) Unusual delay in helix job submission

[ https://issues.apache.org/jira/browse/AIRAVATA-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831956#comment-16831956 ] Dimuthu Upeksha commented on AIRAVATA-2884: --- Fixed in new stack. Fixed in 

[jira] [Closed] (AIRAVATA-2884) Unusual delay in helix job submission

[ https://issues.apache.org/jira/browse/AIRAVATA-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-2884. - Resolution: Fixed > Unusual delay in helix job submission >

[jira] [Closed] (AIRAVATA-2815) First experiment fails after API server restart

[ https://issues.apache.org/jira/browse/AIRAVATA-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-2815. - Resolution: Fixed > First experiment fails after API server restart >

[jira] [Closed] (AIRAVATA-2205) Conflicting Loggers

[ https://issues.apache.org/jira/browse/AIRAVATA-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-2205. - Resolution: Fixed > Conflicting Loggers > > >

[jira] [Commented] (AIRAVATA-2205) Conflicting Loggers

[ https://issues.apache.org/jira/browse/AIRAVATA-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831879#comment-16831879 ] Dimuthu Upeksha commented on AIRAVATA-2205: --- Fixed in latest distributions. So closing >

[jira] [Commented] (AIRAVATA-1904) ARCHIVE did not happen in recovery

[ https://issues.apache.org/jira/browse/AIRAVATA-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831876#comment-16831876 ] Dimuthu Upeksha commented on AIRAVATA-1904: --- [~eroma_a] Do we still need this ticket? Can

[jira] [Created] (AIRAVATA-3000) [GSoC] Refactor parser framework into a generic workflow framework

Dimuthu Upeksha created AIRAVATA-3000: - Summary: [GSoC] Refactor parser framework into a generic workflow framework Key: AIRAVATA-3000 URL: https://issues.apache.org/jira/browse/AIRAVATA-3000

[jira] [Updated] (AIRAVATA-2999) [GSoC] Administration Dashboard for Airavata Services

[ https://issues.apache.org/jira/browse/AIRAVATA-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha updated AIRAVATA-2999: -- Description: Typical Apache Airavata deployment consists of multiple microservices 

[jira] [Created] (AIRAVATA-2999) [GSoC] Administration ashboard for Airavata Services

Dimuthu Upeksha created AIRAVATA-2999: - Summary: [GSoC] Administration ashboard for Airavata Services Key: AIRAVATA-2999 URL: https://issues.apache.org/jira/browse/AIRAVATA-2999 Project: Airavata

[jira] [Created] (AIRAVATA-2993) Hold the execution of Helix components when that API Server is not responding

Dimuthu Upeksha created AIRAVATA-2993: - Summary: Hold the execution of Helix components when that API Server is not responding Key: AIRAVATA-2993 URL: https://issues.apache.org/jira/browse/AIRAVATA-2993

[jira] [Commented] (AIRAVATA-2943) Re-queueing and node failures in HPC clusters need to be handled in gateway middleware as resubmitting failures

[ https://issues.apache.org/jira/browse/AIRAVATA-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782158#comment-16782158 ] Dimuthu Upeksha commented on AIRAVATA-2943: --- Fixed in 

[jira] [Closed] (AIRAVATA-2943) Re-queueing and node failures in HPC clusters need to be handled in gateway middleware as resubmitting failures

[ https://issues.apache.org/jira/browse/AIRAVATA-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-2943. - Resolution: Fixed > Re-queueing and node failures in HPC clusters need to be handled

[jira] [Closed] (AIRAVATA-2963) Cannot login to testing gateway portal and also getting an error in create experiment.

[ https://issues.apache.org/jira/browse/AIRAVATA-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-2963. - Resolution: Fixed > Cannot login to testing gateway portal and also getting an error

[jira] [Commented] (AIRAVATA-2973) Helix submitting two jobs; both at the same time for a single experiment

[ https://issues.apache.org/jira/browse/AIRAVATA-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782154#comment-16782154 ] Dimuthu Upeksha commented on AIRAVATA-2973: --- Fixed in

[jira] [Closed] (AIRAVATA-2973) Helix submitting two jobs; both at the same time for a single experiment

[ https://issues.apache.org/jira/browse/AIRAVATA-2973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-2973. - Resolution: Fixed > Helix submitting two jobs; both at the same time for a single

[jira] [Closed] (AIRAVATA-2974) Even COMPLETE jobs are tagged as CANCELED when the experiment is CANCELED

[ https://issues.apache.org/jira/browse/AIRAVATA-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-2974. - Resolution: Fixed > Even COMPLETE jobs are tagged as CANCELED when the experiment is

[jira] [Commented] (AIRAVATA-2974) Even COMPLETE jobs are tagged as CANCELED when the experiment is CANCELED

[ https://issues.apache.org/jira/browse/AIRAVATA-2974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782149#comment-16782149 ] Dimuthu Upeksha commented on AIRAVATA-2974: --- Fixed in 

[jira] [Resolved] (AIRAVATA-2962) Issue with experiment cancelation request prior to job submission

[ https://issues.apache.org/jira/browse/AIRAVATA-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2962. --- Resolution: Fixed > Issue with experiment cancelation request prior to job

[jira] [Commented] (AIRAVATA-2962) Issue with experiment cancelation request prior to job submission

[ https://issues.apache.org/jira/browse/AIRAVATA-2962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16725171#comment-16725171 ] Dimuthu Upeksha commented on AIRAVATA-2962: --- Fixed in 

[jira] [Resolved] (AIRAVATA-2956) Possible race condition in job monitoring

[ https://issues.apache.org/jira/browse/AIRAVATA-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2956. --- Resolution: Fixed Added validation logic into AbstactParser before putting a job

[jira] [Created] (AIRAVATA-2956) Possible race condition in job monitoring

Dimuthu Upeksha created AIRAVATA-2956: - Summary: Possible race condition in job monitoring Key: AIRAVATA-2956 URL: https://issues.apache.org/jira/browse/AIRAVATA-2956 Project: Airavata

[jira] [Resolved] (AIRAVATA-2942) Experiment cancelation request was not processed in Helix

[ https://issues.apache.org/jira/browse/AIRAVATA-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2942. --- Resolution: Fixed > Experiment cancelation request was not processed in Helix >

[jira] [Commented] (AIRAVATA-2942) Experiment cancelation request was not processed in Helix

[ https://issues.apache.org/jira/browse/AIRAVATA-2942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16689597#comment-16689597 ] Dimuthu Upeksha commented on AIRAVATA-2942: --- Fixed in

[jira] [Commented] (AIRAVATA-2940) Sporadic JPA errors when invoking Registry Server APIs

[ https://issues.apache.org/jira/browse/AIRAVATA-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16684215#comment-16684215 ] Dimuthu Upeksha commented on AIRAVATA-2940: --- Still couldn't identify the cause for the issue

[jira] [Created] (AIRAVATA-2940) Sporadic JPA errors when invoking Registry Server APIs

Dimuthu Upeksha created AIRAVATA-2940: - Summary: Sporadic JPA errors when invoking Registry Server APIs Key: AIRAVATA-2940 URL: https://issues.apache.org/jira/browse/AIRAVATA-2940 Project:

[jira] [Resolved] (AIRAVATA-2386) Fix issues with email monitoring

[ https://issues.apache.org/jira/browse/AIRAVATA-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2386. --- Resolution: Fixed New job monitors are running based on a state model so the

[jira] [Resolved] (AIRAVATA-2689) Distributed email clients to improve email monitoring

[ https://issues.apache.org/jira/browse/AIRAVATA-2689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2689. --- Resolution: Fixed Fixed as a part of new helix implementation. Job monitors were

[jira] [Resolved] (AIRAVATA-2750) Helix Participant is not picking up tasks after a restart

[ https://issues.apache.org/jira/browse/AIRAVATA-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2750. --- Resolution: Fixed > Helix Participant is not picking up tasks after a restart >

[jira] [Closed] (AIRAVATA-2783) Gateway output file (.tar.gz) not existing when staging out but in real it exists in the working directory

[ https://issues.apache.org/jira/browse/AIRAVATA-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha closed AIRAVATA-2783. - Resolution: Fixed Closed as this is no longer an issue as we are deprecating gfac >

[jira] [Resolved] (AIRAVATA-2786) Job COMPLETED but experiment failed with error message "unknown error occurred when initializing ..... "

[ https://issues.apache.org/jira/browse/AIRAVATA-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2786. --- Resolution: Fixed > Job COMPLETED but experiment failed with error message

[jira] [Resolved] (AIRAVATA-2784) Airavata unable to connect with the compute resource, comet.sdsc.edu

[ https://issues.apache.org/jira/browse/AIRAVATA-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2784. --- Resolution: Fixed > Airavata unable to connect with the compute resource,

[jira] [Resolved] (AIRAVATA-2789) Experiment failed with unexpected error in opening a session channel

[ https://issues.apache.org/jira/browse/AIRAVATA-2789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2789. --- Resolution: Fixed > Experiment failed with unexpected error in opening a session

[jira] [Resolved] (AIRAVATA-2790) File uploading error due to session channel opening error occurred!

[ https://issues.apache.org/jira/browse/AIRAVATA-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2790. --- Resolution: Fixed > File uploading error due to session channel opening error

[jira] [Resolved] (AIRAVATA-2792) Staging seagrid fails to submit a job

[ https://issues.apache.org/jira/browse/AIRAVATA-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2792. --- Resolution: Fixed > Staging seagrid fails to submit a job >

[jira] [Commented] (AIRAVATA-2826) Helix participant server was stopped and started while experiments are launched and job submissions to Jetstream cluster failed

[ https://issues.apache.org/jira/browse/AIRAVATA-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16623942#comment-16623942 ] Dimuthu Upeksha commented on AIRAVATA-2826: --- Added job submission retrying logic *

[jira] [Resolved] (AIRAVATA-2826) Helix participant server was stopped and started while experiments are launched and job submissions to Jetstream cluster failed

[ https://issues.apache.org/jira/browse/AIRAVATA-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2826. --- Resolution: Fixed > Helix participant server was stopped and started while

[jira] [Resolved] (AIRAVATA-2831) Experiment FAILED with an error on output file staging! But the file referring in the error is actually downloaded and available in storage.

[ https://issues.apache.org/jira/browse/AIRAVATA-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2831. --- Resolution: Fixed This should be fixed after data staging retrying implementation

[jira] [Resolved] (AIRAVATA-2833) Several experiments failed at various stages of job submission due to connection lost

[ https://issues.apache.org/jira/browse/AIRAVATA-2833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2833. --- Resolution: Fixed Added job submission retrying logic > Several experiments

[jira] [Resolved] (AIRAVATA-2874) Data staging tasks should retry if a file transfer is failed

[ https://issues.apache.org/jira/browse/AIRAVATA-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2874. --- Resolution: Fixed > Data staging tasks should retry if a file transfer is failed

[jira] [Commented] (AIRAVATA-2874) Data staging tasks should retry if a file transfer is failed

[ https://issues.apache.org/jira/browse/AIRAVATA-2874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16591652#comment-16591652 ] Dimuthu Upeksha commented on AIRAVATA-2874: --- Fixed and deployed in staging environment [1] 

[jira] [Created] (AIRAVATA-2874) Data staging tasks should retry if a file transfer is failed

Dimuthu Upeksha created AIRAVATA-2874: - Summary: Data staging tasks should retry if a file transfer is failed Key: AIRAVATA-2874 URL: https://issues.apache.org/jira/browse/AIRAVATA-2874 Project:

[jira] [Updated] (AIRAVATA-2792) Staging seagrid fails to submit a job

[ https://issues.apache.org/jira/browse/AIRAVATA-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha updated AIRAVATA-2792: -- Component/s: helix implementation > Staging seagrid fails to submit a job >

[jira] [Resolved] (AIRAVATA-2713) In helix test bed the outputs are not displayed in the experiment summary

[ https://issues.apache.org/jira/browse/AIRAVATA-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2713. --- Resolution: Fixed > In helix test bed the outputs are not displayed in the

[jira] [Resolved] (AIRAVATA-2736) Job submitted and running in HPC while the experiment is tagged as FAILED

[ https://issues.apache.org/jira/browse/AIRAVATA-2736?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2736. --- Resolution: Fixed > Job submitted and running in HPC while the experiment is

[jira] [Resolved] (AIRAVATA-2735) When transferring input files, check for the file size and 0 byte files transfers should be restricted

[ https://issues.apache.org/jira/browse/AIRAVATA-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2735. --- Resolution: Fixed > When transferring input files, check for the file size and 0

[jira] [Resolved] (AIRAVATA-2734) Experiment status in LAUNCEHD while job is in ACTIVE. Experiment status should be EXECUTING.

[ https://issues.apache.org/jira/browse/AIRAVATA-2734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2734. --- Resolution: Fixed > Experiment status in LAUNCEHD while job is in ACTIVE.

[jira] [Resolved] (AIRAVATA-2737) Too many Zookeeper connections created

[ https://issues.apache.org/jira/browse/AIRAVATA-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2737. --- Resolution: Fixed > Too many Zookeeper connections created >

[jira] [Resolved] (AIRAVATA-2733) Improvements to Helix log messages

[ https://issues.apache.org/jira/browse/AIRAVATA-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2733. --- Resolution: Fixed > Improvements to Helix log messages >

[jira] [Resolved] (AIRAVATA-2740) Non-existing file transfer has failed the experiment

[ https://issues.apache.org/jira/browse/AIRAVATA-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2740. --- Resolution: Fixed > Non-existing file transfer has failed the experiment >

[jira] [Resolved] (AIRAVATA-2743) Experiment in CANCELLED while job is still QUEUED or SUBMITTED and canceling at cluster side

[ https://issues.apache.org/jira/browse/AIRAVATA-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2743. --- Resolution: Fixed > Experiment in CANCELLED while job is still QUEUED or SUBMITTED

[jira] [Resolved] (AIRAVATA-2746) Job completed and experiment failed due to error in initializing SSH agent

[ https://issues.apache.org/jira/browse/AIRAVATA-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2746. --- Resolution: Fixed > Job completed and experiment failed due to error in

[jira] [Commented] (AIRAVATA-2746) Job completed and experiment failed due to error in initializing SSH agent

[ https://issues.apache.org/jira/browse/AIRAVATA-2746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467935#comment-16467935 ] Dimuthu Upeksha commented on AIRAVATA-2746: --- Fixed in new SSHJ based ssh adaptor

[jira] [Resolved] (AIRAVATA-2745) Job cancellations in the cluster should cancel the job and experiment in the gateway portal.

[ https://issues.apache.org/jira/browse/AIRAVATA-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2745. --- Resolution: Fixed > Job cancellations in the cluster should cancel the job and

[jira] [Resolved] (AIRAVATA-2747) OOM issue in Helix Participant

[ https://issues.apache.org/jira/browse/AIRAVATA-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha resolved AIRAVATA-2747. --- Resolution: Fixed > OOM issue in Helix Participant >

[jira] [Commented] (AIRAVATA-2747) OOM issue in Helix Participant

[ https://issues.apache.org/jira/browse/AIRAVATA-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467931#comment-16467931 ] Dimuthu Upeksha commented on AIRAVATA-2747: --- Moved to SSHJ based ssh adaptor

[jira] [Assigned] (AIRAVATA-2750) Helix Participant is not picking up tasks after a restart

[ https://issues.apache.org/jira/browse/AIRAVATA-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha reassigned AIRAVATA-2750: - Assignee: Dimuthu Upeksha > Helix Participant is not picking up tasks after a

[jira] [Updated] (AIRAVATA-2750) Helix Participant is not picking up tasks after a restart

[ https://issues.apache.org/jira/browse/AIRAVATA-2750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha updated AIRAVATA-2750: -- Component/s: helix implementation > Helix Participant is not picking up tasks after

[jira] [Assigned] (AIRAVATA-2747) OOM issue in Helix Participant

[ https://issues.apache.org/jira/browse/AIRAVATA-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha reassigned AIRAVATA-2747: - Assignee: Dimuthu Upeksha > OOM issue in Helix Participant >

[jira] [Updated] (AIRAVATA-2747) OOM issue in Helix Participant

[ https://issues.apache.org/jira/browse/AIRAVATA-2747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha updated AIRAVATA-2747: -- Attachment: airavata.log threaddump-oom.log > OOM issue in Helix

[jira] [Created] (AIRAVATA-2747) OOM issue in Helix Participant

Dimuthu Upeksha created AIRAVATA-2747: - Summary: OOM issue in Helix Participant Key: AIRAVATA-2747 URL: https://issues.apache.org/jira/browse/AIRAVATA-2747 Project: Airavata Issue Type:

[jira] [Commented] (AIRAVATA-2742) Helix Controller throws an Exception when the participant is killed

[ https://issues.apache.org/jira/browse/AIRAVATA-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16434115#comment-16434115 ] Dimuthu Upeksha commented on AIRAVATA-2742: --- Helix Team identified this as an bug and they

[jira] [Commented] (AIRAVATA-2735) When transferring input files, check for the file size and 0 byte files transfers should be restricted

[ https://issues.apache.org/jira/browse/AIRAVATA-2735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16432973#comment-16432973 ] Dimuthu Upeksha commented on AIRAVATA-2735: --- Fixed in 

[jira] [Commented] (AIRAVATA-2713) In helix test bed the outputs are not displayed in the experiment summary

[ https://issues.apache.org/jira/browse/AIRAVATA-2713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16432972#comment-16432972 ] Dimuthu Upeksha commented on AIRAVATA-2713: --- Fixed in 

[jira] [Commented] (AIRAVATA-2743) Experiment in CANCELLED while job is still QUEUED or SUBMITTED and canceling at cluster side

[ https://issues.apache.org/jira/browse/AIRAVATA-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16432964#comment-16432964 ] Dimuthu Upeksha commented on AIRAVATA-2743: --- Rolled back to initial mode as there are some

[jira] [Commented] (AIRAVATA-2745) Job cancellations in the cluster should cancel the job and experiment in the gateway portal.

[ https://issues.apache.org/jira/browse/AIRAVATA-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16432966#comment-16432966 ] Dimuthu Upeksha commented on AIRAVATA-2745: --- Fixed in 

  1   2   >