Goran Cvijanovic
07/27/2022, 2:55 PMSandeep
08/16/2022, 11:36 AMKasper
08/16/2022, 10:47 PMKasper
08/22/2022, 11:56 AMMatch
returns 5M indices in about 5 minutes.Goran Cvijanovic
08/22/2022, 12:22 PMKasper
08/30/2022, 7:41 AMnebula-bench
. Graph is deployed via docker-compose running on a 64 vCPU machine with 256GB RAM. I add a tag index to Post and rebuild:
CREATE TAG INDEX IF NOT EXISTS post_index on Post()
REBUILD TAG INDEX post_index;
After that i use lookup
.
Querying for Posts (~60M instances), this query returns in around 5 minutes:
LOOKUP ON Post yield id(vertex) | yield count(*)
whereas
LOOKUP ON Post yield id(vertex)
stalls. I tested both using console as well as python client.
Am I missing something? How should I retrieve large number of results then? Use vertex scan? Some kind of pagination?Sandeep
08/30/2022, 11:08 PMMarija Zelić
09/13/2022, 7:44 AM2022/09/13 08:05:02 [INFO] statsmgr.go:89: Tick: Time(290.00s), Finished(71750768), Failed(0), Read Failed(0), Latency AVG(1887us), Batches Req AVG(2043us), Rows AVG(247416.41/s)
2022/09/13 08:05:07 [INFO] statsmgr.go:89: Tick: Time(295.00s), Finished(72978112), Failed(0), Read Failed(0), Latency AVG(1887us), Batches Req AVG(2043us), Rows AVG(247383.40/s)
...
at the same time, a Grafana metric nebula_storaged_num_add_vertices_rate_60{instanceName=~"$hosts"}
is reporting ~110k rows/s.
could someone help interpret this metric pls?
thank you!Marija Zelić
09/13/2022, 7:44 AMSandeep
09/21/2022, 11:20 AMSandeep
09/30/2022, 11:52 AMGoran Cvijanovic
09/30/2022, 12:49 PMSandeep
10/01/2022, 8:48 PMGoran Cvijanovic
10/02/2022, 6:48 AMSandeep
10/02/2022, 11:13 AMwey
10/02/2022, 1:06 PMSandeep
10/02/2022, 8:22 PMSandeep
10/02/2022, 8:27 PMSandeep
10/06/2022, 10:32 AMSandeep
10/10/2022, 8:33 AMSandeep
10/11/2022, 11:41 PMSandeep
10/17/2022, 10:02 AMGoran Cvijanovic
10/17/2022, 11:13 AMSandeep
10/17/2022, 3:45 PMSandeep
11/14/2022, 12:26 PMGoran Cvijanovic
11/14/2022, 1:40 PMGoran Cvijanovic
11/17/2022, 9:07 AMWhen inserting an edge that already exists, INSERT VERTEX *overrides* the edge.
Goran Cvijanovic
11/29/2022, 4:08 PM[ERROR (-1005)]: Storage Error: Not the leader of 103. Please retry later.
second request returns valid response.
Also some request don’t return any results for keys that were inserted earlier.
I’ve upgraded my cluster to 3.3.0 version from 3.2.1 one node at a time.
fyi:
one parameter for rocksdb I’ve changed
--rocksdb_compression_per_level=no:no:lz4:lz4:lz4hc:lz4hc:lz4hc
from default setting that was empty string
can that change have impact to not be able to query some of the data ?
I’ve actually changed another one, using query optimizer, previously it was disabled !
--enable_optimizer=true
Goran Cvijanovic
11/29/2022, 9:00 PMGoran Cvijanovic
11/30/2022, 8:12 AME20221129 23:24:55.530879 332829 StorageAccessExecutor.h:39] IndexScanExecutor failed, error E_RPC_FAILURE, part 90
E20221129 23:24:55.530885 332829 StorageAccessExecutor.h:39] IndexScanExecutor failed, error E_RPC_FAILURE, part 92
E20221129 23:24:55.530894 332829 StorageAccessExecutor.h:39] IndexScanExecutor failed, error E_RPC_FAILURE, part 95
E20221129 23:24:55.530901 332829 StorageAccessExecutor.h:39] IndexScanExecutor failed, error E_RPC_FAILURE, part 96
E20221129 23:24:55.530913 332829 StorageAccessExecutor.h:136] Storage Error: part: 124, error: E_RPC_FAILURE(-3).
E20221129 23:24:55.530952 332825 QueryInstance.cpp:137] Storage Error: part: 124, error: E_RPC_FAILURE(-3).
Goran Cvijanovic
11/30/2022, 8:12 AME20221129 23:24:55.530879 332829 StorageAccessExecutor.h:39] IndexScanExecutor failed, error E_RPC_FAILURE, part 90
E20221129 23:24:55.530885 332829 StorageAccessExecutor.h:39] IndexScanExecutor failed, error E_RPC_FAILURE, part 92
E20221129 23:24:55.530894 332829 StorageAccessExecutor.h:39] IndexScanExecutor failed, error E_RPC_FAILURE, part 95
E20221129 23:24:55.530901 332829 StorageAccessExecutor.h:39] IndexScanExecutor failed, error E_RPC_FAILURE, part 96
E20221129 23:24:55.530913 332829 StorageAccessExecutor.h:136] Storage Error: part: 124, error: E_RPC_FAILURE(-3).
E20221129 23:24:55.530952 332825 QueryInstance.cpp:137] Storage Error: part: 124, error: E_RPC_FAILURE(-3).