Project

General

Profile

Actions

Task #3878

closed

Upgrade #3868: D4Science Infrastructure Upgrade to gCube 3.11.0

Upgrade #3873: D4Science Gateways upgrade to gCube 3.11.0

Task #3876: Prepare Elastic Cluster instance for gCube 3.11.0

Please create new VM with Elastic Search of Production

Added by Massimiliano Assante over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
High
Assignee:
_InfraScience Systems Engineer
Category:
Other
Start date:
May 04, 2016
Due date:
May 13, 2016
% Done:

100%

Estimated time:
2.00 h
Infrastructure:
Production

Description

A new VM having 4 CPU, at least 2GB RAM and 50GB Disk. Elastic Search Version 2.3.2

Ssh access to me and Costantino Perciante, same config of #2110

Actions #1

Updated by Andrea Dell'Amico over 9 years ago

  • Status changed from New to In Progress

elastic0-p-d4s.d4science.org will have IP 146.48.122.131

Actions #2

Updated by Andrea Dell'Amico over 9 years ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 100

elastic0-p-d4s.d4science.org is ready. The configuration is identical to the one on the dev node, the only change is the cluster name.

Actions #3

Updated by Massimiliano Assante over 9 years ago

@costantino.perciante@isti.cnr.it please check the VM and close the ticket if everything is as expected (as it should)

Actions #4

Updated by Costantino Perciante over 9 years ago

  • Status changed from Feedback to Closed

I've just checked and it seems fine. I've also prepared the index for the data that is going to be indexed. However, I'm not able to check it, but I suppose the port 9300 on the machine is open too (it is needed to contact the index from java).

Actions #5

Updated by Tommaso Piccioli over 9 years ago

Connections to port 9300 are allowed only from the servers network, from nb-assante and pc-costantino.

Actions #6

Updated by Costantino Perciante over 9 years ago

Perfect, thanks!

Actions #7

Updated by Costantino Perciante over 9 years ago

  • Status changed from Closed to In Progress

We have problem to start the indexer plugin on production. I've just seen that the elasticsearch node in dev has the 2.2.0 version whereas in production the 2.3.2 has been used. Can you downgrade the production version to 2.2.0? Thanks

Actions #8

Updated by Andrea Dell'Amico over 9 years ago

I need to remove the installed version in advance. Is this a problem?

Actions #9

Updated by Massimiliano Assante over 9 years ago

not at all, please proceed

Actions #10

Updated by Andrea Dell'Amico over 9 years ago

Done. 2.2.0 is up and running.

Actions #11

Updated by Costantino Perciante over 9 years ago

  • Status changed from In Progress to Closed

I am looking the logs now and it seems the indexer plugin is working. Unfortunately the needed documents structure is missing into the new elasticsearch node, so the search functionality cannot be used properly. However, that's another problem. Thanks Andrea

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)