Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-7476

test_statestore.py statestore client persists after the test is over

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • Impala 3.1.0
    • Impala 3.1.0
    • Infrastructure
    • None
    • ghx-label-8

    Description

      test_statestore.py does several python tests that build statestore clients to unit test statestored. Based on the logs from statestored, these test clients persist long after the test_statestore.py has completed. They continue to exist for the rest of the invocation of pytest.

      This results in a large amount of logging like this:

      I0821 16:55:46.583678 25215 thrift-util.cc:123] TSocket::open() connect() <Host: localhost Port: 46256>Connection refused
      I0821 16:55:46.583820 25215 thrift-client.cc:78] Couldn't open transport for localhost:46256 (connect() failed: Connection refused)
      I0821 16:55:46.583890 25215 thrift-client.cc:94] Unable to connect to localhost:46256
      I0821 16:55:46.583959 25215 statestore.cc:930] Unable to send heartbeat message to subscriber python-test-client-aad157c8-a59c-11e8-814d-484d7ea85cac, received error: Couldn't open transport for localhost:46256 (connect() failed: Connection refused)
      I0821 16:55:46.585145 25222 thrift-util.cc:123] TSocket::open() connect() <Host: localhost Port: 42796>Connection refused
      I0821 16:55:46.585315 25222 thrift-client.cc:78] Couldn't open transport for localhost:42796 (connect() failed: Connection refused)
      I0821 16:55:46.585371 25222 thrift-client.cc:94] Unable to connect to localhost:42796
      I0821 16:55:46.585429 25222 statestore.cc:930] Unable to send heartbeat message to subscriber python-test-client-b5fb8650-a59c-11e8-8307-484d7ea85cac, received error: Couldn't open transport for localhost:42796 (connect() failed: Connection refused)
      

      This does not seem to impact any tests, but it does produce some log spew in the normal output.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            joemcdonnell Joe McDonnell
            joemcdonnell Joe McDonnell
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment