From owner-freebsd-elastic@freebsd.org Wed May 16 13:30:33 2018 Return-Path: Delivered-To: freebsd-elastic@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E3880EE25B9 for ; Wed, 16 May 2018 13:30:32 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 935EE68AD0 for ; Wed, 16 May 2018 13:30:32 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 60C4E224FB; Wed, 16 May 2018 09:30:26 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Wed, 16 May 2018 09:30:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=dbhwYn 1ZMP6nkrTuzBYLI3c2xZbBBreTqFG05rxa9kY=; b=fGu6D3v92gzxveijlIpALt lBiPgM7rcnPrVLX9hNHwKYzQ3ZfLP70QrF00lU6bWmE5JCH0CWrgYWt1tzljD9jb vDxTfABMcGBqe7Afl77SxameAIn/GaTuCh/E7s58pNUgsaFzrl9OHjx19rQyNFss lzYu36hduFiFYI5ARbBRh+maw4JPewcgs9AcNEVqlZqX/odZAXWopF75q/QHMDNE AI8UTorqED8HFgVRrCgnetYEXLty8MD8V/2QA8rY++8FtJxv7oCNdIm7Qv4ZAE8e +PeMPlVMb9nt3sA1zJujdOvd2oldClghjtz7EhkXvaTZTZUZd3ASHWL9Cn0TjMpw == X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 043809E3E9; Wed, 16 May 2018 09:30:25 -0400 (EDT) Message-Id: <1526477425.413249.1374153960.39FDAF35@webmail.messagingengine.com> From: Mark Felder To: "O'Brien Wes (R0A) Manchester University NHS FT" Cc: freebsd-elastic@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-29fe4c42 References: <71872D6A2D22CD4C96AF216AC6B84B6EAAE9ABC7@V-UHSM-EX-04.UHSM.NHS.UK> Date: Wed, 16 May 2018 08:30:25 -0500 In-Reply-To: <71872D6A2D22CD4C96AF216AC6B84B6EAAE9ABC7@V-UHSM-EX-04.UHSM.NHS.UK> Subject: Re: Upgrade from Elasticsearch 5.x to 6.x in ports X-BeenThere: freebsd-elastic@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Support of ElasticSearch-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 May 2018 13:30:33 -0000 On Wed, May 16, 2018, at 04:33, O'Brien Wes (R0A) Manchester University NHS FT wrote: > Hello, we're using Elasticsearch 5.x installed from ports, however I was > wondering how I would upgrade to the 6.x version as they are two > separate ports; it was suggested to me that I should just uninstall 5.x > as it won't remove any index data and then install 6.x - is this the > recommended way to do it? Once I've installed 6.x do I just point the > configuration file to where my index data is and it'll just work? > > Thanks for any advice. > > That's pretty much the procedure. Do you have a multi-node cluster? If so, you'll have to be careful about how you upgrade. It's not very straightforward as you have to stop ingesting data, freeze/flush the nodes, then upgrade them one at a time. Once they are all at the new version you can return things back to normal. The tooling for this is very poor, IMO... https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html -- Mark Felder ports-secteam & portmgr member feld@FreeBSD.org