[GitHub] [accumulo] dlmarion opened a new issue, #3208: Multiple Managers: Review code that modifies metadata table, modify it to use Ample

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

dlmarion opened a new issue, #3208:
URL: https://github.com/apache/accumulo/issues/3208

   There are classes that update the metadata table (e.g. MetadataTableUtil) that do not use Ample. Suggest finding and modifying these classes to use Ample in preparation for having multiple Manager processes and Ample using conditional mutations.


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

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

[GitHub] [accumulo] ddanielr commented on issue #3208: Multiple Managers: Review code that modifies metadata table, modify it to use Ample

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

ddanielr commented on issue #3208:
URL: https://github.com/apache/accumulo/issues/3208#issuecomment-1505421533

   So this has turned into a bit of a rats nest. 
   
   I started working on removing the managerMetadataUtil class and separating those functions into their respective calling classes.
   
   While there were some improvements there, overall it uncovered a LOT of various actions happening in managerMetadataUtil and MetadataTableUtil that are not using ample for metadata actions. 
   
   The majority of these all fall under Split Tablet and Clone Table operations. 
   
   I also found that ProblemReport uses a reserved prefix of  "~err_" but is not included in the metadata schema at all.


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

[GitHub] [accumulo] ddanielr commented on issue #3208: Multiple Managers: Review code that modifies metadata table, modify it to use Ample

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

ddanielr commented on issue #3208:
URL: https://github.com/apache/accumulo/issues/3208#issuecomment-1460372883

   I started looking into this. 


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

[GitHub] [accumulo] ctubbsii commented on issue #3208: Multiple Managers: Review code that modifies metadata table, modify it to use Ample

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

ctubbsii commented on issue #3208:
URL: https://github.com/apache/accumulo/issues/3208#issuecomment-1507691940

   @ddanielr The metadata has a few distinct sections. The tablets section is first, and covers all the metadata for tablets. After that, there is a separate entire section starting with `~` that is for metadata that is not part of a particular tablet. That's where the `~del` entries exist for the accumulo-gc to pick up files that are candidates for deletion, and I guess the `~err` section also exists in there. Those regions of the metadata are independent of the schema for tablet metadata.


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