You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by "HistoryGift (via GitHub)" <gi...@apache.org> on 2023/03/27 04:32:12 UTC
[GitHub] [druid] HistoryGift opened a new issue, #13979: how to mograte data from one historical to another in the same cluster
HistoryGift opened a new issue, #13979:
URL: https://github.com/apache/druid/issues/13979
I meet one problem, but I can't find any reference file .
I want migrate data from one historical to another in the same cluster ,because one historical node need to down
if I shutdown historical service directly, will the segments on historical lose ? and will the statement of segment on ZK result in new istorical cannot load those segemnt?
--
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: commits-unsubscribe@druid.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
[GitHub] [druid] kfaraz commented on issue #13979: how to mograte data from one historical to another in the same cluster
Posted by "kfaraz (via GitHub)" <gi...@apache.org>.
kfaraz commented on issue #13979:
URL: https://github.com/apache/druid/issues/13979#issuecomment-1491814724
1. Segments are permanently stored in deep storage (e.g. S3). If a historical goes down, nothing is lost permanently and the missing segments can always be loaded on a different historical.
2. When a historical goes down, the segments being served by that historical would become under-replicated or even unavailable if the segment had only 1 copy in the cluster.
3. When segments are unavailable, queries would not return data for that segment.
4. As soon as the new historical loads these missing segments, the data is available for query again.
If you don't want data to be unavailable at any point, the method of doing this right now is to mark the historical as "decommissioning". The Druid coordinator would then move all segments on this "decommissioning" historical to other active historicals. Once all segments are removed from the "decomissioning" historical, it can be safely terminated.
Please refer to the configuration in the docs here for example usage of "decomissioning":
https://druid.apache.org/docs/latest/configuration/index.html#dynamic-configuration
--
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: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
Re: [I] how to mograte data from one historical to another in the same cluster (druid)
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #13979:
URL: https://github.com/apache/druid/issues/13979#issuecomment-1984824746
This issue has been closed due to lack of activity. If you think that
is incorrect, or the issue requires additional review, you can revive the issue at
any time.
--
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: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
Re: [I] how to mograte data from one historical to another in the same cluster (druid)
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #13979:
URL: https://github.com/apache/druid/issues/13979#issuecomment-1935131276
This issue has been marked as stale due to 280 days of inactivity.
It will be closed in 4 weeks if no further activity occurs. If this issue is still
relevant, please simply write any comment. Even if closed, you can still revive the
issue at any time or discuss it on the dev@druid.apache.org list.
Thank you for your contributions.
--
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: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org
Re: [I] how to mograte data from one historical to another in the same cluster (druid)
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #13979: how to mograte data from one historical to another in the same cluster
URL: https://github.com/apache/druid/issues/13979
--
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: commits-unsubscribe@druid.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org