[jira] [Commented] (AIRAVATA-2728) Refactoring Experiment Catalog Implementation
[ https://issues.apache.org/jira/browse/AIRAVATA-2728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16433190#comment-16433190 ] ASF GitHub Bot commented on AIRAVATA-2728: -- tilaks26 opened a new pull request #191: [AIRAVATA-2728] Refactoring Experiment Catalog Implementation URL: https://github.com/apache/airavata/pull/191 Implementation of Repository classes for the Experiment Catalog. Changes made - Added the necessary entity classes. Included all the methods for the repository class. Pending work - Included tests for the repository class. Made necessary changes to the RegistryServerHandler.java class. Note: This PR includes Workspace Catalog modules as well. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Refactoring Experiment Catalog Implementation > - > > Key: AIRAVATA-2728 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2728 > Project: Airavata > Issue Type: Improvement > Components: Registry API >Reporter: Sneha Tilak >Assignee: Sneha Tilak >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 https://github.com/apache/airavata/commit/0f0712382a9ce124a90939c247d2f352510e350b > When transferring input files, check for the file size and 0 byte files > transfers should be restricted > -- > > Key: AIRAVATA-2735 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2735 > Project: Airavata > Issue Type: Improvement > Components: helix implementation >Affects Versions: 0.18 >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > # When transferring input files if the file is 0 in size, file transfer task > should fail and experiment should fail. > # User should be notified about the file being empty. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 https://github.com/apache/airavata/commit/bc0016f65dfb0146c92bbd76cc25cb93650748ea > In helix test bed the outputs are not displayed in the experiment summary > - > > Key: AIRAVATA-2713 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2713 > Project: Airavata > Issue Type: Bug > Components: helix implementation >Affects Versions: 0.18 >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > Submitted a job in helix implementation and job and experiment both got > completed. The outputs exists and can view and download from storage but not > in the experiment summary. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 schedulers do not send emails once the job is cancelled https://github.com/apache/airavata/commit/98b7d16065f946f32ccfb886ff8190c6a545c434 > Experiment in CANCELLED while job is still QUEUED or SUBMITTED and canceling > at cluster side > > > Key: AIRAVATA-2743 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2743 > Project: Airavata > Issue Type: Bug > Components: helix implementation >Affects Versions: 0.18 >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > # Submit an experiment > # Cancel the experiment in PGA > # Experiment status changes to CANCELING > # Experiment status changes to CANCELLED while job is in either SUBMITTED or > QUEUED. > # Experiment status should change to CANCELLED only after the job status > changes to an end status (CANCELLED, COMPLETED or FAILED). > # -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 https://github.com/apache/airavata/commit/e26b66c4b5fe0912c9992ef1baefa2f364469377 > Job cancellations in the cluster should cancel the job and experiment in the > gateway portal. > > > Key: AIRAVATA-2745 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2745 > Project: Airavata > Issue Type: New Feature > Components: helix implementation >Affects Versions: 0.18 >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > When a user cancels the job directly in the cluster/JPC an email will be sent > to the monitoring. This email is sent for all slurm jobs but PBS could be > different and may not send this. > > If airavata receives an cancel email the job should be cancelled and so is > the experiment irrespective of where the command executed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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=16432957#comment-16432957 ] Dimuthu Upeksha commented on AIRAVATA-2736: --- Fixed in https://github.com/apache/airavata/commit/1b950bdb5b96f046e4fbaac6e7024b158dd86e7a > Job submitted and running in HPC while the experiment is tagged as FAILED > - > > Key: AIRAVATA-2736 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2736 > Project: Airavata > Issue Type: Bug > Components: helix implementation >Affects Versions: 0.18 > Environment: http://149.165.168.248:8008/ - Helix test env >Reporter: Eroma >Assignee: Dimuthu Upeksha >Priority: Major > Fix For: 0.18 > > > # Submitted an experiment which then submitted the job. > # Job ID is returned and the status is ACTIVE. > # Due to zookeeper connection issue the experiment is FAILED. > # The job is still running in HPC > # Airavata is not waiting for job monitoring as the task status is not > updated in the zookeeper. > # error in log [1] > # SLM001-AmberSander-BR2_5ed5a19f-ab44-4eba-afb7-1feafaf0bbdd - exp ID > [1] > |org.apache.zookeeper.KeeperException$ConnectionLossException: > KeeperErrorCode = ConnectionLoss for /monitoring/2159926/lock at > org.apache.zookeeper.KeeperException.create(KeeperException.java:99) at > org.apache.zookeeper.KeeperException.create(KeeperException.java:51) at > org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:778) at > org.apache.curator.framework.imps.CreateBuilderImpl$11.call(CreateBuilderImpl.java:696) > at > org.apache.curator.framework.imps.CreateBuilderImpl$11.call(CreateBuilderImpl.java:679) > at org.apache.curator.RetryLoop.callWithRetry(RetryLoop.java:107) at > org.apache.curator.framework.imps.CreateBuilderImpl.pathInForeground(CreateBuilderImpl.java:676) > at > org.apache.curator.framework.imps.CreateBuilderImpl.protectedPathInForeground(CreateBuilderImpl.java:453) > at > org.apache.curator.framework.imps.CreateBuilderImpl.forPath(CreateBuilderImpl.java:443) > at > org.apache.curator.framework.imps.CreateBuilderImpl.forPath(CreateBuilderImpl.java:44) > at > org.apache.airavata.helix.impl.task.submission.JobSubmissionTask.createMonitoringNode(JobSubmissionTask.java:83) > at > org.apache.airavata.helix.impl.task.submission.DefaultJobSubmissionTask.onRun(DefaultJobSubmissionTask.java:144) > at > org.apache.airavata.helix.impl.task.AiravataTask.onRun(AiravataTask.java:264) > at org.apache.airavata.helix.core.AbstractTask.run(AbstractTask.java:74) at > org.apache.helix.task.TaskRunner.run(TaskRunner.java:70) at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at > java.util.concurrent.FutureTask.run(FutureTask.java:266) at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) > at > java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:748)| -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRAVATA-2745) Job cancellations in the cluster should cancel the job and experiment in the gateway portal.
Eroma created AIRAVATA-2745: --- Summary: Job cancellations in the cluster should cancel the job and experiment in the gateway portal. Key: AIRAVATA-2745 URL: https://issues.apache.org/jira/browse/AIRAVATA-2745 Project: Airavata Issue Type: New Feature Components: helix implementation Affects Versions: 0.18 Reporter: Eroma Assignee: Dimuthu Upeksha Fix For: 0.18 When a user cancels the job directly in the cluster/JPC an email will be sent to the monitoring. This email is sent for all slurm jobs but PBS could be different and may not send this. If airavata receives an cancel email the job should be cancelled and so is the experiment irrespective of where the command executed. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (AIRAVATA-2744) In 'Add Filter' of Experiment statistics only show the compute resources that gateway has added preferences
Eroma created AIRAVATA-2744: --- Summary: In 'Add Filter' of Experiment statistics only show the compute resources that gateway has added preferences Key: AIRAVATA-2744 URL: https://issues.apache.org/jira/browse/AIRAVATA-2744 Project: Airavata Issue Type: Improvement Components: PGA PHP Web Gateway Affects Versions: 0.18 Reporter: Eroma Assignee: Marcus Christie Fix For: 0.18 In Experiment Statistics --> Add Filter for Host name all the resources are listed in the scigap. For each gateway only show the ones that gateway has preferences for. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (AIRAVATA-2697) Update GroupResourceProfile methods in API server to use sharing API to enforce READ and WRITE rules
[ https://issues.apache.org/jira/browse/AIRAVATA-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16432689#comment-16432689 ] ASF GitHub Bot commented on AIRAVATA-2697: -- sachinkariyattin commented on issue #181: [AIRAVATA-2697] Update GroupResourceProfile methods in API server to use sharing API to enforce READ and WRITE rules URL: https://github.com/apache/airavata/pull/181#issuecomment-380193173 @machristie Thanks for the review. I have made the suggested changes. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Update GroupResourceProfile methods in API server to use sharing API to > enforce READ and WRITE rules > > > Key: AIRAVATA-2697 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2697 > Project: Airavata > Issue Type: Bug >Reporter: Marcus Christie >Assignee: Sachin Kariyattin >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
