Shulou(Shulou.com)06/01 Report--

Community partner feedback encountered some problems in the practice article "using graph database Nebula Graph data import to quickly experience knowledge graph OwnThink". Nebula Graph will Debug the problems in this article.

Error message: panic: yaml: line 14: mapping values are not allowed in this contex

Error: panic: yaml: line 14: mapping values are not allowed in this contex when using nebula-importer

The reason for this error is that the first * *-path** field in the config.yaml file is not aligned and is changed by adding a space before the first-path field. This error has been corrected in the latest packaged oss package. The changed configuration file can go to GitHub (link: https://github.com/jievince/rdf-converter/blob/master/rdf-import.yaml) or copy the following information directly.

Version: v1rc1description: exampleclientSettings: concurrency: 10 # number of graph clients channelBufferSize: 128 space: test connection: user: user password: password address: 127.0.0.1:3699logPath:. / err/test.logfiles:-path:. / vertex.csv failDataPath:. / err/vertex.csv batchSize: 100 type: csv csv: withHeader: false withLabel: false schema: type: vertex vertex: tags: -name: entity props:-name: name type: string-path:. / edge.csv failDataPath:. / err/edge.csv batchSize: 100 type: csv csv: withHeader: false withLabel: false schema: type: edge edge: name: relation withRanking: false props:-name: name Type: string error message: writing tcp 127.0.0.1... Write: broken_pipe

In the process of using nebula-importer to guide data, report writing tcp 127.0.0.1. Write: broken_pipe error message. This error is caused by a bug of Nebula Graph. It has been fixed in this rc2 (pre-release) update package. Please go to GitHub (link: https://github.com/vesoft-inc/nebula/releases/tag/v1.0.0-rc2) to download.

High memory footprint

Due to the lack of memory on some low-configuration machines, the original default configuration is for models with more than 64 GB of memory. Changed the default number of partition, default wal file size, and wal buffer size. See pr at: https://github.com/vesoft-inc/nebula/pull/1330

Storage starts too slowly, report to Internal error, or report port occupancy

When a large amount of data is available, after storage suddenly failover, there are some problems such as slow data loading during startup, reporting to Internal error, or report port occupation, which has been fixed. See pr at: https://github.com/vesoft-inc/nebula/pull/1341

Other repair information fixes the problem of low probability crash when storage client obtains leader information. For pr, see: https://github.com/vesoft-inc/nebula/pull/1342 fixes the problem of drop space low probability crash while meta client is writing under high pressure, and pr can be found at: https://github.com/vesoft-inc/nebula/pull/1340

Finally, attach the NebulaGraph GitHub address: https://github.com/vesoft-inc/nebula, if you encounter any problems in the process of using NebulaGraph, GitHub is welcome to contact us or join the Wechat exchange group, please contact WeChat: NebulaGraphbot

It is recommended to use the graph database Nebula Graph data import to quickly experience the knowledge graph OwnThink

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.