what's the recommened number of Kafkas and Zookeepers if I want to have around 5 organizations, with each organization to have 5-6 peer nodes?

#fabric-questions #fabric

Hi everyone, i am creating peer1/peer2/peer3, (anchor node is peer1), when i start the peer3, below error message, any idea? 2018-07-16 06:19:51.180 UTC [gossip/gossip] handleMessage -> WARN 1d0 Messa

#fabric #fabric-questions

The important piece of information is what is logged in the log entry above - the reason for this warning. If the reason is that the certificate couldn't be found - then it's OK as long as it doesn't

#fabric #fabric-questions

From a performance standpoint, Kafka and Zookeeper (ZK) are not going to be the bottleneck. So how many ZK nodes and Kafka brokers you deploy will depend on your resiliency model / requirements. Zooke

#fabric-questions #fabric

Hello Simon, Kafka cluster has nothing to do with number of Orgs and Peers. It depends on your Ordering service and Failover requirement. For e.g. 1. will all Org and Peer use same ordering service an

#fabric #fabric-questions

i have now peer1(anchor), peer2-5 (peer) i found now the peer2 does not have the error while peer3-5 do have error my environment: all dockers in the same server, exposing their port using different p

#fabric #fabric-questions

Hi Gari, what if i would like to allow 2 nodes failure, so the number of ZK is 2*2+1 =5 while the number of K is 3(replication factor) +2 = 5?

#fabric-questions #fabric

Dear All, We are in the process of going live with Hyperledger for a trading organization with multiple contracts with multiple clients, while working with limited banks, shippers and insurers. The ar

#fabric #fabric-questions

Hey Simon - On the ZK side, that's correct ... it's a 2f+1 model so f=2 means you need 5 ZK nodes. Kafka is a little trickier in terms of availability and data loss. For data loss, Kafka supports N-1

#fabric-questions #fabric

Hey Simon - On the ZK side, that's correct ... it's a 2f+1 model so f=2 means you need 5 ZK nodes. Kafka is a little trickier in terms of availability and data loss. For data loss, Kafka supports N-1

#fabric-questions #fabric

Integrating two fabric networks with different language for chaincode. Hey guys, I have a scenario which I need some light on: Let's say I have a fabric network with organisations and few different ch

#fabric

Hi Joe, Good example where the application only needs to check available "capacity" before submitting the transaction. For your given scenario, any other mvcc transaction conflicts should be minimal i

#fabric

Joe, So what you are saying is that you want the database to have some kind of built in mechanism that does not require that the chaincode do a read->update->write cycle, but instead decrements the ke

#fabric

"In this case, it would seem that the database must be able to handle that last calculation" This was my conclusion as well, and I can imagine it would create the potential for issues. For one thing,

#fabric

the issue resolved, my mistake, I forgot to add the entries in the DNS...

#fabric #fabric-questions

what's the usage for the affiliations in the Fabric CA ( and thus the cert info) do all the organization in the channel need to align with the same affiliations?

#fabric #fabric-questions

I am now testing on the v1.1 and the zookeeper version should be running 3.4.9 As check in the web, the zookeeper 3.4.9 does not support TLS, am I correct?

#fabric #fabric-questions

The default mode of channel operations (e.g. adding a new organization into the channel) is having MAJORITY to sign it. Any way to simply allow 1 Admin Org to sign it without asking other organization

#fabric #fabric-questions

if organization 1 instantiate a chaincode (let say mycc, version v0) what if organization 2 install a different chaincode using the same name (mycc, v0), the peer will check and reject? Can the peer g

#fabric #fabric-questions

correct. - J

#fabric #fabric-questions