[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&focusedCommentId=16782149#comment-16782149 ] Dimuthu Upeksha commented on AIRAVATA-2974: --- Fixed in  https://github.com/ap

[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 C

[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 expe

[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&focusedCommentId=16782154#comment-16782154 ] Dimuthu Upeksha commented on AIRAVATA-2973: --- Fixed in https://github.com/ap

[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 i

[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 i

[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&focusedCommentId=16782158#comment-16782158 ] Dimuthu Upeksha commented on AIRAVATA-2943: --- Fixed in  https://github.com/ap

[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] [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] [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-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 Proj

[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&focusedCommentId=16831876#comment-16831876 ] Dimuthu Upeksha commented on AIRAVATA-1904: --- [~eroma_a] Do we still need thi

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

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

[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 > > > Ke

[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-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] [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&focusedCommentId=16831956#comment-16831956 ] Dimuthu Upeksha commented on AIRAVATA-2884: --- Fixed in new stack. Fixed in  [

[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&focusedCommentId=16831959#comment-16831959 ] Dimuthu Upeksha commented on AIRAVATA-2815: --- Fixed in [https://github.com/a

[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&focusedCommentId=16831962#comment-16831962 ] Dimuthu Upeksha commented on AIRAVATA-2738: --- Fixed by moving zk level metada

[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 in

[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&focusedCommentId=16832591#comment-16832591 ] Dimuthu Upeksha commented on AIRAVATA-3022: --- Fixed in  [https://github.com/a

[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 tw

[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&focusedCommentId=16832641#comment-16832641 ] Dimuthu Upeksha commented on AIRAVATA-2955: --- Fixed in  [https://github.com/a

[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&focusedCommentId=16832643#comment-16832643 ] Dimuthu Upeksha commented on AIRAVATA-2749: --- Fixed in latest improvements. P

[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 ar

[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-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&focusedCommentId=16832664#comment-16832664 ] Dimuthu Upeksha commented on AIRAVATA-2829: --- [~eroma_a] can you verify this

[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&focusedCommentId=16854145#comment-16854145 ] Dimuthu Upeksha commented on AIRAVATA-3051: --- Fixed in  [https://github.com/a

[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 w

[jira] [Commented] (AIRAVATA-3059) Helix support for multiple input files as a URI_COLLECTION with comma delimiter.

[ https://issues.apache.org/jira/browse/AIRAVATA-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16854823#comment-16854823 ] Dimuthu Upeksha commented on AIRAVATA-3059: --- Fixed in  [https://github.com/a

[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: https://issues.apache.org/jira/browse/AIR

[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&focusedCommentId=16966827#comment-16966827 ] Dimuthu Upeksha commented on AIRAVATA-3259: --- [Fixed in https://github.com/a

[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 d

[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&focusedCommentId=16990146#comment-16990146 ] Dimuthu Upeksha commented on AIRAVATA-3282: --- Fixed in  [https://github.com/a

[jira] [Assigned] (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 reassigned AIRAVATA-3287: - Assignee: Dimuthu Upeksha > 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] [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] [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&focusedCommentId=17007673#comment-17007673 ] Dimuthu Upeksha commented on AIRAVATA-3287: --- Fixed in  [https://github.com/a

[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&focusedCommentId=17007712#comment-17007712 ] Dimuthu Upeksha commented on AIRAVATA-3276: --- Fixed in  [https://github.com/a

[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] [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 T

[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 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: image-2020-03-03-15-51-02-840.png > Implement the new XSEDE usage report

[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&focusedCommentId=17050554#comment-17050554 ] Dimuthu Upeksha commented on AIRAVATA-3300: --- Fixed in  [https://github.com/

[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&focusedCommentId=17201664#comment-17201664 ] Dimuthu Upeksha commented on AIRAVATA-3372: --- Restart helix stack ./helix-st

[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: https://issues.apache.org/jira/browse/AIRAVATA-

[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&focusedCommentId=17213470#comment-17213470 ] Dimuthu Upeksha commented on AIRAVATA-3378: --- Fixed in  https://github.com/ap

[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 conta

[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&focusedCommentId=17239842#comment-17239842 ] Dimuthu Upeksha commented on AIRAVATA-3391: --- Fixed in https://github.com/apa

[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] [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-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 service

[jira] [Commented] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client

[ https://issues.apache.org/jira/browse/AIRAVATA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365777#comment-14365777 ] Dimuthu Upeksha commented on AIRAVATA-1635: --- 1. Is there any documentation th

[jira] [Commented] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client

[ https://issues.apache.org/jira/browse/AIRAVATA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366971#comment-14366971 ] Dimuthu Upeksha commented on AIRAVATA-1635: --- In GridChem-Client [1] build and

[jira] [Commented] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client

[ https://issues.apache.org/jira/browse/AIRAVATA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368302#comment-14368302 ] Dimuthu Upeksha commented on AIRAVATA-1635: --- Hi all, Suresh : Ok. I removed

[jira] [Commented] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client

[ https://issues.apache.org/jira/browse/AIRAVATA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370062#comment-14370062 ] Dimuthu Upeksha commented on AIRAVATA-1635: --- Sudhakar: Yes we will have a cha

[jira] [Commented] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client

[ https://issues.apache.org/jira/browse/AIRAVATA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14375137#comment-14375137 ] Dimuthu Upeksha commented on AIRAVATA-1635: --- What is the method to run GridCh

[jira] [Commented] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client

[ https://issues.apache.org/jira/browse/AIRAVATA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381983#comment-14381983 ] Dimuthu Upeksha commented on AIRAVATA-1635: --- Here is the URL for the proposal

[jira] [Commented] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client

[ https://issues.apache.org/jira/browse/AIRAVATA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14382132#comment-14382132 ] Dimuthu Upeksha commented on AIRAVATA-1635: --- Suresh/Sudhakar, Can I have acce

[jira] [Commented] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client

[ https://issues.apache.org/jira/browse/AIRAVATA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14383553#comment-14383553 ] Dimuthu Upeksha commented on AIRAVATA-1635: --- I tried GridChem client by putti

[jira] [Commented] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client

[ https://issues.apache.org/jira/browse/AIRAVATA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385877#comment-14385877 ] Dimuthu Upeksha commented on AIRAVATA-1635: --- Hi all, Here is the mavenized v

[jira] [Commented] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client

[ https://issues.apache.org/jira/browse/AIRAVATA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386137#comment-14386137 ] Dimuthu Upeksha commented on AIRAVATA-1635: --- Hi Suresh, Thank you for your f

[jira] [Commented] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client

[ https://issues.apache.org/jira/browse/AIRAVATA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14501722#comment-14501722 ] Dimuthu Upeksha commented on AIRAVATA-1635: --- Now GridChem Client can do authe

[jira] [Commented] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client

[ https://issues.apache.org/jira/browse/AIRAVATA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14510352#comment-14510352 ] Dimuthu Upeksha commented on AIRAVATA-1635: --- Hi Suresh, I have almost finish

[jira] [Commented] (AIRAVATA-1635) [GSoC] Integrate Airavata Java Client SDK with GridChem Client

[ https://issues.apache.org/jira/browse/AIRAVATA-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14600622#comment-14600622 ] Dimuthu Upeksha commented on AIRAVATA-1635: --- Short demo of current progress c

[jira] [Commented] (AIRAVATA-2620) Force post processing functionality

[ https://issues.apache.org/jira/browse/AIRAVATA-2620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16303021#comment-16303021 ] Dimuthu Upeksha commented on AIRAVATA-2620: --- Fixed in https://github.com/apa

[jira] [Commented] (AIRAVATA-2621) SSH port provided in compute resource registration is not considered for cluster SSH communication

[ https://issues.apache.org/jira/browse/AIRAVATA-2621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329205#comment-16329205 ] Dimuthu Upeksha commented on AIRAVATA-2621: --- Fix will look for the SSHJobSumi

[jira] [Assigned] (AIRAVATA-2624) Sampede2 cluster SSH connectivity issue

[ https://issues.apache.org/jira/browse/AIRAVATA-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dimuthu Upeksha reassigned AIRAVATA-2624: - Assignee: Dimuthu Upeksha (was: Suresh Marru) > Sampede2 cluster SSH connecti

[jira] [Commented] (AIRAVATA-2624) Sampede2 cluster SSH connectivity issue

[ https://issues.apache.org/jira/browse/AIRAVATA-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329304#comment-16329304 ] Dimuthu Upeksha commented on AIRAVATA-2624: --- Fixed in [https://github.com/ap

[jira] [Commented] (AIRAVATA-2625) Derive and present Text outputs in Experiment summary

[ https://issues.apache.org/jira/browse/AIRAVATA-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16338084#comment-16338084 ] Dimuthu Upeksha commented on AIRAVATA-2625: --- This is might require few change

[jira] [Commented] (AIRAVATA-2143) Experiments with overridden resource allocation details tries to use qos and reservation from community user

[ https://issues.apache.org/jira/browse/AIRAVATA-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16343809#comment-16343809 ] Dimuthu Upeksha commented on AIRAVATA-2143: --- Fixed in https://github.com/apac

[jira] [Created] (AIRAVATA-2687) Distributed agents on compute resources to communicate with Airavata server

Dimuthu Upeksha created AIRAVATA-2687: - Summary: Distributed agents on compute resources to communicate with Airavata server Key: AIRAVATA-2687 URL: https://issues.apache.org/jira/browse/AIRAVATA-2687

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

Dimuthu Upeksha created AIRAVATA-2689: - Summary: Distributed email clients to improve email monitoring Key: AIRAVATA-2689 URL: https://issues.apache.org/jira/browse/AIRAVATA-2689 Project: Airavata

[jira] [Commented] (AIRAVATA-2717) [GSoC] Resurrect User-Defined Airavata Workflows

[ https://issues.apache.org/jira/browse/AIRAVATA-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409595#comment-16409595 ] Dimuthu Upeksha commented on AIRAVATA-2717: --- Hi Yasas, It is bit outdated bu

[jira] [Commented] (AIRAVATA-2718) [GSoC] Re-architect Output Data Parsing into Airavata core

[ https://issues.apache.org/jira/browse/AIRAVATA-2718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16409608#comment-16409608 ] Dimuthu Upeksha commented on AIRAVATA-2718: --- Hi Lahiru, Thanks for your inte

[jira] [Commented] (AIRAVATA-2717) [GSoC] Resurrect User-Defined Airavata Workflows

[ https://issues.apache.org/jira/browse/AIRAVATA-2717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411604#comment-16411604 ] Dimuthu Upeksha commented on AIRAVATA-2717: --- [~marcuschristie] Yeah I guess t

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

[ https://issues.apache.org/jira/browse/AIRAVATA-2733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16424528#comment-16424528 ] Dimuthu Upeksha commented on AIRAVATA-2733: --- Fixed in [https://github.com/ap

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16424532#comment-16424532 ] Dimuthu Upeksha commented on AIRAVATA-2734: --- Fixed in  https://github.com/apa

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

[ https://issues.apache.org/jira/browse/AIRAVATA-2737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16424534#comment-16424534 ] Dimuthu Upeksha commented on AIRAVATA-2737: --- Fixed in  https://github.com/apa

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16428425#comment-16428425 ] Dimuthu Upeksha commented on AIRAVATA-2740: --- Fixed in  [https://github.com/a

[jira] [Commented] (AIRAVATA-2467) When given *.chk as the value for the output file in an application. File(s) with that extension is not listed in the summary.

[ https://issues.apache.org/jira/browse/AIRAVATA-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16429547#comment-16429547 ] Dimuthu Upeksha commented on AIRAVATA-2467: --- Fixed in [https://github.com/apa

[jira] [Assigned] (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:all-tabpanel ] Dimuthu Upeksha reassigned AIRAVATA-2742: - Assignee: Dimuthu Upeksha > Helix Controller throws an Exception when the part

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

Dimuthu Upeksha created AIRAVATA-2742: - Summary: Helix Controller throws an Exception when the participant is killed Key: AIRAVATA-2742 URL: https://issues.apache.org/jira/browse/AIRAVATA-2742 Pro

[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&focusedCommentId=16430643#comment-16430643 ] Dimuthu Upeksha commented on AIRAVATA-2742: --- Tested this locally for both SIG

[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&focusedCommentId=16431625#comment-16431625 ] Dimuthu Upeksha commented on AIRAVATA-2743: --- Fixed in  https://github.com/apa

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16432957#comment-16432957 ] Dimuthu Upeksha commented on AIRAVATA-2736: --- Fixed in  https://github.com/apa

[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&focusedCommentId=16432964#comment-16432964 ] Dimuthu Upeksha commented on AIRAVATA-2743: --- Rolled back to initial mode as t

[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&focusedCommentId=16432966#comment-16432966 ] Dimuthu Upeksha commented on AIRAVATA-2745: --- Fixed in  https://github.com/apa

[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&focusedCommentId=16432972#comment-16432972 ] Dimuthu Upeksha commented on AIRAVATA-2713: --- Fixed in  https://github.com/apa

[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&focusedCommentId=16432973#comment-16432973 ] Dimuthu Upeksha commented on AIRAVATA-2735: --- Fixed in  https://github.com/apa

[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&focusedCommentId=16434115#comment-16434115 ] Dimuthu Upeksha commented on AIRAVATA-2742: --- Helix Team identified this as an

[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: B

[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 Part

[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] [Created] (AIRAVATA-2748) API server throws OOM exception when multiple connections are made through credentials client

Dimuthu Upeksha created AIRAVATA-2748: - Summary: API server throws OOM exception when multiple connections are made through credentials client Key: AIRAVATA-2748 URL: https://issues.apache.org/jira/browse/AIRA

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

Dimuthu Upeksha created AIRAVATA-2750: - Summary: Helix Participant is not picking up tasks after a restart Key: AIRAVATA-2750 URL: https://issues.apache.org/jira/browse/AIRAVATA-2750 Project: Airav

[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 a

[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

  1   2   >