Fast Data Error Codes
In this page are collected all the codes associated to errors that may be generated by Fast Data core components.
Each error code is grouped under a specific category to help understanding which component operation may have raised the error.
Moreover, for each of them is provided a brief explanation of what caused it and which are the steps that should be taken
to potentially resolve the encountered issue.
Real-Time Updater
Coming soon
Projection Storer
In case of any doubt, please refer to service documentation, which can be found here.
| Error Code | Category | Cause | Action |
|---|---|---|---|
| FD_PS_E0001 | Configuration | service configuration file has not been found or its format is not supported | ensure that configuration file set in environment variable CONFIG_FILE_PATH exitsts and it is either a valid json or yaml file |
| FD_PS_E0002 | Configuration | provided service configuration is invalid | ensure that provided json or yaml file respects the configuration schema, as described in the documentation. Note: the error should provide more insights on the issue |
| FD_PS_E0003 | Configuration | no projection has been associated to the service | ensure that at least one valid projection definition is attached to the service configuration. An example can be found in the documentation |
| FD_PS_E0004 | Configuration | selected storage type is unknown or not supported | in the service configuration verify that type property of storage component is set to one of accepted values, as described in the documentation |
| FD_PS_E0005 | Configuration | selected consumer type is unknown or not supported | in the service configuration verify that type property of consumer component is set to one of accepted values, as described in the documentation |
| FD_PS_E0006 | Configuration | selected producer type is unknown or not supported | in the service configuration verify that type property of producer component is set to one of accepted values, as described in the documentation |
| FD_PS_E0007 | Configuration | one of provided custom cast function has not been found, recognized or is invalid | ensure that the custom functions configuration are set as described in the documentation, that the custom cast function file is in the proper location, there is a function whose signature name is the same assigned under the castFunctions properties. Note: in case the cast function is invalid and it can not be evaluated, the service will throw this error |
| FD_PS_E1001 | Startup | selected message adapter type is unknown or not supported | in the service configuration settings verify that type property of dataSourceAdapter component is set to one of accepted values, as described in the documentation |
| FD_PS_E1002 | Startup | component configuration lead to initialization failure | ensure that provided options under storage property within service configuration file are valid and matches selected storage type |
| FD_PS_E1003 | Startup | component configuration lead to initialization failure | ensure that provided options under consumer property within service configuration file are validand matches selected consumer type |
| FD_PS_E1004 | Startup | component configuration lead to initialization failure | ensure that provided options under producer property within service configuration file are valid and matches selected producer type |
| FD_PS_E1005 | Startup | custom message adapter has not been loaded | ensure that selected custom message adapter configured in dataSourceAdapter service configuration settings points to an existing file. If that is correct, please verify that provided file contains a Javascript function definition and there exists a function named messageAdapter, as described in the service documentation |
| FD_PS_E1006 | Runtime | executing custom message adapter resulted into an invalid output | provided custom message adapter logic should contain a function named messageAdapter with a signature matching what is described in the documentation. Note: this error may be raised event when the logic is expected to produce the correct output, but its execution is throwing due to invalid or malformed record |
| FD_PS_E2001 | Consumer | unrecoverable error | the service should restart since it cannot proceed further without losing some record. At restart, the service will try to reprocess the same records since the consumer has not carried out the checkpoint operation. Configuration or incoming data on connected topics should be checked only in case the service restarts indefinitely |
| FD_PS_E2002 | Consumer | consumer commit/checkpointing operation has failed | the service should restart since it has not been able to checkpoint processed events. At restart, the service will try to reprocess the same records since the consumer has not carried out the checkpoint operation. This should be a transient error, since it may occur only in case the consumer abruptly disconnects |
| FD_PS_E2003 | Consumer | consumer cannot access topic on cluster | specified topic may not exists or employed credentials do not allow the access to configured topic. Please verify topic existence and which ACL are assigned to the consumer |
| FD_PS_E3001 | Producer | producer failed to send and event | an error occurred while producing an output event (projection record update). The error should be transient, and the service should automatically retry processing the same set of events before giving up and restarting |
| FD_PS_E3002 | Producer | producer cannot access topic on cluster | specified topic may not exists or employed credentials do not allow the access to configured topic. Please verify topic existence and which ACL are assigned to the producer |
| FD_PS_E4001 | Storage | empty projections operations list provided to the storage component | all the incoming change events were filtered out by the message adapter validation. This occur when the wrong message adapter is selected or incoming change events do not follow the expected format of selected message adapter. It is recommended to verify whether the dataSourceAdapter is correctly configured and whether the origin system (System of Record) is producing events in the expected format |
| FD_PS_E4002 | Storage | projection record provided to the storage does not have a valid identifier | one of the received change events is missing from the payload the fields that uniquely identifies it (the primary key fields). Please review the incoming message since the service may begin to restart indefinitely to avoid losing changes |
| FD_PS_E4003 | Storage | no projection name provided to the storage component to write projections | please verify that each projection under the projections property of service configuration file contains the property storageNamespace with a non-blank value. It is also fine when property storageNamespace is not provided, since projection name would be employed as default value |
| FD_PS_E4004 | Storage | error encountered while writing projections records on the storage | an error occurred while writing projection records onto the storage system. The error should be transient, and the service should automatically retry processing the same set of events before giving up and restarting |
| FD_PS_E4005 | Storage | storage component is not connected and ready for storing operations | this is a transient error. The service should briefly reconnect automatically. Otherwise, it would restart |
| FD_PS_E5001 | Processor | malformed key | please verify incoming events on the topic |
| FD_PS_E5002 | Processor | malformed payload | please verify incoming events on the topic |
| FD_PS_E5003 | Processor | invalid operation type | one of the incoming change events does not have a valid operation type or can not be mapped to a known operation type. Please verify incoming events on the topic |
| FD_PS_E7001 | Internal Events | internal communication has failed due to timeout | the service should retry autonomously failed operation, so that no change event, projection stored is lost. No action is required, unless the service begin to restart indefinitely. |
Single View Trigger Generator
In case of any doubt, please refer to service documentation, which can be found here.
| Error code | Category | Cause | Action |
|---|---|---|---|
| FD_SVTG_E0001 | Configuration | failed loading one of the service config map | verify that files provided in the config maps are all JSON files using utf8 charset |
| FD_SVTG_E0002 | Configuration | one or more strategy is invalid | in the config map loaded from KAFKA_PROJECTION_UPDATES_FOLDER verify that the value of identifier property in each strategy path matches either __automatic__ or __fromFile[<filename>]__ |
| FD_SVTG_E0003 | Configuration | single view does not have any strategy path | in the config map loaded from KAFKA_PROJECTION_UPDATES_FOLDER verify that specified single view exists and it has at least one strategy path associated to it |
| FD_SVTG_E0004 | Configuration | no manual strategy folder has been provided | specify a value for environmental variable MANUAL_STRATEGIES_FOLDER, representing the folder path where manual strategies files can be found |
| FD_SVTG_E0005 | Configuration | manual strategy identifier is malformed | in the config map loaded from KAFKA_PROJECTION_UPDATES_FOLDER ensure that each identifier configured as __fromFile[<strategy-identifier>]__ has a <strategy-identifier> defined |
| FD_SVTG_E0006 | Configuration | manual strategy has not been found or was not possible to load it | in the config map loaded from KAFKA_PROJECTION_UPDATES_FOLDER ensure that each identifier configured as __fromFile[<strategy-identifier>]__ has a <strategy-identifier> pointing to an existing javascript file (containing an async generator function exported by default) in the folder defined in environment variable MANUAL_STRATEGIES_FOLDER |
| FD_SVTG_E0007 | Configuration | a config map did not pass its JsonSchema validation | check out the validation errors described by the error log and modify accordingly the invalid config map |
| FD_SVTG_E2001 | Runtime - Message Parsing | a message with an unexpected format received | verify that message causing trouble has the correct format (pr-update) |
| FD_SVTG_E2002 | Runtime - Event Store | service found an error with the underlying event store techology | check the service error logs to see what caused this error, it could be related to the event store configuration or simply an unavailability of the underlying technology |
Single View Creator
Coming soon