we've recently upgraded from 1.4 to 2.3 and we can't seem to get our 1.4 indexes working. Anyone dealt with this issue?
We've tried updating the config files, copying the data to a "2.3" folder and ES just keeps crashing.
This is where our data is:
/var/lib/elasticsearch/elasticsearch_cognac
But updating the config file just add another '/elasticsearch' directory so it looks like this:
/var/lib/elasticsearch/elasticsearch_cognac/elasticsearch
Any help would be appreciated
You should first check if your 1.4 mappings are compatible with 2.3 before attempting the migration.
There is a specific plugin, called migration, that you need to install in your 1.4 cluster in order to get some insights whether you need to make some changes first (it looks like you do) or not.
Go to your 1.4 installation folder, and install the plugin
./bin/plugin -i elastic/elasticsearch-migration
Then start your ES and go to http://localhost:9200/_plugin/migration
You'll get plenty of info about what you need to change before attempting a migration.
Related
I just installed the elasticsearch (https://github.com/drud/ddev-elasticsearch) add-on on my DDEV site, which is listed on the ddev documents:
https://ddev.readthedocs.io/en/latest/users/extend/additional-services/
The problem is that I need to downgrade the Elasticsearch version to 7.6 and this add-on installed Elasticsearch at version 7.17.6.
I cant not find additional documentation on how to install the specific version of this Elasticsearch add-on, I see that the version is listed in the docker-compose.elasticsearch.yaml file, I tried changing it there, but it complain.
Any tips or reference will be appreciated, thanks
Using https://github.com/drud/ddev-elasticsearch mostly just installs a docker-compose.elasticsearch.yaml for you. You can change the version there.
Change image: elasticsearch:7.17.6 to an appropriate value. image: elasticsearch:7.6.2
You have to look at https://hub.docker.com/_/elasticsearch/tags to see what tags are available, but it looks like you probably want 7.6.2.
I am a newbie in this arena. Due to project demand, I had to install the newest version of Confluence. So, I have taken the backup and install confluence 6.12 on top of 6.6. After completing the installation when I hit the URL I have got the following error message.
Roll back the instance by restoring the backup you made prior to attempting the upgrade. Do this by creating a fresh Confluence install (I would recommend using the same version of Confluence that you used to create your XML backup). Restore the XML backup to this.
Get that site working normally first.
Then connect to a supported database.
Proceed with the upgrade.
I want to update a module on my running WildFly10.0.0.CR4 Server with the help of a cli file on Windows.
For example I would need this to update the Infinispan plugin from version 8.0.1.Final to version 8.0.2
According to a book I am referrencing to, this could be something like
jboss-cli.bat --file=myupdate.cli
where the myupdate.cli file contains the code telling the server what to do (In this case, update Infinispan). I just need to know what to enter into that file - Best would be an example with Infinispan and a documentation on how to write such a file for other plugins by myself.
Thank you in advance!
EDIT:
It may also just delete the old version and install a completely new one, if this is easier.
You don't really want to just update random libraries/modules. Some of them, such as Infinispan, are tightly coupled to the server.
For final releases you can use patching to update an existing server. You just need to download the patch for the container you want to update.
I have puppet 3.4.2 and Vagrant 1.6.5. We configured our puphpet setup over a year ago.
This is all working fine on my environment, but a fresh install downloads a new version of the base box which has an updated version of puppet and so our old configurations don't work.
We are using this box: https://atlas.hashicorp.com/puphpet/boxes/ubuntu1204-x64. I must have v1 but for new instances it will download v2.1
I have tried updating the puphpet config.yaml, but when I upload this to puphpet.com I get the message "The config file provided was empty! Please recreate your manifest manually below.".
So I see a few solutions but I have blockers on each of them:
Use the old base box. Is there an archive copy of V1 of this server somewhere on the internet? https://atlas.hashicorp.com/puphpet/boxes/ubuntu1204-x64
Use the new base box but downgrade Puppet. How do you downgrade Puppet and all it's dependancies?
Figure out some way of importing my config.yaml in to puphpet.com and start using the new versions. Is there anything I need to do to get puphpet.com to recognise an old file?
Reconfigure the whole file from scratch. Do you know anyone that can help me?
Thanks for advice.
It's still there, but no longer supported or publically listed.
All boxes come pre-installed with Puppet 3.4.3, which is BC with 3.4.2.
Sorry, changes in the past month or two have broken BC with old config.yaml files. You'll need to manually select your options again.
Just do this. Honestly, it's textboxes, dropdowns and radio boxes, and will take you less than 10 minutes.
Am looking to upgrade Mangeto from version 1.1.8 to version 1.5.
This is a quite a leap I am taking I know, but and I have tried the following already (as some one else had suggested on another site):
dump v1.1.8 database, restore it in a new database.
install magento 1.5 pointing on the restored v1.1.8 database
let the upgrader run
add the old theme files
test that it all works.
When doing that, the upgrader kept saying some tables already existed.
Can anyone help me out?
Thanks
It's fine now, basically make sure you're using the same server environment.