[ 
https://issues.apache.org/jira/browse/HDDS-8385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17714702#comment-17714702
 ] 

George Jahad edited comment on HDDS-8385 at 4/20/23 6:03 PM:
-------------------------------------------------------------

[~umamaheswararao] 

I was unfamiliar with the TarContainerPacker.java code, but based on   
Wei-Chiu's suggestion,

I did set it in TarContainerPacker.java here: 
[https://github.com/apache/ozone/pull/4580/files#diff-dace84a8cb4c9227812fd21e76250bfe72b84db25f02d76bab30fea0dc68531b]


was (Author: georgejahad):
[~umamaheswararao] 

I was unfamiliar with the code, but based on   Wei-Chiu's suggestion,

I did set it in TarContainerPacker.java here: 
https://github.com/apache/ozone/pull/4580/files#diff-dace84a8cb4c9227812fd21e76250bfe72b84db25f02d76bab30fea0dc68531b

> Ozone can't process snapshot when service UID > 2097151
> -------------------------------------------------------
>
>                 Key: HDDS-8385
>                 URL: https://issues.apache.org/jira/browse/HDDS-8385
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: Snapshot
>            Reporter: Prashant Pogde
>            Assignee: George Jahad
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.4.0
>
>
> With Ozone OM HA configured, the process that tar's up a snapshot fails.
> {{{}2023-03-31 12:51:15,272 ERROR 
> org.apache.hadoop.hdds.utils.DBCheckpointServlet: Unable to process metadata 
> snapshot request.{}}}{{{}java.lang.IllegalArgumentException: group id 
> '1301600003' is too big ( > 2097151 ). Use STAR or POSIX extensions to 
> overcome this limit{}}}
>  
> {{The only solution at this time was to rework my service account UID's to a 
> value below 2097151.}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to