[
https://issues.apache.org/jira/browse/SDAP-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590550#comment-16590550
]
Frank Greguska commented on SDAP-131:
-------------------------------------
I see two potential solutions:
# Start ningesterpy as a service since this is the process that binds port
5000. All ningester jobs would share the same ningesterpy service
** Pros:
*** service could be shared for bulk ingestion and for ability to create tiles
dynamically
** Cons:
*** Data file would have to be uploaded/downloaded to the ningesterpy service
*** Service needs to remain running at all times, losing the cost savings of
only using resources while data is being ingested
# Allow ningesterpy to select random open port and pass selected port to java
process
** Pros:
*** No need for 'always-on' service
*** Same data file is available for both java and python processes
** Cons:
*** Complicated to pass the port chosen from python to java
I think the second option is the better one.
> Unable to run multiple instances of ningester on same host
> ----------------------------------------------------------
>
> Key: SDAP-131
> URL: https://issues.apache.org/jira/browse/SDAP-131
> Project: Apache Science Data Analytics Platform
> Issue Type: Bug
> Components: nexus
> Reporter: Frank Greguska
> Assignee: Frank Greguska
> Priority: Major
>
> Problem was discovered when trying to run ningester on AWS. AWS Batch
> launches containers in network mode 'host'. Since the ningester container
> uses port 5000 to communicate between the python and java processes, this
> means that only one container can run per host.
> Need a fix that will allow multiple ningester containers to run on the same
> host.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
