[GitHub] [accumulo] cshannon commented on issue #3795: Place limit on fence begin and end row size.

["cshannon (via GitHub)" <gi...@apache.org>]

cshannon commented on issue #3795:
URL: https://github.com/apache/accumulo/issues/3795#issuecomment-1741763304

   Having some limit is probably good as long as it is configurable either with the existing property you mentioned or a new property.  The main concern here is that under normal use cases (at least for today, maybe new use cases will be used in the future) the ranges for fenced files are going to be generated as the merge and deletion operations will fence files using the existing rows in tablets. If the limit was hit then these operations could or would fail if the size was violated.
   
   So if it's configurable though it would allow someone who really wanted to run those operations to do so if they were ok with the consequences of large range keys.
   
   In practice, it's hard to say how much of a performance hit there would be until we test. The other thing is that most of the time (but not always of course) the ranges files will not be around for very long. Normal compaction cycles would eventually compact and get rid of them but of course there is no guarantee of that.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org