After sealing, the file is transferred to HDD. The designated worker works like AP PC1 PC2 tasks enable/disable emove #8936
-
Checklist
Lotus component
What is the motivation behind this feature request? Is your feature request related to a problem? Please describe.After sealing, the file is transferred to HDD. The designated worker works like AP PC1 PC2 tasks enable/disable emove Describe the solution you'd likeThe move task provides control commands and configurations Describe alternatives you've consideredNo response Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 2 replies
-
|
Hey @bxs17! I´m not sure I understand the question, could you maybe expand a bit more about what you are wondering about/what issue you are facing? 😄 |
Beta Was this translation helpful? Give feedback.
-
|
The seal worker does not have persistent storage attached. After sealing, miner gets to persistent storage. You want to specify the worker to perform the get move operation. There is a switch to set whether miner opens the get move task。tasks type is？fget？
…---Original---
From: ***@***.***>
Date: Tue, Jun 28, 2022 13:51 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [filecoin-project/lotus] After sealing, the file is transferredto HDD. The designated worker works like AP PC1 PC2 tasks enable/disable emove(Discussion #8936)
Hey @bxs17! I´m not sure I understand the question, could you maybe expand a bit more about what you are wondering about/what issue you are facing? 😄
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Okay, so if I understand correctly, you want a worker to move the data to the long term storage? If so one option is to just run lotus-worker on storage boxes with all compute tasks disabled; this way all storage accesses are going through independent tcp streams, and straight to whatever filesystem. But that requires:
To run a worker on the a storage box, just so it schedules the moving of sectors, just disable all tasks with: |
Beta Was this translation helpful? Give feedback.
-
|
Tried. But miner can also do transfer tasks. The task was not given to the worker. Whether miner can be closed
W？
…---Original---
From: ***@***.***>
Date: Tue, Jun 28, 2022 14:51 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [filecoin-project/lotus] After sealing, the file is transferredto HDD. The designated worker works like AP PC1 PC2 tasks enable/disable emove(Discussion #8936)
Okay, so if I understand correctly, you want a worker to move the data to the long term storage?
If so one option is to just run lotus-worker on storage boxes with all compute tasks disabled; this way all storage accesses are going through independent tcp streams, and straight to whatever filesystem. But that requires:
Post workers for reading challenges from remote storage: https://lotus.filecoin.io/storage-providers/seal-workers/post-workers/
To run a worker on the a storage box, just so it schedules the moving of sectors, just disable all tasks with: lotus-worker run --no-default
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
That is probably because your lotus-miner still has the paths to the long-term storage. The scenario I outlined above, is where the lotus-miner is only doing the scheduling, and has windowPoSt-workers attached, and therefore does not need the paths to the long-term storage on it. In your case it sound like the lotus-miner still has storage-paths set, so if you want to move to an architecture where only the workers does the transfers task you would need to remove them. As a general advice here, please test out this setup first before chaning it on your production. And also keep a backup of the storage.json file. |
Beta Was this translation helpful? Give feedback.
-
|
Or in other words, how to improve the priority of worker move tasks。
lotus-worker run --no-default
Can it be achieved
…---Original---
From: ***@***.***>
Date: Tue, Jun 28, 2022 15:34 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [filecoin-project/lotus] After sealing, the file is transferredto HDD. The designated worker works like AP PC1 PC2 tasks enable/disable emove(Discussion #8936)
But miner can also do transfer tasks.
That is probably because your lotus-miner still has the paths to the long-term storage. The scenario I outlined above, is where the lotus-miner is only doing the scheduling, and has windowPoSt-workers attached, and therefore does not need the paths to the long-term storage on it.
In your case it sound like the lotus-miner still has storage-paths set, so if you want to move to an architecture where only the workers does the transfers task you would need to remove them. As a general advice here, please test out this setup first before chaning it on your production. And also keep a backup of the storage.json file.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
miner conf
[Storage]
AllowMove = false?
Is this configuration available
?
…------------------ 原始邮件 ------------------
发件人: "filecoin-project/lotus" ***@***.***>;
发送时间: 2022年6月28日(星期二) 下午3:34
***@***.***>;
***@***.******@***.***>;
主题: Re: [filecoin-project/lotus] After sealing, the file is transferred to HDD. The designated worker works like AP PC1 PC2 tasks enable/disable emove (Discussion #8936)
But miner can also do transfer tasks.
That is probably because your lotus-miner still has the paths to the long-term storage. The scenario I outlined above, is where the lotus-miner is only doing the scheduling, and has windowPoSt-workers attached, and therefore does not need the paths to the long-term storage on it.
In your case it sound like the lotus-miner still has storage-paths set, so if you want to move to an architecture where only the workers does the transfers task you would need to remove them. As a general advice here, please test out this setup first before chaning it on your production. And also keep a backup of the storage.json file.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hey @bxs17! As far as I know, that is not an configuration available on the |
Beta Was this translation helpful? Give feedback.
-
|
So add task configuration in the next version.
…------------------ 原始邮件 ------------------
发件人: "filecoin-project/lotus" ***@***.***>;
发送时间: 2022年6月30日(星期四) 凌晨3:07
***@***.***>;
***@***.******@***.***>;
主题: Re: [filecoin-project/lotus] After sealing, the file is transferred to HDD. The designated worker works like AP PC1 PC2 tasks enable/disable emove (Discussion #8936)
Hey @bxs17! As far as I know, that is not an configuration available on the lotus-miner currently.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Which version can use --no-default
Which version can use --no-default
***@***.***
----------------- 原始邮件 ------------------
发件人: "filecoin-project/lotus" ***@***.***>;
发送时间: 2022年6月28日(星期二) 下午2:51
***@***.***>;
***@***.******@***.***>;
主题: Re: [filecoin-project/lotus] After sealing, the file is transferred to HDD. The designated worker works like AP PC1 PC2 tasks enable/disable emove (Discussion #8936)
Okay, so if I understand correctly, you want a worker to move the data to the long term storage?
If so one option is to just run lotus-worker on storage boxes with all compute tasks disabled; this way all storage accesses are going through independent tcp streams, and straight to whatever filesystem. But that requires:
Post workers for reading challenges from remote storage: https://lotus.filecoin.io/storage-providers/seal-workers/post-workers/
To run a worker on the a storage box, just so it schedules the moving of sectors, just disable all tasks with: lotus-worker run --no-default
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @bxs17
|
Beta Was this translation helpful? Give feedback.
That is probably because your lotus-miner still has the paths to the long-term storage. The scenario I outlined above, is where the lotus-miner is only doing the scheduling, and has windowPoSt-workers attached, and therefore does not need the paths to the long-term storage on it.
In your case it sound like the lotus-miner still has storage-paths set, so if you want to move to an architecture where only the workers does the transfers task you would need to remove them. As a general advice here, please test out this setup first before chaning it on your production. And also keep a backup of the storage.json file.