Open ks881115 opened 9 years ago
The answer probably depends on which component needs to know the Driver's address. For example, is it one of the following?
First we need it for the Evaluator. But if it's allowed, I also want to have the information from the Driver itself and from the REEF Client
This depends.
Why do you need to create a RPC channel? Can't you reuse the existing channel in REEF?
Because Tajo is already implementing its own RPC using ProtocolBuffer. and it requires IP addr and Port number to be opened.
But now, I found out that Tajo QM (=REEF Driver) serves only as a Server. So it sends its binded IP address when it launches Slave tasks. So Slaves can connect to Tajo QM.
Therefore, maybe we can go without it.Sorry for not checking it thoroughly....
Thanks for your help all the time!!!
2014-12-06 17:52 GMT+09:00 Byung-Gon Chun notifications@github.com:
This depends.
Why do you need to create a RPC channel? Can't you reuse the existing channel in REEF?
— Reply to this email directly or view it on GitHub https://github.com/swsnu/discussionbdcsfall2014/issues/36#issuecomment-65890346 .
Is there any way for me to get a REEF Driver's address? I need this to open an RPC connection between Driver (QueryMaster) / Evaluator (TaskRunner)
Sorry again for asking too many questions...