Uploaded image for project: 'Tajo'
  1. Tajo
  2. TAJO-1424

Investigate the problem of too many "Try to connect" messeges during Travic CI build

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.11.0
    • Component/s: None
    • Labels:
      None

      Description

      See the title.
      After TAJO-1391, Travis emits too many "Try to connect" messeges, and finally reaches the 10000 line limit.

      1. TAJO-1424.patch
        0.8 kB
        Dongjoon Hyun

        Issue Links

          Activity

          Hide
          githubbot ASF GitHub Bot added a comment -

          GitHub user dongjoon-hyun opened a pull request:

          https://github.com/apache/tajo/pull/440

          TAJO-1424: Too many 'Try to connect' messeges during Travic CI build

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

          $ git pull https://github.com/dongjoon-hyun/tajo TAJO-1424

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

          https://github.com/apache/tajo/pull/440.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 #440


          commit 36f3f06eb78e37c5e651e689047f9920eb1d262c
          Author: Dongjoon Hyun <dongjoon@apache.org>
          Date: 2015-03-20T02:42:58Z

          TAJO-1424: Too many 'Try to connect' messeges during Travic CI build


          Show
          githubbot ASF GitHub Bot added a comment - GitHub user dongjoon-hyun opened a pull request: https://github.com/apache/tajo/pull/440 TAJO-1424 : Too many 'Try to connect' messeges during Travic CI build You can merge this pull request into a Git repository by running: $ git pull https://github.com/dongjoon-hyun/tajo TAJO-1424 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/tajo/pull/440.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 #440 commit 36f3f06eb78e37c5e651e689047f9920eb1d262c Author: Dongjoon Hyun <dongjoon@apache.org> Date: 2015-03-20T02:42:58Z TAJO-1424 : Too many 'Try to connect' messeges during Travic CI build
          Hide
          jhkim Jinho Kim added a comment -

          we should investigate it. In my opinion, looks need a idle time checker

          Show
          jhkim Jinho Kim added a comment - we should investigate it. In my opinion, looks need a idle time checker
          Hide
          dongjoon Dongjoon Hyun added a comment -

          Sure, please share the underneath potential problem of this issue.
          Thank you, Jinho Kim.

          Show
          dongjoon Dongjoon Hyun added a comment - Sure, please share the underneath potential problem of this issue. Thank you, Jinho Kim .
          Hide
          jhkim Jinho Kim added a comment -

          Dongjoon Hyun I did not investigate it. but I think that your patch just ignore the log message.
          Navis Can you some explain or investigate this ?

          Show
          jhkim Jinho Kim added a comment - Dongjoon Hyun I did not investigate it. but I think that your patch just ignore the log message. Navis Can you some explain or investigate this ?
          Hide
          navis Navis added a comment -

          It had logged only when reconnecting before but now it logs any new connection trial. Damn my laziness.

          +1 for intention

          Show
          navis Navis added a comment - It had logged only when reconnecting before but now it logs any new connection trial. Damn my laziness. +1 for intention
          Hide
          jhkim Jinho Kim added a comment -

          Navis Thank you for your response
          I like your sense of humor.

          Show
          jhkim Jinho Kim added a comment - Navis Thank you for your response I like your sense of humor.
          Hide
          dongjoon Dongjoon Hyun added a comment -

          Hi, Jinho Kim,

          This is a trivial issue and patch.
          I know you already reviewed this patch.
          After Jenkins build, could you give here +1?

          Show
          dongjoon Dongjoon Hyun added a comment - Hi, Jinho Kim , This is a trivial issue and patch. I know you already reviewed this patch. After Jenkins build, could you give here +1?
          Hide
          jihoonson Jihoon Son added a comment -

          Thanks for discussion.
          As Jinho Kim and Navis said, it would be better if we find and fix the fundamental problem rather than just ignoring the log messages.
          I think Navis knows a better solution.
          Do you have any ideas?

          Show
          jihoonson Jihoon Son added a comment - Thanks for discussion. As Jinho Kim and Navis said, it would be better if we find and fix the fundamental problem rather than just ignoring the log messages. I think Navis knows a better solution. Do you have any ideas?
          Hide
          tajoqa Tajo QA added a comment -

          -1 overall. Here are the results of testing the latest attachment
          http://issues.apache.org/jira/secure/attachment/12705812/TAJO-1424.patch
          against master revision release-0.9.0-rc0-212-g154f5b9.

          +1 @author. The patch does not contain any @author tags.

          -1 tests included. The patch doesn't appear to include any new or modified tests.
          Please justify why no new tests are needed for this patch.
          Also please list what manual steps were performed to verify this patch.

          +1 javac. The applied patch does not increase the total number of javac compiler warnings.

          +1 javadoc. The applied patch does not increase the total number of javadoc warnings.

          +1 checkstyle. The patch generated 0 code style errors.

          -1 findbugs. The patch appears to cause Findbugs (version 2.0.3) to fail.

          +1 release audit. The applied patch does not increase the total number of release audit warnings.

          +1 core tests. The patch passed unit tests in tajo-rpc/tajo-rpc-protobuf.

          Test results: https://builds.apache.org/job/PreCommit-TAJO-Build/626//testReport/
          Findbugs results: https://builds.apache.org/job/PreCommit-TAJO-Build/626//findbugsResult
          Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/626//console

          This message is automatically generated.

          Show
          tajoqa Tajo QA added a comment - -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12705812/TAJO-1424.patch against master revision release-0.9.0-rc0-212-g154f5b9. +1 @author. The patch does not contain any @author tags. -1 tests included. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 javadoc. The applied patch does not increase the total number of javadoc warnings. +1 checkstyle. The patch generated 0 code style errors. -1 findbugs. The patch appears to cause Findbugs (version 2.0.3) to fail. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in tajo-rpc/tajo-rpc-protobuf. Test results: https://builds.apache.org/job/PreCommit-TAJO-Build/626//testReport/ Findbugs results: https://builds.apache.org/job/PreCommit-TAJO-Build/626//findbugsResult Console output: https://builds.apache.org/job/PreCommit-TAJO-Build/626//console This message is automatically generated.
          Hide
          dongjoon Dongjoon Hyun added a comment -

          You can investigate more with DEBUG level. I did not delete that.
          Don't you suffer from this log?

          Show
          dongjoon Dongjoon Hyun added a comment - You can investigate more with DEBUG level. I did not delete that. Don't you suffer from this log?
          Hide
          dongjoon Dongjoon Hyun added a comment -

          By the way, if you find any fundamental problem, please create another issue.
          Current issue description does not mention anything at all.

          Show
          dongjoon Dongjoon Hyun added a comment - By the way, if you find any fundamental problem, please create another issue. Current issue description does not mention anything at all.
          Hide
          jihoonson Jihoon Son added a comment -

          No, your patch is good to just ignore annoying messages.
          However, it would be better if we fix the fundamental problem which generates these annoying messages by calling NettyClientBase.connectUsingNetty() repeatedly.

          Show
          jihoonson Jihoon Son added a comment - No, your patch is good to just ignore annoying messages. However, it would be better if we fix the fundamental problem which generates these annoying messages by calling NettyClientBase.connectUsingNetty() repeatedly.
          Hide
          jihoonson Jihoon Son added a comment -

          Dongjoon Hyun, sorry for confusing you.
          Honestly, I intended the investigation of the fundamental problem.
          I've changed the title.

          Show
          jihoonson Jihoon Son added a comment - Dongjoon Hyun , sorry for confusing you. Honestly, I intended the investigation of the fundamental problem. I've changed the title.
          Hide
          navis Navis added a comment -

          AFAIK, which is a little, tajo clients does not use connection pool as a pool (closes connection when it does what it wanted).

          Show
          navis Navis added a comment - AFAIK, which is a little, tajo clients does not use connection pool as a pool (closes connection when it does what it wanted).
          Hide
          jhkim Jinho Kim added a comment -

          You’re right. RpcConnectionPool should be renamed

          Anyway. If a client reference count is one, It execute following
          getConnection() -> selectDatabase() -> close() -> getConnection() -> getTable() -> close()

          IdleStageHandler would be better than the reference counter
          http://netty.io/4.0/api/io/netty/handler/timeout/IdleStateHandler.html

          Show
          jhkim Jinho Kim added a comment - You’re right. RpcConnectionPool should be renamed Anyway. If a client reference count is one, It execute following getConnection() -> selectDatabase() -> close() -> getConnection() -> getTable() -> close() IdleStageHandler would be better than the reference counter http://netty.io/4.0/api/io/netty/handler/timeout/IdleStateHandler.html
          Hide
          githubbot ASF GitHub Bot added a comment -

          GitHub user navis opened a pull request:

          https://github.com/apache/tajo/pull/488

          TAJO-1424 Investigate the problem of too many "Try to connect" messeges

          Ok, let's fix this quickly. Hard to see the log.

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

          $ git pull https://github.com/navis/tajo TAJO-1424

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

          https://github.com/apache/tajo/pull/488.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 #488


          commit 21bcd08648eb2332b096e7a66f8c75cf85ee6149
          Author: navis.ryu <navis@apache.org>
          Date: 2015-04-01T01:29:03Z

          TAJO-1424 Investigate the problem of too many "Try to connect" messeges


          Show
          githubbot ASF GitHub Bot added a comment - GitHub user navis opened a pull request: https://github.com/apache/tajo/pull/488 TAJO-1424 Investigate the problem of too many "Try to connect" messeges Ok, let's fix this quickly. Hard to see the log. You can merge this pull request into a Git repository by running: $ git pull https://github.com/navis/tajo TAJO-1424 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/tajo/pull/488.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 #488 commit 21bcd08648eb2332b096e7a66f8c75cf85ee6149 Author: navis.ryu <navis@apache.org> Date: 2015-04-01T01:29:03Z TAJO-1424 Investigate the problem of too many "Try to connect" messeges
          Hide
          jhkim Jinho Kim added a comment -

          Navis
          I'll fix real problems in TAJO-1497

          Show
          jhkim Jinho Kim added a comment - Navis I'll fix real problems in TAJO-1497
          Hide
          jhkim Jinho Kim added a comment -

          Jihoon Son
          We can skip the warnings for a while. What do you think about temporary solution before TAJO-1497 is fixed ?

          Show
          jhkim Jinho Kim added a comment - Jihoon Son We can skip the warnings for a while. What do you think about temporary solution before TAJO-1497 is fixed ?
          Hide
          jihoonson Jihoon Son added a comment -

          Much appreciate Jinho Kim.
          I'll review Navis's patch.

          Show
          jihoonson Jihoon Son added a comment - Much appreciate Jinho Kim . I'll review Navis 's patch.
          Hide
          jhkim Jinho Kim added a comment -

          Thanks. please go ahead

          Show
          jhkim Jinho Kim added a comment - Thanks. please go ahead
          Hide
          jihoonson Jihoon Son added a comment -

          Hey Navis.
          I run 'mvn clean install -Pparallel-test,hcatalog-0.12.0 -DLOG_LEVEL=WARN -Dmaven.fork.count=2', and saw the following messages.

          Running org.apache.tajo.engine.query.TestJoinBroadcast
          2015-04-01 15:37:39,450 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:37:42,968 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:37:46,480 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:37:49,992 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:37:53,512 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:37:57,030 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:00,543 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:04,057 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:07,576 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:11,094 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:14,614 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:18,132 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:21,646 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:25,158 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:28,677 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:32,196 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:35,707 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:39,226 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:42,734 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:46,243 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:49,757 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:53,268 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:38:56,791 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:39:00,306 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:39:03,828 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:39:07,347 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:39:10,859 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:39:14,374 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:39:17,895 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:39:21,407 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:39:24,926 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:39:28,445 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:39:31,960 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:39:35,481 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:39:38,988 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          Tests run: 48, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 124.784 sec - in org.apache.tajo.engine.query.TestJoinBroadcast
          Running org.apache.tajo.engine.query.TestJoinOnPartitionedTables
          2015-04-01 15:39:42,511 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:39:46,033 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:39:49,548 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:39:53,060 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:39:56,575 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:00,094 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:03,612 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.84 sec - in org.apache.tajo.engine.query.TestJoinOnPartitionedTables
          Running org.apache.tajo.engine.query.TestJoinQuery
          2015-04-01 15:40:07,122 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:10,641 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:14,161 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:17,680 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:21,193 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:24,706 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:28,225 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:31,743 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:35,259 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:38,774 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:42,289 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:45,807 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:49,322 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:52,837 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:56,356 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:40:59,876 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:41:03,394 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:41:06,911 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:41:10,426 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:41:13,948 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          2015-04-01 15:41:17,458 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3
          ...
          

          It seems that your patch induces another problem. So, I suggest to ignore the "Try to connect" messages as Dongjoon Hyun did, and wait for Jinho Kim's patch.

          Show
          jihoonson Jihoon Son added a comment - Hey Navis . I run 'mvn clean install -Pparallel-test,hcatalog-0.12.0 -DLOG_LEVEL=WARN -Dmaven.fork.count=2', and saw the following messages. Running org.apache.tajo.engine.query.TestJoinBroadcast 2015-04-01 15:37:39,450 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:37:42,968 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:37:46,480 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:37:49,992 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:37:53,512 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:37:57,030 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:00,543 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:04,057 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:07,576 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:11,094 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:14,614 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:18,132 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:21,646 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:25,158 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:28,677 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:32,196 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:35,707 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:39,226 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:42,734 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:46,243 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:49,757 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:53,268 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:38:56,791 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:39:00,306 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:39:03,828 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:39:07,347 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:39:10,859 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:39:14,374 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:39:17,895 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:39:21,407 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:39:24,926 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:39:28,445 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:39:31,960 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:39:35,481 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:39:38,988 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 Tests run: 48, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 124.784 sec - in org.apache.tajo.engine.query.TestJoinBroadcast Running org.apache.tajo.engine.query.TestJoinOnPartitionedTables 2015-04-01 15:39:42,511 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:39:46,033 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:39:49,548 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:39:53,060 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:39:56,575 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:00,094 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:03,612 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 22.84 sec - in org.apache.tajo.engine.query.TestJoinOnPartitionedTables Running org.apache.tajo.engine.query.TestJoinQuery 2015-04-01 15:40:07,122 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:10,641 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:14,161 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:17,680 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:21,193 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:24,706 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:28,225 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:31,743 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:35,259 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:38,774 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:42,289 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:45,807 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:49,322 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:52,837 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:56,356 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:40:59,876 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:41:03,394 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:41:06,911 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:41:10,426 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:41:13,948 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 2015-04-01 15:41:17,458 ERROR: org.apache.tajo.rpc.NettyClientBase (operationComplete(186)) - Max retry count has been exceeded. attempts=3 ... It seems that your patch induces another problem. So, I suggest to ignore the "Try to connect" messages as Dongjoon Hyun did, and wait for Jinho Kim 's patch.
          Hide
          githubbot ASF GitHub Bot added a comment -

          Github user navis commented on the pull request:

          https://github.com/apache/tajo/pull/488#issuecomment-88401983

          Sorry, I've not resolved address when reconnecting.

          Show
          githubbot ASF GitHub Bot added a comment - Github user navis commented on the pull request: https://github.com/apache/tajo/pull/488#issuecomment-88401983 Sorry, I've not resolved address when reconnecting.
          Hide
          githubbot ASF GitHub Bot added a comment -

          Github user jihoonson commented on the pull request:

          https://github.com/apache/tajo/pull/488#issuecomment-88697812

          +1
          I'll commit to ignore annoying messages which frequently incurs test failures.
          The fundamental problem will be solved in https://issues.apache.org/jira/browse/TAJO-1497

          Show
          githubbot ASF GitHub Bot added a comment - Github user jihoonson commented on the pull request: https://github.com/apache/tajo/pull/488#issuecomment-88697812 +1 I'll commit to ignore annoying messages which frequently incurs test failures. The fundamental problem will be solved in https://issues.apache.org/jira/browse/TAJO-1497
          Hide
          githubbot ASF GitHub Bot added a comment -

          Github user asfgit closed the pull request at:

          https://github.com/apache/tajo/pull/488

          Show
          githubbot ASF GitHub Bot added a comment - Github user asfgit closed the pull request at: https://github.com/apache/tajo/pull/488
          Hide
          githubbot ASF GitHub Bot added a comment -

          Github user jihoonson commented on the pull request:

          https://github.com/apache/tajo/pull/440#issuecomment-88703138

          Would you close this PR, please?

          Show
          githubbot ASF GitHub Bot added a comment - Github user jihoonson commented on the pull request: https://github.com/apache/tajo/pull/440#issuecomment-88703138 Would you close this PR, please?
          Hide
          jihoonson Jihoon Son added a comment -

          Committed to the master branch

          Show
          jihoonson Jihoon Son added a comment - Committed to the master branch
          Hide
          hudson Hudson added a comment -

          ABORTED: Integrated in Tajo-master-CODEGEN-build #280 (See https://builds.apache.org/job/Tajo-master-CODEGEN-build/280/)
          TAJO-1424: Investigate the problem of too many "Try to connect" messeges during Travic CI build. (jihoonson: rev 7c2a2409032c1bcd1fa9c636f0ef49982a995362)

          • CHANGES
          • tajo-rpc/tajo-rpc-protobuf/src/main/java/org/apache/tajo/rpc/RpcConnectionPool.java
          • tajo-rpc/tajo-rpc-protobuf/src/main/java/org/apache/tajo/rpc/NettyClientBase.java
          Show
          hudson Hudson added a comment - ABORTED: Integrated in Tajo-master-CODEGEN-build #280 (See https://builds.apache.org/job/Tajo-master-CODEGEN-build/280/ ) TAJO-1424 : Investigate the problem of too many "Try to connect" messeges during Travic CI build. (jihoonson: rev 7c2a2409032c1bcd1fa9c636f0ef49982a995362) CHANGES tajo-rpc/tajo-rpc-protobuf/src/main/java/org/apache/tajo/rpc/RpcConnectionPool.java tajo-rpc/tajo-rpc-protobuf/src/main/java/org/apache/tajo/rpc/NettyClientBase.java
          Hide
          hudson Hudson added a comment -

          SUCCESS: Integrated in Tajo-master-build #643 (See https://builds.apache.org/job/Tajo-master-build/643/)
          TAJO-1424: Investigate the problem of too many "Try to connect" messeges during Travic CI build. (jihoonson: rev 7c2a2409032c1bcd1fa9c636f0ef49982a995362)

          • tajo-rpc/tajo-rpc-protobuf/src/main/java/org/apache/tajo/rpc/RpcConnectionPool.java
          • tajo-rpc/tajo-rpc-protobuf/src/main/java/org/apache/tajo/rpc/NettyClientBase.java
          • CHANGES
          Show
          hudson Hudson added a comment - SUCCESS: Integrated in Tajo-master-build #643 (See https://builds.apache.org/job/Tajo-master-build/643/ ) TAJO-1424 : Investigate the problem of too many "Try to connect" messeges during Travic CI build. (jihoonson: rev 7c2a2409032c1bcd1fa9c636f0ef49982a995362) tajo-rpc/tajo-rpc-protobuf/src/main/java/org/apache/tajo/rpc/RpcConnectionPool.java tajo-rpc/tajo-rpc-protobuf/src/main/java/org/apache/tajo/rpc/NettyClientBase.java CHANGES
          Hide
          githubbot ASF GitHub Bot added a comment -

          Github user dongjoon-hyun commented on the pull request:

          https://github.com/apache/tajo/pull/440#issuecomment-88725492

          Absolutely!

          Show
          githubbot ASF GitHub Bot added a comment - Github user dongjoon-hyun commented on the pull request: https://github.com/apache/tajo/pull/440#issuecomment-88725492 Absolutely!
          Hide
          githubbot ASF GitHub Bot added a comment -

          Github user dongjoon-hyun closed the pull request at:

          https://github.com/apache/tajo/pull/440

          Show
          githubbot ASF GitHub Bot added a comment - Github user dongjoon-hyun closed the pull request at: https://github.com/apache/tajo/pull/440

            People

            • Assignee:
              navis Navis
              Reporter:
              jihoonson Jihoon Son
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development