Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-3224 Observations from large scale testing.
  3. PHOENIX-3228

Index tables should not be configured with a custom/smaller MAX_FILESIZE

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 4.9.0, 4.8.1
    • None
    • None

    Description

      I do not think we should do this. The default of 10G is chosen to keep HBase happy. For smaller tables or initially until the index gets large it might lead to more index regions and hence be able to utilize more region server, but generally, this is not the right thing to do.

      Attachments

        1. 3228.txt
          2 kB
          Lars Hofhansl
        2. 3228-remove.txt
          6 kB
          Lars Hofhansl

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. PHOENIX-2762 Phoenix creating global index tables with MAX_FILESIZE of 11994435 (11.99 MB) when creating index on one column in a wide table.

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

          Activity

            People

              larsh Lars Hofhansl
              larsh Lars Hofhansl
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: