To avoid such slow writes (and possible data loss due to missing replicas ) Shards are unassigned/unreachable due to a missing node. Stall until the replica becomes active or an internal timeout of `30s` is If not all defined N shards for this new partition are active, the write will Setting into account and such this setting will partly affect writes here. In case of a partitioned table, new partitions are created on-fly taking this
The `wait_for_active_shards` value only affects table (or partition) creation So if you issue a query right after writing a messageĪnd QuantumLeap picks node B, probability to find the data you just pushed Writes on Crate node A, first the data is indexed in node A, and then Of multi-node CrateDB deployment this can take even more because QuantumLeap Is stored in crate, and when it is actually available for querying. So this means that there is additional latency between when the a message Especially in the case of CrateDB, indexing of inserted data may take a bit, The QuantumLeap takes some msec to process a single message and store it inġ. Orion takes some msec to process a request and trigger a notification.ġ. Latency between the data writing and the time the data is available for reading.ġ. QuantumLeap is a Timeseries API that stores values forwarded by the Context Broker,Īnd due to the nature of its backends as well, there is always some synch # Sometimes it takes more than 500 msec to read the data sent to Orion in QuantumLeap If you spot an error such as: : SQLActionException) 3D Coordinates are not working when using CrateDB as backend Of time slice (on the top-right corner of grafana) is actually covering a time Make sure you have enough data points in your database and that your selection I got no errors but I cannot see data in my Dashboards You may be missing an important parameter in your request. Have a look at the message in the returned body for hints of what could have These are flagged in the API specification. Is the endpoint you are using implemented? Note for now some of them are not. Open the corresponding ports? (See the Ports section.)Īre you using the correct FIWARE headers for the tenant? Refer to the Multi-tenancy Subscription a resolvable url for the containerised Orion? Review theĪre you running the different components behind firewalls? If so, did you Is the location of QuantumLeap expressed in the notify_url field of the Subscription? I.e, will Orion trigger notifications for that insert/update?Ĭan you see such subscription if you query Orion subscriptions? When is its
Review theĪre you inserting/updating attributes listed in the "condition" of the The subscription NGSIv2 and WITHOUT the "keyValues" option?. Have you created a subscription for the entity type you are inserting? Is Please ask yourself the following questions: If you don't see your data being saved in the database, before reporting a bug FAQs Followed the instructions, but nothing happens Something not working as expected? Don't worry! the expected thing is for itĬheckout the following section to make sure you didn't miss a critical step,Īnd if none of that applies to your case, then proceed to the Bug reporting.
0 kommentar(er)
