Re: [geomesa-users] how to fix disappeared index table in geomesa accumu

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [geomesa-users] how to fix disappeared index table in geomesa accumulo

From: Emilio Lahr-Vivaz <elahrvivaz@xxxxxxxx>
Date: Mon, 11 Apr 2022 09:12:58 -0400
Delivered-to: geomesa-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/geomesa-users/>
List-help: <mailto:geomesa-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/geomesa-users>, <mailto:geomesa-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/geomesa-users>, <mailto:geomesa-users-request@eclipse.org?subject=unsubscribe>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0

Hello,

I'm not sure what would cause the tables to get out of sync - possibly the age-off you have configured is interfering with the table partitioning. Generally those two aren't combined, as it's faster to set up a cron job to drop the tables instead of using a filter on all queries. Still, I wouldn't expect that to cause the tables to be completely dropped, they would just end up empty; also it would drop older tables and not the newer ones that seem to be missing. Generally, GeoMesa doesn't drop tables, so there may be something else going on. Have you checked the logs in your cluster for any information? You might reach out to the Accumulo community for help trying to recover the tables - but to get queries working again, you could also just delete the bad references in the GeoMesa catalog table, so that it will stop trying to query them.

Thanks,

Emilio

On 4/11/22 7:23 AM, Rinchin Gomboev wrote:

In my accumulo db data is next, why these tables are not presented and how to restore them? Thank you

root@accumulo> tables -ns myNamespace

geomesa

geomesa_SignalBuilder_attr_cam_time_v8_02712

geomesa_SignalBuilder_attr_cam_time_v8_02716

geomesa_SignalBuilder_attr_cam_time_v8_02723

geomesa_SignalBuilder_attr_cam_time_v8_02724

geomesa_SignalBuilder_attr_cam_time_v8_02725

geomesa_SignalBuilder_z2_geo_v5_02712

geomesa_SignalBuilder_z2_geo_v5_02716

geomesa_SignalBuilder_z2_geo_v5_02723

geomesa_SignalBuilder_z2_geo_v5_02724

geomesa_SignalBuilder_z2_geo_v5_02725

geomesa_SignalBuilder_z3_geo_time_v7_02712

geomesa_SignalBuilder_z3_geo_time_v7_02716

geomesa_SignalBuilder_z3_geo_time_v7_02723

geomesa_SignalBuilder_z3_geo_time_v7_02724

geomesa_SignalBuilder_z3_geo_time_v7_02725

geomesa_stats

root@accumulo> table myNamespace.geomesa

root@accumulo myNamespace.geomesa> scan

SignalBuilder~attributes : [] *geo:Point,time:Date,cam:String:keep-stats=true,imei:String,dir:Double,alt:Double,vlc:Double,sl:Integer,ds:Integer,dir_y:Double,poi_azimuth_x:Double,poi_azimuth_y:Double;geomesa.stats.enable='true',geomesa.feature.expiry='time(30 days)',geomesa.z.splits='4',geomesa.table.partition='time',geomesa.index.dtg='time',geomesa.attr.splits='4',geomesa.indices='z3:7:3:geo:time,z2:5:3:geo,attr:8:3:cam:time',geomesa.z3.interval='week'

SignalBuilder~stats-date : [] 2022-04-11T10:11:14.134Z

SignalBuilder~table.attr.cam.time.v8.02712 : [] myNamespace.geomesa_SignalBuilder_attr_cam_time_v8_02712

SignalBuilder~table.attr.cam.time.v8.02716 : [] myNamespace.geomesa_SignalBuilder_attr_cam_time_v8_02716

SignalBuilder~table.attr.cam.time.v8.02723 : [] myNamespace.geomesa_SignalBuilder_attr_cam_time_v8_02723

SignalBuilder~table.attr.cam.time.v8.02724 : [] myNamespace.geomesa_SignalBuilder_attr_cam_time_v8_02724

SignalBuilder~table.attr.cam.time.v8.02725 : [] myNamespace.geomesa_SignalBuilder_attr_cam_time_v8_02725

SignalBuilder~table.attr.cam.time.v8.02726 : [] myNamespace.geomesa_SignalBuilder_attr_cam_time_v8_02726

SignalBuilder~table.attr.cam.time.v8.02727 : [] myNamespace.geomesa_SignalBuilder_attr_cam_time_v8_02727

SignalBuilder~table.z2.geo.v5.02712 : [] myNamespace.geomesa_SignalBuilder_z2_geo_v5_02712

SignalBuilder~table.z2.geo.v5.02716 : [] myNamespace.geomesa_SignalBuilder_z2_geo_v5_02716

SignalBuilder~table.z2.geo.v5.02723 : [] myNamespace.geomesa_SignalBuilder_z2_geo_v5_02723

