IBM Support

LI79829: THE UPGRADE TO 5.0.7 OR 5.0.8 FAILS DUE TO UNABLE TO UPGRADE THE MAPPINGS ERROR IN ELASTICSEARCH

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The upgrade to 5.0.7 or 5.0.8 API Manager fails due to unable
    to upgrade the mappings error in elasticsearch
    The error stack is :
    2017-09-12T09:12:36,070][ERROR][o.e.g.GatewayMetaState   ]
    [o28WMkZ] failed to read local state, exiting...
    java.lang.IllegalStateException: unable to upgrade the mappings
    for the index [[cmc-2017.01/zEzaQ-xxxxxxx]]
    at
    org.elasticsearch.cluster.metadata.MetaDataIndexUpgradeService.c
    heckMappingsCompatibility(MetaDataIndexUpgradeService.java:152)
    ~[elasticsearch-5.1.1.jar:5.1.1]
    at
    org.elasticsearch.cluster.metadata.MetaDataIndexUpgradeService.u
    pgradeIndexMetaData(MetaDataIndexUpgradeService.java:82)
    ~[elasticsearch-5.1.1.jar:5.1.1]
    at
    org.elasticsearch.gateway.GatewayMetaState.upgradeMetaData(Gatew
    ayMetaState.java:248) ~[elasticsearch-5.1.1.jar:5.1.1]
    at
    org.elasticsearch.gateway.GatewayMetaState.<init>(GatewayMetaSta
    te.java:91) [elasticsearch-5.1.1.jar:5.1.1]
    at
    sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
    Method) ~[?:?]
    at
    sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeCons
    tructorAccessorImpl.java:88) ~[?:?]
    To identify the error, execute the below command in APIM shell:
    debug tail file var/log/elasticsearch/apiconnect_analytics.log
    

Local fix

  • Contact IBM Support to move the problematic index
    

Problem summary

  • A management server upgrade from V5.0.0.0 through V5.0.6.X to
    5.0.7.X or later can cause elasticsearch to hang and prevent the
    management server from starting up. This is an infrequent
    problem.  You will see elasticsearch fail to sync in
    /var/log/messages and the elasticsearch log will show a
    "java.lang.IllegalStateException: unable to upgrade the mappings
    for the index [[cmc-2017.01/zEzaQ-xxxxxxx]]" message.
    

Problem conclusion

  • The problem has been fixed in API Connect 5.0.8.1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI79829

  • Reported component name

    API CONNECT ENT

  • Reported component ID

    5725Z2201

  • Reported release

    507

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-21

  • Closed date

    2017-11-10

  • Last modified date

    2017-11-10

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    API CONNECT ENT

  • Fixed component ID

    5725Z2201

Applicable component levels

  • R507 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"507","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 September 2021