[
https://issues.apache.org/jira/browse/TAJO-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493609#comment-14493609
]
ASF GitHub Bot commented on TAJO-1497:
--------------------------------------
GitHub user jinossy opened a pull request:
https://github.com/apache/tajo/pull/533
TAJO-1497: TajoClient does not share a connection
I've change RpcConnectionPool to RpcConnectionManager and remove the
release codes.
Because netty rpc does not need pooling.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jinossy/tajo TAJO-1497
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/533.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 #533
----
commit a0ff031876f29c5d449916ffd13bb9c66636014b
Author: Jinho Kim <[email protected]>
Date: 2015-04-14T05:39:07Z
TAJO-1497: TajoClient does not share a connection
----
> TajoClient does not share a connection
> --------------------------------------
>
> Key: TAJO-1497
> URL: https://issues.apache.org/jira/browse/TAJO-1497
> Project: Tajo
> Issue Type: Bug
> Components: client, rpc
> Affects Versions: 0.11.0
> Reporter: Jinho Kim
> Assignee: Jinho Kim
> Fix For: 0.11.0
>
>
> Currently, tajo client try to connect per client API call.
> Because a client reference count is one. RPC pool should close only Idle
> connection
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
