Project

General

Profile

Actions

Task #9341

closed

Remove couchbase library from enabling services

Added by Roberto Cirillo almost 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Application
Start date:
Jul 21, 2017
Due date:
% Done:

100%

Estimated time:
Infrastructure:
Development

Description

In order to remove the accounting load from enabling services in production environment, it's needed to test the accounting "empty" library in development environment.
I've just replaced the following lib:

document-store-lib-couchbase

with the following one

 document-store-lib-no-insert 1.0.0

on the following hosts:

node8-d-d4s        collector (/gcube)
node9-d-d4s        registry (/gcube)
node6-d-d4s         resourceManager (/gcube) 
dlib01              collector (devsec)
node3.d.d4science  registry (devsec)

in about one hour I'm going to recheck the hosts above with the aid of @luca.frosini@isti.cnr.it

Actions #1

Updated by Roberto Cirillo almost 8 years ago

  • Status changed from New to In Progress
Actions #2

Updated by Roberto Cirillo almost 8 years ago

As suggested by @luca.frosini@isti.cnr.it I've added the following accessPoint to the Accounting service endpoint resource:

      <AccessPoint>
         <Description>Persistence No Insert</Description>
         <Interface>
            <Endpoint EntryName="PersistenceNoInsert">PersistenceNoInsert</Endpoint>
         </Interface>
         <AccessData>
            <Username />
            <Password>MwDldJhEXBV7c2zXKQQdTQ==</Password>
         </AccessData>
         <Properties>
            <Property>
               <Name>AggregationSchedulerTime</Name>
               <Value encrypted="false">30</Value>
            </Property>
            <Property>
               <Name>BufferRecordNumber</Name>
               <Value encrypted="false">1</Value>
            </Property>
            <Property>
               <Name>BufferRecordTime</Name>
               <Value encrypted="false">30</Value>
            </Property>
         </Properties>
      </AccessPoint>

Actions #3

Updated by Roberto Cirillo almost 8 years ago

After the update of the ServiceEndpoint resource, it's needed to restart the VMs above in order to discover the new settings.
I'm going to restart all the VMs.

Actions #4

Updated by Roberto Cirillo almost 8 years ago

  • Status changed from In Progress to Feedback
  • Assignee changed from Roberto Cirillo to Luca Frosini
  • % Done changed from 0 to 100

The VMs have been restarted. I've checked the logs and now I don't see any exception.
Please @luca.frosini@isti.cnr.it could you give me a feedback before to start the upgrade in production environment?

Actions #5

Updated by Luca Frosini almost 8 years ago

  • Status changed from Feedback to Closed

It seems working.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 8.91 MB)