I'm trying to determine the correct upgrade process for a 3 node cluster running 9.x sitting behind a load balancer.
Looking at the cluster configuration we find :
Node 1 has forests and is the boot node ( likely the d-node ) and 300GB free.
Node 2 has no forests and has 700 GB free disk space ( likely an e-node ).
Node 3 has no forests and has 700 GB free disk space ( likely an e-node ).
Can I confirm that the correct cluster upgrade sequence from 9.x to 10.x Server is :
Shutdown node 3,2,1 ( in that order )
Deinstall converters then deinstall Server 9.x from Node 1
Deinstall converters then deinstall Server 9.x from Node 2 and Node 3
Install Server 10.x then install converters on Node 1 & restart Node 1
Install Server 10.x then install converters on Node 2 & 3 and restart both nodes.
Have I missed anything?
Is there anything I can look for on each node that tells me specifically that a node is an e-node or d-node?
Thanks.
Unless you are attempting to perform a rolling-upgrade (probably not necessary for a small 3-node cluster that only has one D-node), it is easiest to just shut them all down, uninstall the converters and MarkLogic, install the new version of server and converters, then start them all up and complete the upgrade in the Admin UI.
https://docs.marklogic.com/guide/installation/procedures#id_77358
Stop MarkLogic Server (as described in step 1 of Removing MarkLogic).
Uninstall the old MarkLogic 9 release (as described in Removing MarkLogic).
If you want to uninstall MarkLogic 9.0-4 or later, and if the converters package was previously installed with it, you will have to perform a two-step uninstall: first uninstall MarkLogic Converters and then uninstall MarkLogic Server. For more detail, see MarkLogic Converters Installation Changes Starting at Release 9.0-4 and Removing MarkLogic.
Install the new MarkLogic 10 release (as described in Installing MarkLogic).
If you want to install MarkLogic 9.0-4 or later, and you plan to use the converters package with it, you will have to perform a two-step installation: first install MarkLogic Server and then install MarkLogic Converters. For more detail, see MarkLogic Converters Installation Changes Starting at Release 9.0-4 and Installing MarkLogic.
Start MarkLogic Server (as described in Starting MarkLogic Server).
Open the Admin Interface in a browser (http://localhost:8001/).
When the Admin Interface prompts you to upgrade the databases and the configuration files, click the button to confirm the upgrade.
Related
I want to install redis 5.0.7 in CentOS 8 but 5.0.3 is the only avaliable rpm.
Is it safe to install from source?
If you trust the source provider -- e.g. you downloaded from one of redis' servers -- then you should be fine.
Their site shows they also provide hashes for integrity: https://redis.io/download#how-to-verify-files-for-integrity
But, it also states the hashes don't match for the 'generic redis-stable.tar.gz tarball'
I need to upgrade our redis cluster(s) from v3.2.12 to latest (v6). What would be the easiest route for upgrading?
We run Redis as well as Sentinel on each node.
3 node cluster -> 1 master, 2 slaves
Thank you very much
The upgrade is pretty standard. i would suggest to upgrade in this order.
First upgrade the sentinel nodes which are currently are slaves/replica nodes.
After upgrade is completed, it will sync from master node, note that a node can sync from version 3 to version 6 node but not vice-versa.( You can't go back to earlier version)
Use sentinel to Failover to upgraded node.
Upgrade the old master node.
I need to do integration testing for a spring cloud application running with spring data on redis.
Tests work locally with the regular redis server instance and I need to run this on a Jenkins CI server that is controlled by the corporate CI engineering group.
Obviously I can attach to a redo server there so I used an embedded redis server (from here: https://github.com/kstyrc/embedded-redis).
Running tests locally with this redis server works well since there is a test profile to inject the embedded server in place of the production one.
Now the problem is that when we run this in the Jenkins environment this is the error we see.
/tmp/1430170830037-0/redis-server-2.8.19: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by /tmp/1430170830037-0/redis-server-2.8.19)
So this version of redis has specific dependency on a specific version of glibc. I tried a couple of other libraries but they all depend on the same underlying version of the embedded redis server.
Is there a spring data mock framework that can be used to get around this sort of issue?
This might come a little late for you, but there is indeed a Spring Data Mock framework that you can use, which let's you mock repositories (regardless of the specific backend solution) without a real database connection.
Here is a link: https://github.com/mmnaseri/spring-data-mock
You don't have a high enough version of libc6, that is causing the error.
From How to fix “/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found”? – Super User:
That means the program was compiled against glibc version 2.14, and it requires that version to run, but your system has an older version installed. You'll need to either recompile the program against the version of glibc that's on your system, or install a newer version of glibc (the "libc6" package in Debian).
So, you just need to upgrade your libc6 package. All versions of Ubuntu have at least version 2.15 because it's a faily important package (reference).
To upgrade it, use these commands in a terminal:
sudo apt-get update
sudo apt-get install libc6
p.s. This is answer from askubuntu.com by minerz029
I've installed redis-server using apt-get install redis-server and everything went fine.
Right now I'm trying to configure it in a Cluster mode. The problem is that in the tutorial supplied here http://redis.io/topics/cluster-tutorial they use a script called redis-trib.rb which I can't find it in my system.
Can you please tell me how can I configure my Redis to run in Cluster mode without that script ?
I would like to have a setup with two masters, each on a different machine.
Thank you very much.
Had same problem with reredis-trib.rb
This tutorial explains how to create Redis Cluster using only Redis commands: Configuring and Running Redis Cluster on Linux
You need Redis 3.0.0 beta to run Cluster. You'll not find it in a Linux distribution, since they all have copy of the stable server (fortunately!). Redis 3.0.0 will go out as a stable release the next week. You can find the source code of the stable release here: http://redis.io/download.
There is now a tutorial for Ubuntu at https://www.digitalocean.com/community/tutorials/how-to-configure-a-redis-cluster-on-ubuntu-14-04 which includes installation of a PPA to supply 3.0.x. This tutorial is only for two nodes and does not reference redis-trib.rb ...
Is there a guide on how to do this easily? I want to upgrade it without losing all the configuration settings etc. Is there a particular method to achieve this (or config files that I can just copy to the new installation). I'm running it as a windows service at the moment so the new version will need to run in the same way too.
Thanks.
There isn't an upgrade script that will do it for you, at least not that I've ever used/found. Which, is actually a good thing, IMO. You can simply download the newer Tomcat version to a different directory than your current install (c:/tomcat55 and c:/tomcat6) and copy the configuration from you 5.5 installation. Nearly all of the basic settings are the same from 5.5 to 6.0.x, not as sure about 7.0. If you install the new service with a different service name, you don't have to worry about any conflicts (except the ports in your server.xml)
If this is a production box, I would recommend changing the ports on your new installation so you can run it alongside your current install, and test your applications before you switch over. If all is OK, you can shutdown your new Tomcat, update the ports to be what your current install is, shutdown Tomcat5.5, and start your new install and you should be good. Of course you can always run the new install on the different port, but if you're using Apache in front, you'll have to update the Apache config as well.
Hope this helps.