From solr-user-return-148349-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Mon Jun 10 22:32:48 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id EA4CA180649 for ; Tue, 11 Jun 2019 00:32:47 +0200 (CEST) Received: (qmail 51138 invoked by uid 500); 10 Jun 2019 22:32:44 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 51126 invoked by uid 99); 10 Jun 2019 22:32:42 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Jun 2019 22:32:42 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id E313E1A4247 for ; Mon, 10 Jun 2019 22:32:41 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.802 X-Spam-Level: * X-Spam-Status: No, score=1.802 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=semandex.net Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id gQzU0NXEgMz4 for ; Mon, 10 Jun 2019 22:32:40 +0000 (UTC) Received: from mail-pg1-f177.google.com (mail-pg1-f177.google.com [209.85.215.177]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 4807D5FBC9 for ; Mon, 10 Jun 2019 22:32:40 +0000 (UTC) Received: by mail-pg1-f177.google.com with SMTP id n2so5755929pgp.11 for ; Mon, 10 Jun 2019 15:32:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semandex.net; s=gmail; h=mime-version:from:date:message-id:subject:to; bh=IbHVbVTXHSkCFK/TQmqfdhh+Qbqz+vtOjfr45IWlGsU=; b=ra4d/BEZIOnGtv8gj6ALOQvV/qpdFJ9nDUxJTArIhOX6FKyr5rRbCRo5Y/0He6t/cE 9rBtuX1yLK8Qgk+fv26gjFC9o3brPAZIPTS4LJyxqxOryJLptmSdHpC9OAY2KyxUDR/p iD9fDfhSerH9gc63jB/QwXb18z4GLqjNg5Jmc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=IbHVbVTXHSkCFK/TQmqfdhh+Qbqz+vtOjfr45IWlGsU=; b=umjeeqePbef0fJty49j7Fv5eUwk+7zHOdiT5cjAfVm1d1WR6E/viKOdSMoqTvsVOQC t6KIBUHhSaGjvDhUGyX+vkqSfUgyeWO0rmY+X6DbQBKloenJQdoyxjG52uUHC/DbcPNS IaeMi+iP3nEagPwkO9oTGbKTVs8waKWhZFvT3MBxdmLq6Tv9sQmCcsuszLfsKtROGz+y wCMS+qaGBX2CvI0SXzA0I9LFTgXT8ulFNN5mqsXXr/1qPdTeCl+JpmRla73wiDES+ib4 d3cwY0YrTbADtGWO/YxtFsqyfuq/ZlvprgLKoOqZK+Xji/FyDqDiMEY3u8deKdT7hwPl IGIg== X-Gm-Message-State: APjAAAU3Xr8F1LTzp80vE20byeKz5qZ3zi/S7PxYYY0qVVKUhUt6J0ad Qie9V6a6wLjMInKM7Azrn1wWNLsiLY1prYqB+HUTb8vOsZnBRQ== X-Google-Smtp-Source: APXvYqx+WC7GDoyxgAbzNqG4MHG6diuEAgOqdHUSRUEklYeI9nGyuhspDADOqZnCR9aP1fXHgeVdGrUOisj1D9kWE00= X-Received: by 2002:a62:5306:: with SMTP id h6mr77727061pfb.29.1560205959127; Mon, 10 Jun 2019 15:32:39 -0700 (PDT) MIME-Version: 1.0 From: Pratik Patel Date: Mon, 10 Jun 2019 18:32:28 -0400 Message-ID: Subject: How to increase maximum size of files allowed in configuration for MiniSolrCloudCluster To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary="000000000000f8758a058affc1b0" --000000000000f8758a058affc1b0 Content-Type: text/plain; charset="UTF-8" Hi, I am trying to upload a configuration to "MiniSolrCloudCluster" in my unit test. This configuration has some binary files for NLP related functionality. Some of these binary files are bigger than 5 MB. If I try to upload configuration with these files then it doesn't work. I can set up the cluster fine if I remove all binary files bigger than 5 MB. I have noticed the same issue when I try to restore a backup having configuration files bigger than 5 MB. Does jetty have some limit on the size of configuration files? Is there a way to override this? Thanks, Pratik --000000000000f8758a058affc1b0--