querysub 0.700.0 → 0.701.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "querysub",
-  "version": "0.700.0",
+  "version": "0.701.0",
   "main": "index.js",
   "license": "MIT",
   "note1": "note on node-forge fork, see https://github.com/digitalbazaar/forge/issues/744 for details",

package/src/-a-archives/archives2.ts

@@ -41,6 +41,8 @@ function createSourceWindows(
 
 function archiveBuilder(bucket: string, overrides: Partial<RemoteConfigBase>) {
     const ONTARIO = `https://99-250-124-91.querysubtest.com:5234/file/${STORAGE_ACCOUNT}/${bucket}/storage/storagerouting.json`;
+    // NOTE: This is on an overly large extra disk that's on our 4090 machine. I prefer to not use it because it might slow down diffusion, but it's quite large (2tb, and diffusion will never use more than 1tb), so we could use it if we needed to.
+    const ONTARIO2 = `https://99-250-124-91.querysubtest.com:5235/file/${STORAGE_ACCOUNT}/${bucket}/storage/storagerouting.json`;
     const HETZNER = `https://65-109-93-113.querysubtest.com:5234/file/${STORAGE_ACCOUNT}/${bucket}/storage/storagerouting.json`;
     const BACKBLAZE = `https://f002.backblazeb2.com/file/${bucket}/storage/storagerouting.json`;
 
@@ -76,6 +78,12 @@ function archiveBuilder(bucket: string, overrides: Partial<RemoteConfigBase>) {
                 // NOTE: Once we add new sources, we need to add something at a new start time in the future so we have time to move the files. 
                 // TODO: EVENTUALLY, Once we have enough data, instead of restriping, we need to bisect the data. That way we can slowly move over the data instead of trying to rewrite all of our data all at once. However, for the moment, moving all the data is probably fine. On the data center, we should be able to move terabytes of data every hour, so we should be able to handle quite a bit, especially if we have a few days to run the restriping. 
                 // IMPORTANT! Every time we re-stripe, we need to increment the route version. Otherwise, we could reuse a folder that we previously used that's no longer in sync. which will cause us to resurrect old data, which is very bad. We don't want to do that...
+                // NOTE: We do full redundancy, so if the ranges are a, b, c, then its:
+                //   s0=a s1=b s2=c
+                //   s0=c s1=a s2=b
+                //   s0=b s1=c s2=a
+                //  Essentially, we just shift it every time. So every server has all the data, But the primary writers are divided between all the servers. 
+                //  (If you follow A, you can see it's diagonal, B is diagonal, they're all diagonal, like stripes).
                 ...stripeSources([ONTARIO, HETZNER], { routeVersion: 2 }),
                 { type: "backblaze", url: BACKBLAZE, name: "backblaze" },
             ]
@@ -83,7 +91,7 @@ function archiveBuilder(bucket: string, overrides: Partial<RemoteConfigBase>) {
     ]);
 
     return createArchives({
-        version: 28,
+        version: 29,
         sources,
     });
 }

package/src/deployManager/machineApplyMainCode.ts

@@ -93,12 +93,12 @@ const getDiskInfos = measureWrap(async function getDiskInfos(): Promise<DiskInfo
             }
             disks.push({ device, mountPoint, value, max });
         }
+        sort(disks, disk => -disk.max);
         let large = disks.filter(disk => disk.max >= LARGE_DISK_MIN_BYTES);
-        if (large.length > 0) {
-            disks = large;
+        if (large.length === 0) {
+            large = disks.slice(0, 1);
         }
-        sort(disks, disk => -disk.max);
-        return disks;
+        return large;
     } catch (e: any) {
         console.warn(`Error getting disk info: ${e.stack}`);
     }