README.adoc

RELP Flooder library rlp_10

Standalone version of rlp_09

Features

• Simple to use

• Scales to as many threads as wanted

• Supports infinite flooding and sending specific amount of events

Limitations

• Minimal failure tolerance, mostly meant for testing

• Limited usability outside specific testing situations

• Supports only one record per RELP batch

• No TLS support yet

How to compile

mvn clean package

How to run

java -jar rlp_10.jar

Configurations

System property	Default value	Usage
hostname	localhost	Sets hostname for the record
appname	rlp_10	Sets used appname for the record
target	127.0.0.1	RELP target server
port	1601	RELP target port
threads	4	RELP Flooder thread count
useTls	false	Is TLS used for connections (Note: Not implemented)
payloadSize	10	Record message extra padding
reportInterval	10	How often report should be printed
maxRecordsSent	-1	How many records should be sent (-1 for infinity). By default, this is per-thread but with usePerThreadIterator=false it is the total amount.
usePerThreadIterator	true	Should each thread act as an independent iterator (will send maxRecordsSent * threads amount of records)

Contributing

You can involve yourself with our project by opening an issue or submitting a pull request.

Contribution requirements:

1. All changes must be accompanied by a new or changed test. If you think testing is not required in your pull request, include a sufficient explanation as why you think so.

2. Security checks must pass

3. Pull requests must align with the principles and values of extreme programming.

4. Pull requests must follow the principles of Object Thinking and Elegant Objects (EO).

Read more in our Contributing Guideline.

Contributor License Agreement

Contributors must sign Teragrep Contributor License Agreement before a pull request is accepted to organization’s repositories.

You need to submit the CLA only once. After submitting the CLA you can contribute to all Teragrep’s repositories.