[GitHub] [accumulo] keith-turner edited a comment on issue #1998: Decide behavior of external compactions when a table is taken offline.

[GitBox <gi...@apache.org>]

keith-turner edited a comment on issue #1998:
URL: https://github.com/apache/accumulo/issues/1998#issuecomment-818040783


   > Can you give a brief summary of what happens when an external compaction completes?
   
   1. The compactor makes an RPC call the compaction coordinator to let it know the compactions completed
   2. The coordinator writes an entry to the ~ecomp section of the metadata table recording the compaction completed AND queues up an async RPC to the tablet to let it know the ext compaction completed.
   3. The coordinator periodically scans the ~ecomp section of the metadata table looking for tablets to notify
   4. When the tablet recieves the message that an external compaction completed, it does some sanity checks and if everything looks ok it will :
      1. Update tablets in memory list of files
      2. Update tablet metadata (deleting the tablets information about the external compaction and updating the files atomically in a single mutation)
      3. Delete ~ecomp entry from metadata table


-- 
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.

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