Skip to content

Latest commit

 

History

History
141 lines (102 loc) · 6.71 KB

upgrading_crossing_1-3-0.md

File metadata and controls

141 lines (102 loc) · 6.71 KB
Raw

Upgrading to 1.3.0 and beyond from a pre-1.3.0 version

This procedure has to be done always as long as your database contains at least one entity document or at least one context subscription document.

  • Stop contextBroker

  • Remove previous contextBroker version

    yum remove contextBroker

  • Take a backup of your DBs (this is just a safety measure in case any problem occurs, e.g some script gets interrupted before finished and your database data ends in an incoherent state)

  • Download the following scripts:

  • Install pymongo (it is a script dependency) in case you don't have it previously installed

    pip-python install pymongo

  • Apply the mdsvector2mdsobject.py script to your DBs, using the following command (where 'db' is the database name). Note that if you are using multitenant/multiservice you need to apply the procedure to each per-tenant/service database. The script can take a while, so an interactive progress counter is shown.

    python mdsvector2mdsobject.py orion

  • If you get any of the following messages, there is some problem that needs to be solved before going to the next step. Check the "Troubleshooting mdsvector2mdsobject" section below.

    WARNING: some problem was found during the process.
ERROR: document ... change attempt failed

  • Apply the csub_merge_condvalues.py script to your DBs, using the following command (where 'db' is the database name). Note that if you are using multitenant/multiservice you need to apply the procedure to each per-tenant/service database. The script can take a while, so an interactive progress counter is shown.

    python csub_merge_condvalues.py orion

  • If you get some of the following messages, there is some problem that needs to be solved before going to the next step. Check the "Troubleshooting csub_merge_condvalues" section below.

    WARNING: some csub were skipped
ERROR: document ... change attempt failed

  • Install new contextBroker version (Sometimes the commands fails due to yum cache. In that case, run "yum clean all" and try again)

    yum install contextBroker

  • Start contextBroker

Note that the rpm command demands superuser privileges, so you have to run it as root or using the sudo command.

Troubleshooting mdsvector2mdsobject

Three different kinds of problems may happen:

  • You get the following error message:

    OperationFailed: Sort operation used more than the maximum 33554432 bytes of RAM. Add an index, or specify a smaller limit.

    Try to create a suitable index with the following command in the mongo shell, then run mdsvector2mdsobject.py again.

    db.entities.createIndex({"_id.id": 1, "_id.type": -1, "_id.servicePath": 1})

    Once migration has ended, you can remove the index with the following command:

    db.entities.dropIndex({"_id.id": 1, "_id.type": -1, "_id.servicePath": 1})

  • Due to duplicated metadata names in a given entity while running mdsvector2mdsobject.py. The symptom of this problem is getting errors like this one:

    - <n>: dupplicate metadata detected in entity {"type": "...", "id": "...", "servicePath": "..."} (attribute: <attrName>): <MetadataName>. Skipping

    This may correspond to entities created with old Orion versions, which were using the name-type combination to identify metadata. The solution is to remove the duplicate metadata and re-run mdsvector2mdsobject.py. The procedure to remove duplicate metadata is similar to the one documented for duplicated attributes in this post at StackOverflow. In the case of doubts, please submit a question in StackOverflow (using "fiware-orion" tag to label your question).

  • Due to some unexpected problem during DB updating. The symptom of this problem is getting errors like this one:

    - <n>: ERROR: document <...> change attempt failed!

    There is no a general solution for this problem, it has to be analyzed case by case. If this happens to you, please have a look at the existing questions in StackOverflow about fiware-orion in order to check whether your problem is solved there. Otherwise create your own question (don't forget to include the "fiware-orion" tag and the exact error message in your case).

Troubleshooting csub_merge_condvalues

Two different kinds of problems may happen:

  • You get the following warning message:

    WARNING: some csub were skipped

    It means that some subscription document was skipped and not actually migrated. The subscription ID is provide as part of the script output, so the document can be located at DB and analyzed. Note that some skip causes are fine and not mean an actual problem. In particular "empty conditions" corresponds to subscriptions triggered by changes in any attribute, so they are fine. All the other causes may hide a potencial problem: the safest option is to remove the problematic documents (using db.csubs.remove({_id: ObjectId("<subscription ID>")>})) or fix them at DB (check DB model for csubs collection). In the case of doubt, please please have a look at the existing questions in StackOverflow about fiware-orion in order to check whether your problem is solved there. Otherwise create your own question (don't forget to include the "fiware-orion" tag and the exact error message in your case).

  • Due to some unexpected problem during DB updating. The symptom of this problem is getting errors like this one:

    - <n>: ERROR: document <...> change attempt failed!

    There is no a general solution for this problem, it has to be analyzed case by case. If this happens to you, please have a look at the existing questions in StackOverflow about fiware-orion in order to check whether your problem is solved there. Otherwise create your own question (don't forget to include the "fiware-orion" tag and the exact error message in your case).