Uploaded image for project: 'ZooKeeper'
  1. ZooKeeper
  2. ZOOKEEPER-4821

ConnectRequest got NOTREADONLY ReplyHeader

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 3.8.4, 3.9.2
    • None
    • java client, server
    • None

    Description

      I would expect ConnectRequest has two kinds of response in normal conditions: ConnectResponse and socket close. But if sever was configured with readonlymode.enabled but not localSessionsEnabled, then client could get NOTREADONLY in reply to ConnectRequest. I saw, at least, no handling in java client. And, I encountered this in writing tests for rust client.

      It guess it is not by design. And we probably could close the socket in early phase. But also, it could be solved in client sides as sizeof(ConnectResponse) is larger than sizeof(ReplyHeader). Then, we gain ability to carry error for ConnectRequest while ConnectResponse does not.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. ZOOKEEPER-3863 Do not track global sessions in ReadOnlyZooKeeperServer

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          links to

          Web Link document the need for local sessions within the readonly mode

          Activity

            People

              Unassigned Unassigned
              kezhuw Kezhu Wang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: