Aetherstore in the real world
-
@Breffni-Potter looks like you killed the AetherStore Drive Manager process, or the AetherStore Daemon service. Restarting the Daemon service or running 'aetherstore-drive-manager.exe' in Program Files -> AetherStore -> Core will cause the drive to re-mount on that machine. If you killed the process manually then you probably know how to restart it
an alternative (and much simpler) solution is to just log out/log in and it'll re-mount by itself. -
@Rob said:
@Breffni-Potter looks like you killed the AetherStore Drive Manager process, or the AetherStore Daemon service.
Not deliberately
-
Is this a glitch? Or a sign of something wrong with the data.
-
That's a known timezone translation glitch in that spot on UI - great catch!
-
@Breffni-Potter ah - well-spotted. Please refer to the 'last sync' column in the data grid for the time being - looks like we've addressed that in v1.2.4 (releasing soon). As an FYI: you'll get a notification on the home screen of your dashboard when there's a new version available, and there's an 'update all' button that will push out the new version to your nodes automatically.
I see a backlog of a couple q's - gotta finish up some work here at the moment but I'll hop back in a bit and make sure to get you across all the info you need
-
Some performance tests
When Aetherstore is first powered up, the average speed is around 10 MB per second.
After it is settled, it can go as high as 20 MB per second but the average is around 15.
The read speed can go as high as 25 MB per second. -
The test network are virtual machines running on SSDs, the VMs themselves measure performance of 450 MB per second when testing the
drive. This performance was measured on the node where the drive was mounted.http://mangolassi.it/topic/7020/ntg-partners-with-aetherstore/30
So the performance matches what Aetherstore says it will be.
After dumping a load of data into a store, the read/write speeds do not suffer whilst it does the background task of replicating to other nodes. Even if I force a sync from the dashboard.
So far so good in terms of performance.
-
Awesome, thanks for the lab work!
-
Ok, if you are an AetherStore user
Do not - Delete a store - Unless you really mean to delete them and the computers that are part of the Store are online.
If the computers part of the store are offline, what happens is the DashBoard will not be able to delete them and the store is left in a broken state. You can't re-deploy the existing machines.
To fix it, go onto the offending machines, uninstall the node software and delete the AetherStore folder from
and reinstall it. -
@Breffni-Potter said:
Ok, if you are an AetherStore user
Do not - Delete a store - Unless you really mean to delete them and the computers that are part of the Store are online.
If the computers part of the store are offline, what happens is the DashBoard will not be able to delete them and the store is left in a broken state. You can't re-deploy the existing machines.
To fix it, go onto the offending machines, uninstall the node software and delete the AetherStore folder from
and reinstall it.Yeah, I learned this the hard way during the alpha. Kind of sad that it is still a problem. Hope they build in a method to fix that.
-
@JaredBusch said:
Yeah, I learned this the hard way during the alpha. Kind of sad that it is still a problem. Hope they build in a method to fix that.
Thankfully it's the only broken feature discovered in testing, hopefully it will be fixed.
-
@Breffni-Potter said:
@JaredBusch said:
Yeah, I learned this the hard way during the alpha. Kind of sad that it is still a problem. Hope they build in a method to fix that.
Thankfully it's the only broken feature discovered in testing, hopefully it will be fixed.
Hi everyone! I'm Renee, the Product Quality Manager over here at AetherStore. @Breffni-Potter, thanks for all your testing and interest in AetherStore! Just a quick comment about what happens when you delete Stores when some machines are offline: You are correct that you will observe the smoothest behavior if you delete the Store while all machines are offline. However, if you delete the Store while some machines are offline, the behavior you are seeing isn’t actually a bug.
In the case when some machines are offline , you will see in the “Delete Store” pop-up that the machines that are still online are successfully deleted. The machines that are offline return a failure—this is expected, because the Dashboard cannot communicate with them, so there is no way they could delete the Store. For example, in the screenshot below x86-win8-1 could not be deleted because it was offline, but the other nodes were removed successfully:
If at this point, you turned on x86-win8-1, waited a few minutes, and clicked “Try Again”, it would successfully remove the Store altogether. However, if you click “Done” before turning on the missing machine and instead return to the “Manage Existing Store” page, the Store is gone, because the Dashboard can’t communicate with any machines in the Store and thinks it has deleted it. Then, if the machines that were offline come back online, the Dashboard will re-discover the Store, but if you go to the “Store Summary” page for that Store, you will notice that only the machines that failed originally are still included in the Store. The machines that were successfully deleted remain deleted. At this point, you can delete the Store again from the “Manage Existing Store” page, and observe that the last remaining machine(s) are successfully deleted, as below:
Uninstalling and reinstalling on the machines that were offline when the Store was originally deleted should not be necessary.
This is quite a lengthy reply, but I hope it clarifies things! Let me know if you have any questions!
-
@ReneeHayter welcome to the community!
