Details

    • Type: Brainstorming Brainstorming
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Not A Problem
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Is it just me or do others sense that there is pressure building to redo the client? If just me, ignore the below... I'll just keep notes in here. Otherwise, what would the requirements for a client rewrite look like?

      + Let out InterruptedException
      + Enveloping of messages or space for metadata that can be passed by client to server and by server to client; e.g. the region a.b.c moved to server x.y.z. or scanner is finished or timeout
      + A different RPC? One with tighter serialization.
      + More sane timeout/retry policy.

      Does it have to support async communication? Do callbacks?

      What else?

        Issue Links

          Activity

          Andrew Purtell made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Not A Problem [ 8 ]
          stack made changes -
          Link This issue is related to HBASE-2182 [ HBASE-2182 ]
          stack made changes -
          Link This issue relates to HBASE-4956 [ HBASE-4956 ]
          stack made changes -
          Link This issue relates to HBASE-2170 [ HBASE-2170 ]
          stack made changes -
          Link This issue relates to HBASE-1843 [ HBASE-1843 ]
          stack made changes -
          Link This issue relates to HBASE-1844 [ HBASE-1844 ]
          stack made changes -
          Link This issue relates to HBASE-3382 [ HBASE-3382 ]
          stack made changes -
          Link This issue relates to HBASE-2937 [ HBASE-2937 ]
          stack made changes -
          Link This issue incorporates HBASE-3584 [ HBASE-3584 ]
          stack made changes -
          Summary Rewrite our client Rewrite our client (client 2.0)
          stack made changes -
          Field Original Value New Value
          Link This issue incorporates HBASE-2408 [ HBASE-2408 ]
          stack created issue -

            People

            • Assignee:
              Unassigned
              Reporter:
              stack
            • Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development