VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Minor
    • Resolution: Won't Fix
    • None
    • None
    • None
    • None

    Description

      Canary is marked as a Private class. Its interfaces could change at any time. Should we change the annotation on Canary to Public/Evolving? Or add annotations on some of these subtypes? I think it depends on how we think Canary results should be consumed.

      In our production we find that scraping logs and parsing them is brittle and not scalable. Although the scalability issue is more to do with the totality of logs from a Hadoopish stack, if you run HBase then you have this problem, and you wouldn't be using the canary if you didn't run HBase. We have a tool that embeds the Canary and calls various methods and takes actions without needing a round trip to the logs and whatever aggregates them.

      I propose we promote Canary to Public/Evolving.

      Attachments

        1. HBASE-22823.master.000.patch
          0.9 kB
          Caroline Zhou
        2. HBASE-22823.branch-1.000.patch
          1 kB
          Caroline Zhou
        3. HBASE-22823.branch-2.000.patch
          0.9 kB
          Caroline Zhou

        Issue Links

        Activity

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

          People

            caroliney14 Caroline Zhou
            apurtell Andrew Kyle Purtell
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment