[GitHub] zeppelin pull request #1391: ZEPPELIN-1403. Should maintain the using port l...

2018-03-06 Thread zjffdu
Github user zjffdu closed the pull request at:

https://github.com/apache/zeppelin/pull/1391


---


[GitHub] zeppelin pull request #1391: ZEPPELIN-1403. Should maintain the using port l...

2016-09-01 Thread zjffdu
GitHub user zjffdu opened a pull request:

https://github.com/apache/zeppelin/pull/1391

ZEPPELIN-1403. Should maintain the using port list

### What is this PR for?
For now, in RemoteInterpreterManagedProcess we will first find one 
available port (By using ServerSocket) and then use this port in the 
interpreter process. But it is possible that 2 interpreters use the same port. 
Here's the scenarios.
1. Thread1 (Interpreter A) find available port 3000 
2. Thread2 (Interpreter B) find available port 3000 
3. Process for Interpreter A starts
4. Process for Interpreter B starts


### What type of PR is it?
[Bug Fix]

### Todos
* [ ] - Task

### What is the Jira issue?
* https://issues.apache.org/jira/browse/ZEPPELIN-1403

### How should this be tested?
No test added

### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/zjffdu/zeppelin ZEPPELIN-1403

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/zeppelin/pull/1391.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1391


commit 8ce0c5fb5b94aa9d8efb0ee0f9f32d0e629b3ba6
Author: Jeff Zhang 
Date:   2016-09-01T06:21:56Z

ZEPPELIN-1403. Should maintain the using port list




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---