jokerCoCo commented on issue #1968: URL: https://github.com/apache/incubator-hugegraph/issues/1968#issuecomment-1255709301
> 现在的默认发布版本应该是多副本形式把，为什么会存在分步不均的情况，你可以多（编辑）一些配置信息和时间。 > > 第二个不同计算能力正在做的内部是核心核心，多个请求的api是自动被分割到多个台请求的节点的，比较大的一个请求和测试。 嗯嗯，好的。下面是我配置文件的相关信息，是1主2从的形式，后端采用rockdb做存储 rest-server.properties的配置 `rpc.server_host=host1 rpc.remote_url=host1,host2,host3 server.id=server-1 server.role=master` `rpc.server_host=host2 rpc.remote_url=host1,host2,host3 server.id=server-2 server.role=worker` `rpc.server_host=host3 rpc.remote_url=host1,host2,host3 server.id=server-3 server.role=worker` 上述配置也是我从其他问题中了解到的，host都是我服务器的ip地址 hugegraph.properties配置 对于raft参数配置我主要改了raft.mode、raft.safe_read、raft.endpoint、raft.group_peers这几个参数，其他都是默认配置 master配置 `# gremlin entrance to create graph # auth config: com.baidu.hugegraph.auth.HugeFactoryAuthProxy gremlin.graph=com.baidu.hugegraph.HugeFactory # cache config #schema.cache_capacity=100000 # vertex-cache default is 1000w, 10min expired vertex.cache_type=l2 #vertex.cache_capacity=10000000 #vertex.cache_expire=600 # edge-cache default is 100w, 10min expired edge.cache_type=l2 #edge.cache_capacity=1000000 #edge.cache_expire=600 # schema illegal name template #schema.illegal_name_regex=\s+|~.* #vertex.default_label=vertex backend=rocksdb serializer=binary store=hugegraph1 raft.mode=true raft.safe_read=true raft.use_snapshot=false raft.endpoint=192.168.1.16:8282 raft.group_peers=192.168.1.16:8282,192.168.1.17:8282,192.168.1.18:8282 raft.path=./raft-log raft.use_replicator_pipeline=true raft.election_timeout=10000 raft.snapshot_interval=3600 raft.backend_threads=48 raft.read_index_threads=8 raft.read_strategy=ReadOnlyLeaseBased raft.queue_size=16384 raft.queue_publish_timeout=60 raft.apply_batch=1 raft.rpc_threads=80 raft.rpc_connect_timeout=5000 raft.rpc_timeout=60000 search.text_analyzer=jieba search.text_analyzer_mode=INDEX # rocksdb backend config rocksdb.data_path=/path/to/disk1 rocksdb.wal_path=/path/to/disk1 # cassandra backend config cassandra.host=localhost cassandra.port=9042 cassandra.username= cassandra.password= #cassandra.connect_timeout=5 #cassandra.read_timeout=20 #cassandra.keyspace.strategy=SimpleStrategy #cassandra.keyspace.replication=3 # hbase backend config #hbase.hosts=localhost #hbase.port=2181 #hbase.znode_parent=/hbase #hbase.threads_max=64 # mysql backend config #jdbc.driver=com.mysql.jdbc.Driver #jdbc.url=jdbc:mysql://127.0.0.1:3306 #jdbc.username=root #jdbc.password= #jdbc.reconnect_max_times=3 #jdbc.reconnect_interval=3 #jdbc.sslmode=false # postgresql & cockroachdb backend config #jdbc.driver=org.postgresql.Driver #jdbc.url=jdbc:postgresql://localhost:5432/ #jdbc.username=postgres #jdbc.password= #jdbc.postgresql.connect_database=template1 # palo backend config #palo.host=127.0.0.1 #palo.poll_interval=10 #palo.temp_dir=./palo-data #palo.file_limit_size=32 ` worker1配置 ``` raft.mode=true raft.safe_read=true raft.use_snapshot=false raft.endpoint=192.168.1.17:8282 raft.group_peers=192.168.1.16:8282,192.168.1.17:8282,192.168.1.18:8282 raft.path=./raft-log raft.use_replicator_pipeline=true raft.election_timeout=10000 raft.snapshot_interval=3600 raft.backend_threads=48 raft.read_index_threads=8 raft.read_strategy=ReadOnlyLeaseBased raft.queue_size=16384 raft.queue_publish_timeout=60 raft.apply_batch=1 raft.rpc_threads=80 raft.rpc_connect_timeout=5000 raft.rpc_timeout=60000 ``` worker2配置 ``` raft.mode=true raft.safe_read=true raft.use_snapshot=false raft.endpoint=192.168.1.18:8282 raft.group_peers=192.168.1.16:8282,192.168.1.17:8282,192.168.1.18:8282 raft.path=./raft-log raft.use_replicator_pipeline=true raft.election_timeout=10000 raft.snapshot_interval=3600 raft.backend_threads=48 raft.read_index_threads=8 raft.read_strategy=ReadOnlyLeaseBased raft.queue_size=16384 raft.queue_publish_timeout=60 raft.apply_batch=1 raft.rpc_threads=80 raft.rpc_connect_timeout=5000 raft.rpc_timeout=60000 ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
