GC control of use-per-document-delete and max-merge-memory from config production side in java.

1 files changed, 0 insertions, 19 deletions

diff --git a/flags/src/main/java/com/yahoo/vespa/flags/Flags.java b/flags/src/main/java/com/yahoo/vespa/flags/Flags.java
index e800792af4f..4aac29c5093 100644
--- a/flags/src/main/java/com/yahoo/vespa/flags/Flags.java
+++ b/flags/src/main/java/com/yahoo/vespa/flags/Flags.java
@@ -421,25 +421,6 @@ public class Flags {
             "Whether to send cloud trial email notifications",
             "Takes effect immediately");
 
-    public static final UnboundLongFlag MERGING_MAX_MEMORY_USAGE_PER_NODE = defineLongFlag(
-            "merging-max-memory-usage-per-node", 0,
-            List.of("vekterli"), "2023-11-03", "2024-03-01",
-            "Soft limit of the maximum amount of memory that can be used across merge operations on a content node. " +
-            "Value semantics: < 0: unlimited (legacy behavior), == 0: auto-deduced from node HW and config," +
-            " > 0: explicit memory usage limit in bytes.",
-            "Takes effect at redeployment",
-            INSTANCE_ID);
-
-    public static final UnboundBooleanFlag USE_PER_DOCUMENT_THROTTLED_DELETE_BUCKET = defineFeatureFlag(
-            "use-per-document-throttled-delete-bucket", true,
-            List.of("vekterli"), "2023-11-13", "2024-03-01",
-            "If set, DeleteBucket operations are internally expanded to an individually persistence-" +
-            "throttled remove per document stored in the bucket. This makes the cost model of " +
-            "executing a DeleteBucket symmetrical with feeding the documents to the bucket in the " +
-            "first place.",
-            "Takes effect at redeployment",
-            INSTANCE_ID);
-
     public static final UnboundBooleanFlag ENABLE_NEW_PAYMENT_METHOD_FLOW = defineFeatureFlag(
             "enable-new-payment-method-flow", false,
             List.of("bjorncs"), "2023-11-29", "2024-03-01",