SignalBuilder~table.z2.geo.v5.02724 : [] myNamespace.geomesa_SignalBuilder_z2_geo_v5_02724

SignalBuilder~table.z2.geo.v5.02725 : [] myNamespace.geomesa_SignalBuilder_z2_geo_v5_02725

SignalBuilder~table.z2.geo.v5.02726 : [] myNamespace.geomesa_SignalBuilder_z2_geo_v5_02726

SignalBuilder~table.z2.geo.v5.02727 : [] myNamespace.geomesa_SignalBuilder_z2_geo_v5_02727

SignalBuilder~table.z3.geo.time.v7.02712 : [] myNamespace.geomesa_SignalBuilder_z3_geo_time_v7_02712

SignalBuilder~table.z3.geo.time.v7.02716 : [] myNamespace.geomesa_SignalBuilder_z3_geo_time_v7_02716

SignalBuilder~table.z3.geo.time.v7.02723 : [] myNamespace.geomesa_SignalBuilder_z3_geo_time_v7_02723

SignalBuilder~table.z3.geo.time.v7.02724 : [] myNamespace.geomesa_SignalBuilder_z3_geo_time_v7_02724

SignalBuilder~table.z3.geo.time.v7.02725 : [] myNamespace.geomesa_SignalBuilder_z3_geo_time_v7_02725

SignalBuilder~table.z3.geo.time.v7.02726 : [] myNamespace.geomesa_SignalBuilder_z3_geo_time_v7_02726

SignalBuilder~table.z3.geo.time.v7.02727 : [] myNamespace.geomesa_SignalBuilder_z3_geo_time_v7_02727

пн, 11 апр. 2022 г. в 13:42, Rinchin Gomboev <gomboev.rinchin@xxxxxxxxx>:

Hello everyone. Please help.

Geomesa index tables in accumulo disappeared. Is there the way to recreate it?

Now when I try to make export request the util geomesa-accumulo and my app return the same output Table myNamespace.geomesa_SignalBuilder_attr_cam_time_v8_02726 does not exist

ERROR Could not execute export query. Please ensure that all arguments are correct

java.lang.RuntimeException: Could not execute export query. Please ensure that all arguments are correct

at org.locationtech.geomesa.tools.export.ExportCommand.export(ExportCommand.scala:212)

at org.locationtech.geomesa.tools.export.ExportCommand.export$(ExportCommand.scala:197)

at org.locationtech.geomesa.accumulo.tools.export.AccumuloExportCommand.export(AccumuloExportCommand.scala:24)

at org.locationtech.geomesa.tools.export.ExportCommand.export(ExportCommand.scala:123)

at org.locationtech.geomesa.tools.export.ExportCommand.$anonfun$execute$5(ExportCommand.scala:72)

at org.locationtech.geomesa.tools.package$DataStoreCommand.withDataStore(package.scala:69)

at org.locationtech.geomesa.tools.package$DataStoreCommand.withDataStore$(package.scala:67)

at org.locationtech.geomesa.accumulo.tools.export.AccumuloExportCommand.withDataStore(AccumuloExportCommand.scala:24)

at org.locationtech.geomesa.tools.export.ExportCommand.$anonfun$execute$4(ExportCommand.scala:72)

at org.locationtech.geomesa.utils.stats.MethodProfiling.profile(MethodProfiling.scala:26)

at org.locationtech.geomesa.utils.stats.MethodProfiling.profile$(MethodProfiling.scala:24)

at org.locationtech.geomesa.accumulo.tools.export.AccumuloExportCommand.profile(AccumuloExportCommand.scala:24)

at org.locationtech.geomesa.tools.export.ExportCommand.execute(ExportCommand.scala:72)

at org.locationtech.geomesa.tools.export.ExportCommand.execute$(ExportCommand.scala:59)

at org.locationtech.geomesa.accumulo.tools.export.AccumuloExportCommand.execute(AccumuloExportCommand.scala:24)

at org.locationtech.geomesa.tools.Runner$MainExecutor.execute(Runner.scala:203)

at org.locationtech.geomesa.tools.Runner.execute(Runner.scala:39)

at org.locationtech.geomesa.tools.Runner.main(Runner.scala:34)

at org.locationtech.geomesa.tools.Runner.main$(Runner.scala:34)

at org.locationtech.geomesa.accumulo.tools.AccumuloRunner$.main(AccumuloRunner.scala:17)

at org.locationtech.geomesa.accumulo.tools.AccumuloRunner.main(AccumuloRunner.scala)

Caused by: org.apache.accumulo.core.client.TableNotFoundException: Table myNamespace.geomesa_SignalBuilder_attr_cam_time_v8_02726 does not exist

at org.apache.accumulo.core.clientImpl.Tables._getTableId(Tables.java:123)

at org.apache.accumulo.core.clientImpl.Tables.getTableId(Tables.java:89)

