I'd like to know the best to identify the metrics which have data with the specific key values.For example "show me the metrics that have data with a tagv of zrjrc767mug1h0cv5jjntfsf3mj7u32h"
High level works. Is there a stable commit I should try?
High level works. Is there a stable commit I should try?
I disabled tracking, and the problem still seems to be there.
I also noticed that trying to create multiple metrics doesn't work:
Looking at the code, UidManager.assign() doesn't call UniqueId.setTSDB(), so tsdb.getConfig() is probably throwing the NPE.
I also tried to run metasync, and got this:
tsdb uid metasync
2013-04-30 22:56:07,847 ERROR [Thread-17] UidManager: [16]Scanner Exception
java.lang.RuntimeException: [16] Should never be here
at net.opentsdb.tools.UidManager$MetaSync.run(UidManager.java:1022) ~[tsdb-2.0.0.jar:85a1dfe]
org.hbase.async.UnknownRowLockException: org.apache.hadoop.hbase.UnknownRowLockException: Invalid row lock
at org.apache.hadoop.hbase.regionserver.HRegionServer.getLockFromId(HRegionServer.java:2664)
at org.apache.hadoop.hbase.regionserver.HRegionServer.get(HRegionServer.java:2021)
at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:364)
at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1400)
Caused by RPC: GetRequest(table="tsdb-uid", key="\x00\x001", family="name", qualifiers=["metric_meta"], attempt=1, region=RegionInfo(table="tsdb-uid", region_name="tsdb-uid,,1367359058752.536783ba39c4b4bd6c8aadb9a3a3c9f2.", stop_key=""))
at org.hbase.async.UnknownRowLockException.make(UnknownRowLockException.java:56) ~[asynchbase-1.4.1.jar:8c94a38]
at org.hbase.async.UnknownRowLockException.make(UnknownRowLockException.java:32) ~[asynchbase-1.4.1.jar:8c94a38]
...
All this is from a completely new database.
Is this specific to the 2.0 branch? Can it be used in the last version 1 release? If 2.0, can I run a separated 2.0 tsd to make use of this patch and keep all of my prod on 1.0?
Sorry for all the questions. I've been away spinning up a 16K samples per seconds ingest on our openTSDB system.
I ran with the fix, and it's working without a hitch.
Did you get a chance to finish up the search functionality? I went through the api/uid docs and couldn't figure out how to effectively use the endpoints.