Incident #212: MongoDB for usageTracker should be upgraded. - D4Science Infrastructure - D4science

Actions

Copy link

Incident #212

closed

MongoDB for usageTracker should be upgraded.

Added by Roberto Cirillo over 10 years ago. Updated over 10 years ago.

Status:

Closed

Priority:

Urgent

Assignee:

Roberto Cirillo

Category:

Data Management

Target version:

UnSprintable

Start date:

Jun 04, 2015

Due date:

% Done:

100%

Estimated time:

(Total: 0.00 h)

Infrastructure:

Production

Description

On node57.p (UsageTracker) run 32-bit mongoDB. This version is limited to only 2GB of datasize.
At this time it seems that we can not add new records because we have already reached the maximum limit.
On catalina log I see this error:

SEVERE: The RuntimeException could not be mapped to a response, re-throwing to the HTTP container
com.mongodb.WriteConcernException: { "serverUsed" : "localhost/127.0.0.1:27017" , "err" : "can't map file memory - mongo requires 64 bit build for larger datasets" , "code" : 10084 , "n" : 0 , "connectionId" : 55 , "ok" : 1.0}

I'm going to analyze if is possible to upgrade to 64bit version

Subtasks 1 (0 open — 1 closed)

Actions

Copy link

Updated by Roberto Cirillo over 10 years ago

The problem seems to be: 32 bit linux DISTRIBUTION with 64 Bit KERNEL.
I'm not able to donwload a 64bit package by apt-get but if I run arch command I see x86_64; Is this possible?

Actions

Copy link

Updated by Roberto Cirillo over 10 years ago

I've changed the UsageTracker configuration for mongoDB. Now the UsageTracker service is connected to the new machine and the new records are correctly stored on the new mongodb instance

Actions

Copy link