@riocrypto/common-server 1.0.2917 → 1.0.2919

package/build/models/order.js

@@ -403,11 +403,22 @@ const buildOrder = (mongoose) => {
     orderSchema.index({ payoutAutoRetryAt: 1 }, { sparse: true });
     orderSchema.index({ userId: 1, "TWAP.sessionId": 1, createdAt: 1 });
     orderSchema.index({ brokerId: 1, "TWAP.sessionId": 1, createdAt: 1 });
+    // The stuck order scans (the admin task in admin-tasks and the payout
+    // auto-complete in orders) both select on status alone, which no index above
+    // has as a prefix, so each run scanned the whole collection. The first serves
+    // the side + status pairs the auto-complete looks for, the second gives the
+    // admin task its createdAt bound after the status bounds.
+    orderSchema.index({ status: 1, side: 1 });
+    orderSchema.index({ status: 1, createdAt: 1 });
     orderSchema.index({ clientReferenceId: 1 }, { sparse: true });
     orderSchema.index({ "paymentsReceived.blockchainTxId": 1 }, { sparse: true });
     // At most one order per real quoteId. Imported orders use quoteId "" and are
     // excluded by the partial filter (which also serves the createOrder lookup).
     orderSchema.index({ quoteId: 1 }, { unique: true, partialFilterExpression: { quoteId: { $gt: "" } } });
+    // Looking up an order by quote matches on quoteId or expiredQuotes in one
+    // $or, and an $or falls back to a collection scan unless every branch is
+    // indexed. Without this the partial quoteId index above never gets used.
+    orderSchema.index({ expiredQuotes: 1 });
     // At most one order per (broker family, clientReferenceId). rootUserId is
     // brokerId || userId; orders without a clientReferenceId (or, defensively,
     // without rootUserId) are excluded from the constraint.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@riocrypto/common-server",
-  "version": "1.0.2917",
+  "version": "1.0.2919",
   "description": "",
   "main": "./build/index.js",
   "types": "./build/index.d.ts",