peer的配置文件 core.yaml 中文翻译

###############################################################################
#
#    日志部分
#
###############################################################################
logging:# 默认日志级别指定针对3个peer命令：'node', 'network' and 'chaincode'# 同样适用命令的子命令.# 以下字符串是有效的日志级别选项，不区分大小写#     CRITICAL | ERROR | WARNING | NOTICE | INFO | DEBUG# 这里指定的日志级别可以用各种方式覆盖，# 下面列出优先级从最高到最低:## 1. --logging-level=<level> 命令行选项覆盖所有其他选项## 2. 空字符串无效。使用环境变量 CORE_LOGGING_LEVEL## 3. 空字符串无效。使用环境变量 CORE_LOGGING_[NODE|NETWORK|CHAINCODE]## 4. 如果以上都没有设置，那以下设置会生效# 开发者: 可以到 fabric/docs/Setup/logging-control.md 看到更详细的选项peer:       warningnode:       warningnetwork:    warningversion:    warningprotoutils: warningerror:      warningmsp:        warninggossip:     warninggrpc:       warningledger:     warningpolicies:   warningcauthdsl:   warningformat: '%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc} -> %{level:.4s} %{id:03x}%{color:reset} %{message}'###############################################################################
#
#    Peer 部分
#
###############################################################################
peer:# 这个ID用于标识这个 Peer 实例.id: jdoe# 用于逻辑上分割网络# networkId: dev# networkId: testnetworkId: dev# peer监听地址listenAddress: 0.0.0.0:7051# 同组织下其它节点所看到的本节点的地址# 不是同组织可以使用 externalEndpointaddress: 0.0.0.0:7051# 是否应以编程方式确定其地址# 对于Docker容器很有用addressAutoDetect: false# Setting for runtime.GOMAXPROCS(n). If n < 1, it does not change the current settinggomaxprocs: -1# Gossip related configurationgossip:# Bootstrap set to initialize gossip withbootstrap: 127.0.0.1:7051# NOTE: orgLeader and useLeaderElection parameters are mutual exclusive# setting both to true would result in the termination of the peer, since this is undefined# state.# Defines whenever peer will initialize dynamic algorithm for# "leader" selection, where leader is the peer to establish# connection with ordering service and use delivery protocol# to pull ledger blocks from ordering serviceuseLeaderElection: true# Statically defines peer to be an organization "leader",# where this means that current peer will maintain connection# with ordering service and disseminate block across peers in# its own organizationorgLeader: false# ID of this instanceendpoint:# Maximum count of blocks we store in memorymaxBlockCountToStore: 100# Max time between consecutive message pushes(unit: millisecond)maxPropagationBurstLatency: 10ms# Max number of messages stored until it triggers a push to remote peersmaxPropagationBurstSize: 10# Number of times a message is pushed to remote peerspropagateIterations: 1# Number of peers selected to push messages topropagatePeerNum: 3# Determines frequency of pull phases(unit: second)# Must be greater than digestWaitTime + responseWaitTimepullInterval: 4s# Number of peers to pull frompullPeerNum: 3# Determines frequency of pulling state info messages from peers(unit: second)requestStateInfoInterval: 4s# Determines frequency of pushing state info messages to peers(unit: second)publishStateInfoInterval: 4s# Maximum time a stateInfo message is kept until expiredstateInfoRetentionInterval:# Time from startup certificates are included in Alive messages(unit: second)publishCertPeriod: 10s# Should we skip verifying block messages or notskipBlockVerification: false# Dial timeout(unit: second)dialTimeout: 3s# Connection timeout(unit: second)connTimeout: 2s# Buffer size of received messagesrecvBuffSize: 20# Buffer size of sending messagessendBuffSize: 20# Time to wait before pull engine processes incoming digests (unit: second)# Should be slightly smaller than requestWaitTimedigestWaitTime: 1s# Time to wait before pull engine removes incoming nonce (unit: milliseconds)# Should be slightly bigger than digestWaitTimerequestWaitTime: 1500ms# Time to wait before pull engine ends pull (unit: second)responseWaitTime: 2s# Alive check interval(unit: second)aliveTimeInterval: 5s# Alive expiration timeout(unit: second)aliveExpirationTimeout: 25s# Reconnect interval(unit: second)reconnectInterval: 25s# This is an endpoint that is published to peers outside of the organization.# If this isn't set, the peer will not be known to other organizations.externalEndpoint:# Leader election service configurationelection:# Longest time peer wait for stable membership during leader election startup (unit: second)startupGracePeriod: 15s# Interval gossip membership sampled to check its stability (unit: second)membershipSampleInterval: 1s# Time pass since last declaration message before peer decide to go to election (unit: second)leaderAliveThreshold: 10s# Time between peer sends propose message and declare itself as a leader (sends declaration message) (unit: second)leaderElectionDuration: 5s# Sync related configurationsync:blocks:# Channel size for readonly SyncBlocks messages channel for receiving# blocks from oppositie Peer Endpoints.# NOTE: currently messages are not stored and forwarded, but rather# lost if the channel write blocks.channelSize: 10state:snapshot:# Channel size for readonly syncStateSnapshot messages channel# for receiving state deltas for snapshot from oppositie Peer Endpoints.# NOTE: when the channel is exhausted, the writes block for up to the# writeTimeout specified belowchannelSize: 50# Write timeout for the syncStateSnapshot messages# When the channel above is exhausted, messages block before being# discarded for this amount of timewriteTimeout: 60sdeltas:# Channel size for readonly syncStateDeltas messages channel for# receiving state deltas for a syncBlockRange from oppositie# Peer Endpoints.# NOTE: currently messages are not stored and forwarded,# but rather lost if the channel write blocks.channelSize: 20# Validator defines whether this peer is a validating peer or not, and if# it is enabled, what consensus plugin to loadevents:# The address that the Event service will be enabled on the validatoraddress: 0.0.0.0:7053# total number of events that could be buffered without blocking the# validator sendsbuffersize: 100# milliseconds timeout for producer to send an event.# if < 0, if buffer full, unblocks immediately and not send# if 0, if buffer full, will block and guarantee the event will be sent out# if > 0, if buffer full, blocks till timeouttimeout: 10# TLS Settings for p2p communicationstls:enabled: truecert:file: tls/server.crtkey:file: tls/server.keyrootcert:file: tls/ca.crt# The server name use to verify the hostname returned by TLS handshakeserverhostoverride:# Path on the file system where peer will store data (eg ledger)fileSystemPath: /var/hyperledger/fabric/peer# BCCSP (Blockchain crypto provider): Select which crypto implementation or# library to useBCCSP:Default: SWSW:# TODO: The default Hash and Security level needs refactoring to be# fully configurable. Changing these defaults requires coordination# SHA2 is hardcoded in several places, not only BCCSPHash: SHA2Security: 256# Location of Key StoreFileKeyStore:# If "", defaults to 'mspConfigPath'/keystore# TODO: Ensure this is read with fabric/core/config.GetPath() once readyKeyStore:# Path on the file system where peer will find MSP local configurationsmspConfigPath: msp# Identifier of the local MSP# ----!!!!IMPORTANT!!!-!!!IMPORTANT!!!-!!!IMPORTANT!!!!----# Deployers need to change the value of the localMspId string.# In particular, the name of the local MSP ID of a peer needs# to match the name of one of the MSPs in each of the channel# that this peer is a member of. Otherwise this peer's messages# will not be identified as valid by other nodes.localMspId: Org1MSP# Used with Go profiling tools only in none production environment. In# production, it should be disabled (eg enabled: false)profile:enabled:     falselistenAddress: 0.0.0.0:6060###############################################################################
#
#    VM section
#
###############################################################################
vm:# Endpoint of the vm management system.  For docker can be one of the following in general# unix:///var/run/docker.sock# http://localhost:2375# https://localhost:2376endpoint: unix:///var/run/docker.sock# settings for docker vmsdocker:tls:enabled: falseca:file: docker/ca.crtcert:file: docker/tls.crtkey:file: docker/tls.key# Enables/disables the standard out/err from chaincode containers for debugging purposesattachStdout: false# Parameters of docker container creating. For docker can created by custom parameters# If you have your own ipam & dns-server for cluster you can use them to create container efficient.# NetworkMode Sets the networking mode for the container. Supported standard values are: `host`(default),`bridge`,`ipvlan`,`none`# dns A list of DNS servers for the container to use.# note: not support customize for `Privileged` `Binds` `Links` `PortBindings`# not support set LogConfig using Environment Variables# LogConfig sets the logging driver (Type) and related options (Config) for Docker# you can refer https://docs.docker.com/engine/admin/logging/overview/ for more detail configruation.hostConfig:NetworkMode: hostDns:# - 192.168.0.1LogConfig:Type: json-fileConfig:max-size: "50m"max-file: "5"Memory: 2147483648###############################################################################
#
#    Chaincode section
#
###############################################################################
chaincode:# The id is used by the Chaincode stub to register the executing Chaincode# ID with the Peerand is generally supplied through ENV variables# the Path form of ID is provided when deploying the chaincode. The name is# used for all other requests. The name is really a hashcode# returned by the system in response to the deploy transaction. In# development mode where user runs the chaincode, the name can be any stringid:path:name:# Generic builder environment, suitable for most chaincode typesbuilder: $(DOCKER_NS)/fabric-ccenv:$(ARCH)-$(PROJECT_VERSION)golang:# golang will never need more than baseosruntime: $(BASE_DOCKER_NS)/fabric-baseos:$(ARCH)-$(BASE_VERSION)car:# car may need more facilities (JVM, etc) in the future as the catalog# of platforms are expanded.  For now, we can just use baseosruntime: $(BASE_DOCKER_NS)/fabric-baseos:$(ARCH)-$(BASE_VERSION)java:# This is an image based on java:openjdk-8 with addition compiler# tools added for java shim layer packaging.# This image is packed with shim layer libraries that are necessary# for Java chaincode runtime.Dockerfile:  |from $(DOCKER_NS)/fabric-javaenv:$(ARCH)-$(PROJECT_VERSION)# timeout in millisecs for starting up a container and waiting for Register# to come through. 1sec should be plenty for chaincode unit testsstartuptimeout: 300000# timeout in millisecs for invokes and initialize commands# this timeout is used by all chaincodes in all the channels including# system chaincodes. Default is 30000ms (30 seconds)executetimeout: 30000#timeout in millisecs for deploying chaincode from a remote repository.deploytimeout: 30000#mode - options are "dev", "net"#dev - in dev mode, user runs the chaincode after starting validator from# command line on local machine#net - in net mode validator will run chaincode in a docker containermode: net# keepalive in seconds. In situations where the communiction goes through a# proxy that does not support keep-alive, this parameter will maintain connection# between peer and chaincode.# A value <= 0 turns keepalive offkeepalive: 0# system chaincodes whitelist. To add system chaincode "myscc" to the# whitelist, add "myscc: enable" to the list below, and register in# chaincode/importsysccs.gosystem:cscc: enablelscc: enableescc: enablevscc: enableqscc: enable# logging section for the chaincode containerlogLevel: warninglogFormat: '%{color}%{time:2006-01-02 15:04:05.000 MST} [%{module}] %{shortfunc} -> %{level:.4s} %{id:03x}%{color:reset} %{message}'###############################################################################
#
#    Ledger section - ledger configuration encompases both the blockchain
#    and the state
#
###############################################################################
ledger:blockchain:state:# stateDatabase - options are "goleveldb", "CouchDB"# goleveldb - default state database stored in goleveldb.# CouchDB - store state database in CouchDBstateDatabase: CouchDBcouchDBConfig:# It is recommended to run CouchDB on the same server as the peer, and# not map the CouchDB container port to a server port in docker-compose.# Otherwise proper security must be provided on the connection between# CouchDB client (on the peer) and server.couchDBAddress: 127.0.0.1:5984# This username must have read and write authority on CouchDBusername:# The password is recommended to pass as an environment variable# during start up (eg LEDGER_COUCHDBCONFIG_PASSWORD).# If it is stored here, the file must be access control protected# to prevent unintended users from discovering the password.password:# Number of retries for CouchDB errorsmaxRetries: 3# Number of retries for CouchDB errors during peer startupmaxRetriesOnStartup: 10# CouchDB request timeout (unit: duration, e.g. 20s)requestTimeout: 35s# Limit on the number of records to return per queryqueryLimit: 10000# historyDatabase - options are true or false# Indicates if the history of key updates should be stored in goleveldbhistoryDatabase: true# Limit on the number of records to return per queryqueryLimit: 10000