fabric-kafka | Kafka Docker | Continuous Deployment library
kandi X-RAY | fabric-kafka Summary
kandi X-RAY | fabric-kafka Summary
Kafka Docker
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- constructQueryResponseFromIterator returns a JSON representation of the query results .
- getQueryResultForQueryStringWithPagination executes a query string with the given pageSize and pagination metadata .
- getQueryResultForQueryString returns the result for a query
- queryMarblesByOwner retrieves a list of marbles for a given owner
- get returns the value of the state
- addPaginationMetadataToQueryResults adds pagination metadata to buffer
- set stores a state
- Starts a new contract
fabric-kafka Key Features
fabric-kafka Examples and Code Snippets
Community Discussions
Trending Discussions on fabric-kafka
QUESTION
I'm trying to install Hyperledger Fabric binaries, but I found some errors stating that
"Error response from daemon: No such image" for Fabric-ca and third party binaries.
How can I install the full package?
command and error:
...ANSWER
Answered 2019-Jan-29 at 16:09I must have also been looking at some earlier documentation and hit the same problem. The solution in the comment above is correct, but the syntax is malformed. I re-ran with version 1.4.0 and it succeeded:
QUESTION
I was trying to make fabric network with 3 orgs(each has 3 peers) and 2 orderer nodes working with kafka&zookeeper but when I up orderer and check log there are errors like "Failed to initialize local MSP: Setup error: nil conf reference" after make localMSP.
...ANSWER
Answered 2019-Oct-10 at 08:28I have seen very similar errors in my Orderer and Peers logs and did a lot of checking of Volume mapping but the solution for me was to delete Fabric 1.4.2 docker images and replace them with 1.4.3. (Making sure that the 1.4.3 images also have the tag "latest".
The reason for the error is a new 1.4.3 feature regarding the Admin identity of a peer - it is explained here and here in other Stack Overflow posts.
QUESTION
ANSWER
Answered 2018-Jul-22 at 00:26We had to increase the timeout on the create channel command to 10 seconds for the kafka configuration.
For example: peer channel create -o orderer0:7050 -t 10s -c $CHANNEL_NAME ...
QUESTION
I'm trying to setup a network of 2 organizations each having two peers. A 3rd organisation having 2 orderer nodes with kakfa-zookeeper ensemble with 4 kafka and 3 zookeeper nodes.
Below is the relevant part of my crypto-config.yaml file:
...ANSWER
Answered 2019-Apr-02 at 07:33I finally able to resolve this issue. There was nothing wrong with these YAML configurations. The issue was with the docker configurations that It was lacking in resources and the strange thing is that I didn't get any resources related error in any container logs file. So, I just increased CPUs and Memory settings in the docker advanced configurations like below:
And after these configurational changes, my network started successfully and working properly.
Thanks to my colleague @Rafiq who help me in sorting out this issue.
QUESTION
I am trying to configure hyperledger fabric network. I run three zookeepers, three kafkas, three orderers and a couchdb. They are docker containers and work well. All containers are in the same docker network called ibknet. After that, I run peer container but it has a problem to detect couchdb container while its starting. Here is my command to run peer container.
docker run -d --name main.stock.ibk.com --hostname main.stock.ibk.com \
-p 7051:7051 \
-p 7053:7053 \
-e CORE_LEDGER_STATE_STATEDATABASE=CouchDB \
-e CORE_LEDGER_STATE_COUCHDBCONFIG_COUCHDBADDRESS=couchdb0:5984 \
--network ibknet hyperledger/fabric-peer:x86_64-1.0.4
Here is the list of running docker containers before executing the command above.
...ANSWER
Answered 2017-Dec-04 at 09:54Try adding : "--dns-search ." to the docker run command. The resolver on your host system is likely configured to append / search a domain for unknown hosts. "--dns-search ." should force resolution only via the embedded Docker DNS
QUESTION
This question is similar to First network in hyperledger except that I am attempting to run the automated scripts as described here: http://hyperledger-fabric.readthedocs.io/en/latest/build_network.html rather than executing steps manually.
When I run the supplied scripts, I get the following output:
...ANSWER
Answered 2017-Aug-14 at 20:30Run configtxgen --version, is the output 1.0.0 or 1.0.1?
Version 1.0.0 doesn't include the mod_policy stuff required to make the 1.0.1 images work, you'll need to redownload the tools.
If the output is 1.0.1, can you please re-run through everything manually, except when you get to bringing the containers up:
CHANNEL_NAME=$CHANNEL_NAME TIMEOUT= docker-compose -f docker-compose-cli.yaml up -d
make sure to run it without the -d argument at the end, so the command is now:
CHANNEL_NAME=$CHANNEL_NAME TIMEOUT= docker-compose -f docker-compose-cli.yaml up
This will display the logs in the terminal. Now open a new terminal tab and set your env variables again (i.e. CHANNEL_NAME and FABRIC_CFG_PATH) and continue the manual setup. When you run the channel creation command:
peer channel create -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls $CORE_PEER_TLS_ENABLED --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
Look at the last few lines of the log on the other tab and post them here.
QUESTION
We're stuck configuring a fabric network based on 3 orgs with 1 peer each and 2 kafka-based orderers. For kafka ordering we use 4 kafka nodes with 3 zookeepers. It's deployed on some AWS ec2 instances as follows:
1: Org1
2: Org2
3: Org3
4: orderer0, orderer1, kafka0, kafka1, kafka2, kafka3, zookeeper0, zookeeper1, zookeeper2
The whole of the ordering nodes plus kafka cluster is located in the same machine for connectivity reasons (read somewhere they must be in the same machine to avoid these problems)
During our test, we try taking down the first orderer (orderer0) for redundancy testing with docker stop. We expected the network to continue working through orderer1, but instead it dies and stops working.
Looking at the peer's console, I can see some errors.
Could not connect to any of the endpoints: [orderer0.example.com:7050, orderer1.example.com:8050]
Find attached the content of the files related to the configuration of the system.
Orderer + kafka + zk
...ANSWER
Answered 2018-Oct-02 at 16:10I'm not sure but it could be because of different network layer. Since it's a different compose file , docker do create different network layer for each composer.
Also, I don't see network mentioned in the yaml files.
Please check list of network layer using "docker network list".
QUESTION
I try to run First network sample Building Your First Network from official docs. I need to run this sample with kafka orderer type. For this case I edit configtx.yaml file (changed OrdererType to kafka and added Brokers)
...ANSWER
Answered 2017-Dec-19 at 05:50I fixed problem. Added sleep 30 before running script.sh in cli container. File docker-compose-cli.yaml
QUESTION
I need some assistance with configuring my kafka brokers docker containers for hyperledger fabric. My setup will be a cluster of 4 brokers and I am having an issue when I introduce the second broker. All the brokers are currently sitting on a single machine and I need them to advertise their external address so that my orderers on different machines can discover them.
My compose file with 1 Zookeeper and 1 Broker:
...ANSWER
Answered 2018-May-11 at 03:35Within the container is where your listener variables are configured. 10092 is the port on your host, not the container.
Therefore, you want this
QUESTION
I played around with Hyperledger Fabric lately and I'm not able to find a good and exhaustive description of ALL environment variables one can set on the hyperledger fabric docker containers (fabric-orderer, fabric-peer, fabric-ca, fabric-tools, fabric-kafka, ...)
Is there such a documentation? I only find so little about the possible variables and what their different values would do and when one would choose which value; even on the official documentation.
Can anyone provide such a list with explanation? Or can we collect information to create such a list?
Ideally, I would like to have something like the following:
fabric-orderer ...ANSWER
Answered 2018-Mar-30 at 13:41This is a great question, and would indeed make a good addition to the docs. It is not currently explicitly documented, but I can explain at least how you can determine what the variables are.
We use viper for managing configuration. We ship a sample configuration with the distribution of the docker images and binaries. As you can see, there are three configuration yaml files: configtx.yaml, core.yaml and orderer.yaml. For each configuration parameter in the yaml file, you can derive an environment variable that can be used to override the value in the config file used at startup. The environment variable name is derived from the filename (e.g. CORE for core.yaml), and underscore-separated capitalization of the nested properties in the config, (e.g. CORE_LOGGING_LEVEL).
The sample apps provided contain docker-compose yaml configurations that leverage most of the properties you might consider leveraging for your own purposes.
Meanwhile, I have created a JIRA to track this and invite contributions to help us flesh out an addition to our documentation that provides a useful reference.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install fabric-kafka
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