at org.apache.accumulo.core.clientImpl.ClientContext.getTableId(ClientContext.java:458)

at org.apache.accumulo.core.clientImpl.ClientContext.createBatchScanner(ClientContext.java:470)

at org.apache.accumulo.core.clientImpl.ConnectorImpl.createBatchScanner(ConnectorImpl.java:87)

at org.locationtech.geomesa.accumulo.data.AccumuloQueryPlan$BatchScanPlan.scanner(AccumuloQueryPlan.scala:153)

at org.locationtech.geomesa.accumulo.data.AccumuloQueryPlan$BatchScanPlan.$anonfun$scan$6(AccumuloQueryPlan.scala:136)

at org.locationtech.geomesa.utils.collection.CloseableIterator$FlatMapCloseableIterator.hasNext(CloseableIterator.scala:142)

at scala.collection.Iterator$$anon$10.hasNext(Iterator.scala:460)

at org.locationtech.geomesa.utils.collection.CloseableIterator$CloseableIteratorImpl.hasNext(CloseableIterator.scala:61)

at org.locationtech.geomesa.utils.collection.CloseableIterator$FlatMapCloseableIterator.hasNext(CloseableIterator.scala:139)

at org.locationtech.geomesa.utils.iterators.ExceptionalIterator.hasNext(ExceptionalIterator.scala:27)

at scala.collection.Iterator$$anon$10.hasNext(Iterator.scala:460)

at org.locationtech.geomesa.utils.collection.CloseableIterator$CloseableIteratorImpl.hasNext(CloseableIterator.scala:61)

at org.locationtech.geomesa.index.geotools.GeoMesaFeatureReader.hasNext(GeoMesaFeatureReader.scala:32)

at org.locationtech.geomesa.index.geotools.GeoMesaFeatureReader$GeoMesaFeatureReaderWithAudit.super$hasNext(GeoMesaFeatureReader.scala:79)

at org.locationtech.geomesa.index.geotools.GeoMesaFeatureReader$GeoMesaFeatureReaderWithAudit.$anonfun$hasNext$2(GeoMesaFeatureReader.scala:79)

at scala.runtime.java8.JFunction0$mcZ$sp.apply(JFunction0$mcZ$sp.java:23)

at org.locationtech.geomesa.utils.stats.MethodProfiling.profile(MethodProfiling.scala:19)

at org.locationtech.geomesa.utils.stats.MethodProfiling.profile$(MethodProfiling.scala:17)

at org.locationtech.geomesa.index.geotools.GeoMesaFeatureReader$GeoMesaFeatureReaderWithAudit.profile(GeoMesaFeatureReader.scala:66)

at org.locationtech.geomesa.index.geotools.GeoMesaFeatureReader$GeoMesaFeatureReaderWithAudit.hasNext(GeoMesaFeatureReader.scala:79)

at org.geotools.feature.FeatureReaderIterator.hasNext(FeatureReaderIterator.java:53)

at org.geotools.feature.collection.DelegateFeatureIterator.hasNext(DelegateFeatureIterator.java:47)

at org.locationtech.geomesa.utils.collection.CloseableIterator$CloseableFeatureIterator.hasNext(CloseableIterator.scala:81)

at scala.collection.Iterator.foreach(Iterator.scala:943)

at scala.collection.Iterator.foreach$(Iterator.scala:943)

at org.locationtech.geomesa.utils.collection.CloseableIterator$CloseableFeatureIterator.foreach(CloseableIterator.scala:79)

at org.locationtech.geomesa.tools.export.formats.DelimitedExporter.export(DelimitedExporter.scala:51)

at org.locationtech.geomesa.tools.export.ExportCommand$Exporter.export(ExportCommand.scala:417)

at org.locationtech.geomesa.tools.export.ExportCommand.$anonfun$export$19(ExportCommand.scala:204)

at org.locationtech.geomesa.utils.io.package$WithClose$.apply(package.scala:64)

at org.locationtech.geomesa.tools.export.ExportCommand.export(ExportCommand.scala:201)

... 20 more

Thenk you
--

Rinchin Gomboev

--

Rinchin Gomboev
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxx
To unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/geomesa-users

References:
- [geomesa-users] how to fix disappeared index table in geomesa accumulo
  - From: Rinchin Gomboev
- Re: [geomesa-users] how to fix disappeared index table in geomesa accumulo
  - From: Rinchin Gomboev

Prev by Date: Re: [geomesa-users] how to fix disappeared index table in geomesa accumulo
Next by Date: Re: [geomesa-users] Installing Geomesa Kafka and Geomesa HBase in same GeoServer
Previous by thread: Re: [geomesa-users] how to fix disappeared index table in geomesa accumulo
Next by thread: [geomesa-users] GeoMesa 3.4.0 released
Index(es):
- Date
- Thread

Breadcrumbs