You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@airavata.apache.org by "Marcus Christie (JIRA)" <ji...@apache.org> on 2017/06/13 13:30:00 UTC

[jira] [Commented] (AIRAVATA-2376) Duplicating experiment records in Experiment statistics and Experiment browse

    [ https://issues.apache.org/jira/browse/AIRAVATA-2376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16047902#comment-16047902 ] 

Marcus Christie commented on AIRAVATA-2376:
-------------------------------------------

I've got this working now by using the MariaDB jar.  Since [version 1.1.8|https://mariadb.com/kb/en/mariadb/mariadb-java-client-118-changelog/] the MariaDB JDBC driver defaults to using fractional seconds.  So the solution required two changes:
* update the column as in the previous comment
* switch to using the MariaDB JDBC jar

Still to do:
* update Ansible scripts to create a airavata-server.properties with mariadb JDBC driver
* also update Ansible scripts to download the MariaDB JDBC driver and remove the MySQL JDBC driver

> Duplicating experiment records in Experiment statistics and Experiment browse
> -----------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2376
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2376
>             Project: Airavata
>          Issue Type: Bug
>          Components: PGA PHP Web Gateway, Registry API
>    Affects Versions: 0.17
>         Environment: https://seagrid.org and all other gateways as well
>            Reporter: Eroma
>            Assignee: Marcus Christie
>            Priority: Critical
>             Fix For: 0.17
>
>
> When experiments are launched there are two records in EXPERIMENT SUMMARY table for LAUNCHED and EXECUTING state which has the exact same state change time. In PGA however two records show up for the same experiment and with same status. e.g.: two exact records for a single experiment. This only appears until the experiment is FAILED or COMPLETED. But both users and gateway admins notices this and this needs fixing. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)