[
https://issues.apache.org/jira/browse/AIRAVATA-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774528#comment-16774528
]
Marcus Christie commented on AIRAVATA-2374:
-------------------------------------------
One interesting question that came up in our recent hackathon was whether the
Airavata services and their dependencies need to be started in a particular
order. Here are the services and dependencies to consider:
* MariaDB
* Zookeeper
* RabbitMQ
* API-Orchestrator
* GFac (master only)
* Helix services (develop/staging only)
* Kafka (develop/staging only)
* Keycloak
The first thing I looked at is whether the API-Orch service can handle a
restart of RabbitMQ. I think this is because the RabbitMQ client connection has
automatic recovery enabled [see
RabbitMQSubscriber|https://github.com/apache/airavata/blob/develop/modules/messaging/core/src/main/java/org/apache/airavata/messaging/core/impl/RabbitMQSubscriber.java#L58].
Next thing to look at is whether the API-Orch service can be started when
RabbitMQ is down and successfully connect to RabbitMQ once it is started.
> Create init scripts for airavata servers
> ----------------------------------------
>
> Key: AIRAVATA-2374
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2374
> Project: Airavata
> Issue Type: Bug
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Priority: Major
> Fix For: 0.18
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
