Message boards :
Number crunching :
Problem with validation.
Message board moderation
Author | Message |
---|---|
Send message Joined: 24 Jul 23 Posts: 2 Credit: 113,244 RAC: 0 |
The minimum quorum is set to 2 but if 1 has been returned it is validated and the other workunit is Cancelled by server. Either change the initial replication from 2 to 1 or change the validation process. |
Send message Joined: 25 Jul 23 Posts: 2 Credit: 1,001,716 RAC: 0 |
I am seeing this same problem. Furthermore if the task was started and completed but returned minutes after the wingman it gets no credit for work done. It needs to be fixed. |
Send message Joined: 14 Jun 23 Posts: 275 Credit: 3,999,713 RAC: 7,188 |
Thank You for your message. Yes. There is such a problem. On short tests, I did not see it. We are looking into how this can be fixed. This may take time. We are very sorry. |
Send message Joined: 14 Jun 23 Posts: 432 Credit: 280,293 RAC: 0 |
Demis I propose to refuse quorum=2. The program has been tested for a long time and works stably. |
Send message Joined: 14 Jun 23 Posts: 275 Credit: 3,999,713 RAC: 7,188 |
Maybe. I think the current task needs to be worked on to the end In one day, we counted more than 20,000 tasks. If we continue at the same speed, then in 10 days 200,000 will be ready, and so on. Yes. There is a problem. I'm still thinking about how to solve it. I propose to count to the end. And release the next task with a quorum of 1. It is interesting to hear the opinion of crunchers. How can we do better? |
Send message Joined: 14 Jun 23 Posts: 432 Credit: 280,293 RAC: 0 |
Demis The problem with the deadline is described here https://boinc.termit.me/adsl/forum_thread.php?id=12&postid=161 You wrote that you launched a batch of 250,000 WUs. With a quorum of 2, 500,000 WUs will need to be calculated. This is a lot. It will count for almost a month. And existing problems make calculations difficult. |
Send message Joined: 14 Jun 23 Posts: 432 Credit: 280,293 RAC: 0 |
It is interesting to hear the opinion of crunchers. How can we do better? I think crunchers don't need quorum issues and deadline issues. I propose to stop issuing tasks, wait for all the tasks that are at the crunchers. Then solve the problem with the deadline and launch a new batch of tasks with a quorum of 1. At the same time it is necessary to solve the problem with communication (message notifications from subscribed topics). PS. Since the deadline is now valid not for 7 days, but only for a day, all tasks from crunchers will have to wait a day. |
Send message Joined: 15 Jun 23 Posts: 22 Credit: 10,821,491 RAC: 17,426 |
Users do not want their resources wasted by the server canceling tasks, especially if tasks are canceled while they are actively being worked on. |
Send message Joined: 14 Jun 23 Posts: 432 Credit: 280,293 RAC: 0 |
Users do not want their resources wasted by the server canceling tasks, especially if tasks are canceled while they are actively being worked on. Agree. Therefore, I propose to stop the distribution of tasks and solve all problems. |
Send message Joined: 16 Jun 23 Posts: 4 Credit: 1,585,484 RAC: 1,880 |
G'Day ADSL@Home team, With a quorum of 2 work units sent out in a project, it is usually done for the project to check that the results match and then credit is awarded to both volunteers. If there is a quorum of 2 but you only need 1 result then there is no reason to send out 2 work units, just send 1. Currently 2 are sent out but first one back gets the credit and the other is cancelled if it has not been started, or given the "Too late to validate" message if returned after the first work unit was returned. It would be an easier thing to allow both work units to run check results and award credit. You already send out 2 work units you would only need to check results and then award the credit if both are correct. Have a good day Conan |
Send message Joined: 14 Jun 23 Posts: 275 Credit: 3,999,713 RAC: 7,188 |
Problem fixed. It will take some time until new tasks arrive. |
Send message Joined: 14 Jun 23 Posts: 275 Credit: 3,999,713 RAC: 7,188 |
A very good tip. Thank you! |
Send message Joined: 14 Jun 23 Posts: 275 Credit: 3,999,713 RAC: 7,188 |
Users do not want their resources wasted by the server canceling tasks, especially if tasks are canceled while they are actively being worked on. Now, more precisely, very soon, half of the duplicate tasks will be canceled. From the moment this happens, those clients who have already received assignments may have questions. Be ready... |
Send message Joined: 24 Jul 23 Posts: 2 Credit: 113,244 RAC: 0 |
The work distribution and validation is still wrong. There are still 2 copies send out and when 1 is returned it is validated but gets zero credit. |
Send message Joined: 14 Jun 23 Posts: 275 Credit: 3,999,713 RAC: 7,188 |
The work distribution and validation is still wrong. I will cancel tasks. |
Send message Joined: 14 Jun 23 Posts: 432 Credit: 280,293 RAC: 0 |
Workunits waiting for validation 2780 https://boinc.termit.me/adsl/server_status.php Demis Why are there so many tasks waiting for validation? What is validation? |
Send message Joined: 26 Jul 23 Posts: 9 Credit: 10,124,696 RAC: 0 |
Tasks getting validated doesn't seem to be happening for a day now. None of my tasks have been validated in the last day. My credit score is the same as yesterday. Currently I have Validation pending (2320) and it's increasing steadily. Also I have to manually update to keep my queue full as the client is currently showing long times between updates. Something is going wrong with the project. Please look into it. |
Send message Joined: 26 Jul 23 Posts: 9 Credit: 10,124,696 RAC: 0 |
Now all I'm getting is validate errors. I'm aborting all remaining tasks. Not worth the effort. |
Send message Joined: 14 Jun 23 Posts: 432 Credit: 280,293 RAC: 0 |
Workunits waiting for validation 10893 https://boinc.termit.me/adsl/server_status.php Demis What's happening?? |
Send message Joined: 26 Jul 23 Posts: 9 Credit: 10,124,696 RAC: 0 |
25% of those tasks are mine waiting to be validated. I'm not hopeful they will get credit. Validation pending (3262) |
©2024 Natalia Makarova & Alex Belyshev & Tomáš Brada