In gossip there are send and receive buffers that are
allocated for each connection.
When the throughput of messages is too high and the send buffer
overflows, the connection to the peer is closed and the peer is removed from the membership.

From performance evaluations I did - I conclude that:
- Increasing the send buffer size would benefit to withstand
  intense bursts of messages, even when the receive buffer stays the same.
- Not closing the connection to the peer (and not removing it from the membership)
  that its corresponding send buffer overflowed helps the throughput by giving the
  runtime an opportunity to recover in spite of an intensive burst.

Change-Id: I7bc84092e366b75b6cbcaee1ea9d5320274dfc1c
Signed-off-by: yacovm <yacovm@il.ibm.com>

Authorization error contains bin data (package) which is useless
for error reporting and would get in the way of SDKs and other
tools's reporting. This CR removes the bin data. Further we don't
want to peek into the data on auth. failure and so will _not_
attempt to read the package to enhance the reported error.

. patch 2 fixed lscc unit test to look for right error string

Change-Id: Ic55eba8d890aa2489488fdbd54d4ccc3a8483fed
Signed-off-by: Srinivasan Muralidharan <muralisr@us.ibm.com>

There are still a couple of coming soon
and WIP docs which show up via search.
Some are no longer needed and some will
be addressed in the future.  For both cases
we should remove them for the release.

Change-Id: I8a890431c48200b16da4383b7781deb6ba49cdeb
Signed-off-by: Gari Singh <gari.r.singh@gmail.com>

While it is possibly implied/required that you
should install libtool from the prereqs section
and/or also clone the fabric, there is really
no need to add this overhead if you simply
want to build chaincode.  We can use the
nopkcs11 build tag to avoid libtool and
we can add go get for getting the shim package

Change-Id: I96936d11dfaa14e2a85d99506deddbcc8fed4c2a
Signed-off-by: Gari Singh <gari.r.singh@gmail.com>

peer exe follows a different metadata pattern than other exes
such as configtxgen, cryptogen etc. The fix sets GO_LDFLAGS
for each binary production so peer's GO_LDFLAGS can be different
from other binaries.

. made one scoped change for peer production per Gari's comment

Change-Id: I899580796aa20ff299f1a69bf1762dae3a196e84
Signed-off-by: Srinivasan Muralidharan <muralisr@us.ibm.com>

This CR updates the comments for the logging section of core.yaml
to accurately document the usage of the available environment variables.

Change-Id: Ib042b9af1deb925d8fa30b870b7c774906909564
Signed-off-by: Will Lahti <wtlahti@us.ibm.com>

If configtxgen cannot find a configtx.yaml file,
it panics.  While this in and of itself is ok,
it should not panic when simply trying to get the
version.

Two changes were made:

- move response to --version above all other flags
- added a defer / recover function to better handle
config not found and make things more clear

Change-Id: I512d1fed464c734db7178eb576440c45767f6994
Signed-off-by: Gari Singh <gari.r.singh@gmail.com>

Change-Id: I60405320de34c35b21467802db4c4f0fa93d16da
Signed-off-by: Christopher Ferris <chrisfer@us.ibm.com>

Comment messages in Makefile is not updated after merging
CR10413 (https://gerrit.hyperledger.org/r/#/c/10413/

).
The following commands don't work as comment suggests.
 - dist-clean
 - clean-all
In addition, configtxlator doesn't have instruction.

This patch set fixes the comments above.

Change-Id: I55ec8e1e57db255ede99b0151f30833f86a5c2c1
Signed-off-by: Yuki Kondo <yuki.kondo@hal.hitachi.com>

Fixed simple asset chaincode link
Changed link to local ref
[ci-skip]

Change-Id: I41f8dd01ff9619d670341013e6bb9f8a1e441de7
Signed-off-by: Mark Parzygnat <markparz@us.ibm.com>

FAB-5052:
In gossip when a peer obtains an AliveMessage from a peer it hasn't
received its certificate yet - it complains in the log in WARNING that
it has received a message from some peer it can't verify its identity.

This is actually a common scenario where a peer is restarted and its
in-meory certificate store is now empty, but the other peers contact
the peer and send it alive messages which he can't verify until it syncs
its certificates with them.

This startles users and I think we should reduce the logging severity
from WARN to DEBUG.

FAB-5051:
When a peer is in a partition or is dead for a long enough time,
gossip prints:
        Haven't heard from", <gibberish>, "for" <elapsed time>

The problem is that the id is a string of a hash and its
printed in gibberish.
It's not something humans can read,
and we need to cast the string back to []byte so it would be human readable.

Change-Id: I94bcad11623e53b5275ef8cecbdd3f9563fa1e77
Signed-off-by: yacovm <yacovm@il.ibm.com>

This patch set deletes unused code in common packages.
field msg in common/config/standardvalues_test.go is
intentionally unused

Change-Id: Ic37049262875e3405fd6f8553a4bbd00591cb286
Signed-off-by: Nao Nishijima <nao.nishijima@hal.hitachi.com>

This patch set deletes unused code in events packages.

Change-Id: I330831a56709b4fd0a672f37e7d8c5193b02e4b5
Signed-off-by: Nao Nishijima <nao.nishijima@hal.hitachi.com>

generateArtifacts.sh does not work at 2nd time. Due to generating
a private key every time, if we execute generateArtifacts.sh more
than once, the command to get the private key will return more
than one result. However, we do not expect this result.
This patch set adds checking code of the existence of crypto-config
dir at the beginning.

Change-Id: Ie9249556c1988e30463683f688e4e50dc75d7b15
Signed-off-by: Nao Nishijima <nao.nishijima@hal.hitachi.com>

Fixed missing link to Setting up CA doc

[ci-skip]

Change-Id: I24a8265427293915fe1c6fd3154cad517c5fc88c
Signed-off-by: Mark Parzygnat <markparz@us.ibm.com>

The current documentation does not make it clear what the behavior of
GetState is when the key does not exist.  This CR simply adds another
line to the documentation indicating that (nil, nil) will be returned so
that the chaincode developer does not have to guess or test this
behavior.

Change-Id: Ic610c3c488bd2b45482371231744c7a5579c7137
Signed-off-by: Jason Yellick <jyellick@us.ibm.com>

remove marbles.rst

Change-Id: I8b369de6baef5cbfa0860f27d4885fb230dbbe3a
Signed-off-by: Christopher Ferris <chrisfer@us.ibm.com>

Fix [FAB-5002] remove assignment of
"CORE_PEER_MSPCONFIGPATH" when set globals on
peer1. Because there is no need to make a
assignment again on "CORE_PEER_MSPCONFIGPATH".
No matter peer0 or peer1 set globals, they have
the same configuration.

Change-Id: Ibf0d5fd3b03f5d85293c2fa365bcfd528ee29913
Signed-off-by: Wang Wenfeng <kalot.wang@gmail.com>