[
https://issues.apache.org/jira/browse/LIVY-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16291734#comment-16291734
]
Avneet Oberoi edited comment on LIVY-401 at 12/19/17 11:58 PM:
---------------------------------------------------------------
For this issue,the problem to be addressed is that 2 or more instances of
livy-servers were unable to be setup on a single machine due to the naming
conflict described above.
As a fix, we can let a user provide an optional identifier as an additional
argument when starting,checking status, or killing a livy instance.
This identifier would be included in the LIVY_IDENT_STRING which is defined in
the livy-server script.
This would help prevent the naming conflict in the pid and log file name, thus
letting multiple instances of livy run on different ports.
This would also be backward compatible and would not require any change in
usage for those running a single instance.
Does this sound like a reasonable approach?
Are there other implications of having multiple instance of livy on a machine,
which would need to be fixed?
was (Author: avneet15):
For this issue,the problem to be addressed is that 2 or more instances of
livy-servers were unable to
be setup on a single machine due to the naming conflict described above.
As a fix, we can let a user provide an optional identifier as an additional
argument when starting,checking status, or killing a livy instance.
This identifier would be included in the LIVY_IDENT_STRING which is defined in
the livy-server script.
This would help prevent the naming conflict in the pid and log file name, thus
letting multiple instances of livy run on different ports.
Does this sound like a reasonable approach?
Are there other implications of having multiple instance of livy on a machine,
which would need to be fixed?
> Can not start 2 livy server instance in different port
> ------------------------------------------------------
>
> Key: LIVY-401
> URL: https://issues.apache.org/jira/browse/LIVY-401
> Project: Livy
> Issue Type: Bug
> Reporter: Jeff Zhang
>
> I try to launch 2 livy server instances in different port. But after I launch
> the second livy server, the first one then won't work, but no error message
> in the log. The issue seems to be they are using the same LIVY_PID_DIR, but
> there's no error message for that when I launch the second livy server.
> Actually I can see the warning message when I launch 2 livy server of livy
> 0.3.0. So this may be due to some bugs in livy launch script.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
