The Amazon Kinesis Producer Library (KPL) performs many tasks common to creating efficient and reliable producers for Amazon Kinesis. By using the KPL, customers do not need to develop the same logic every time they create a new application for data ingestion.
For detailed information and installation instructions, see the article Developing Producer Applications for Amazon Kinesis Using the Amazon Kinesis Producer Library in the Amazon Kinesis Developer Guide.
Starting on February 9, 2018 Amazon Kinesis Data Streams will begin transitioning to certificates issued by Amazon Trust Services (ATS). To continue using the Kinesis Producer Library (KPL) you must upgrade the KPL to version 0.12.6 or later.
If you have further questions please open a GitHub Issue, or create a case with the AWS Support Center.
This is a restatement of the notice published in the Amazon Kinesis Data Streams Developer Guide
- Including windows binary for Apache 2.0 release.
- [PR #256] Update KPL to Apache 2.0
- Bump up the version to 0.12.11.
- Fixes Issue #231
- Support for additional AWS regions.
- Bug fix to avoid Heap Out of Memory Exception.
- Support for additional AWS regions.
- Update the CloudWatch upload logic to timeout retries at 10 Minutes instead of 30 Minutes and backoff between retries.
- Stream the native application to disk instead of loading into memory. Extracting the native component will now stream it to disk, instead of copying it into memory. This should reduce memory use of the KPL during startup.
- Extract certificates when using a custom binary. Certificates will now be extracted to the directory of the custom binary.
- Improve exception handling in the credential update threads.
Runtime exceptions are now caught, and ignored while updating the credentials. This should avoid the thread death
that could occur if the credentials supplier threw an exception. At this only
RuntimeExceptions are handled,Throwables will still cause the issue.
- Removed the spin lock protecting credentials access. Credential access is now handled by atomic swaps, and when necessary a standard explicit lock. This significantly reduces contention retrieving credentials when a large number of threads are being used.
- Ticket spin locks will now fall back to standard locking after a set number of spins. The ticket spin lock is now a hybrid spin lock. After a set number of spins the lock will switch to a conventional lock, and condition variable. This reduces CPU utilization when a large number of threads are accessing the spin lock.
- Ensure that all certificates are registered the
FileAgeManagerto prevent file sweepers from removing them - Upgrade aws-java-sdk-core to 1.11.245
- Removed unnecessary libidn, and correctly set libuuid to static linking. This issue only affected the Linux version.
- Disabled clock_gettime support in Curl for macOS.
This fixes an issue where the KPL was unable to run on macOS versions older than 10.12. - Updated requirements for the using the KPL on Linux.
The KPL on Linux now requires glibc 2.9 or later.
- Added Windows support
The 0.12.x version now supports Windows.
The Windows version is currently mastered on the branchwindows, which will be merged at a later date.
The build instructions for Windows are currently out of date, and will be updated at a later date.__ - Removed the libc wrapper
The libc wrapper lowered the required version of glibc. The KPL is now built with an older version of libc, which removes the need for the wrapper. - Set the minimum required version of macOS to 10.9.
The KPL is now built against macOS 10.9.
- Allow exceptions to bubble to the thread exception handler for Daemon threads.
Exceptions that occur on daemon threads will now be allowed to propagate to the thread exception handler. This doesn't provide any additional monitoring or handling of thread death. - Updated
amazon-kinesis-producer-sampleto use the correct properties in its configuration file. - Updated documentation of
AggregationMaxSizeto match actual Kinesis limits. - Added support for setting
ThreadingModel, andThreadPoolSizeusing a properties file. - Extracted
IKinesisProducerfromKinesisProducerto allow for easier testing.
- Revert to an older version of glibc.
- Update bootstrap.sh to include new compiler options for the newer version of GCC.
- Upgraded dependency on aws-java-sdk-core to 1.11.128, and removed version range.
- Use an explicit lock file to manage access to the native KPL binaries.
- Log reader threads should be shut down when the native process exits.
- Add support for using a thread pool, instead of a thread per request. The thread pool model guarantees a fixed number of threads, but have issue catching up if the KPL is overloaded.
- Add log messages, and statistics about sending data to Kinesis.
-
Added flush statistics that record the count of events that trigger flushes of data destined for Kinesis
-
Added a log message that indicates the average time it takes for a PutRecords request to be completed.
This time is recorded from the when the request is enqueued to when it is completed.
-
Log a warning if the average request time rises above five times the configured flush interval.
If you see this warning normally it indicates that the KPL is having issues keeping up. The most likely cause is to many requests being generated, and you should investigate the flush triggers to determine why flushes are being triggered.
-
- The Java process will periodically reset the last modified times for native components. This will help to ensure that these files aren't deleted by automated cleanup scripts.
- Fixes Issue #81
- The native process will no longer report SIGPIPE signals as an error with a stack trace.
- Allow the use of SIGUSR1 to trigger a stack trace. This stack trace will only report for the thread that happened to receive the signal.
-
The native process will no longer attempt to use the default system CA bundle
- The KPL should now run on versions of Linux that don't place the default CA bundle in /etc/pki
- This fixes issue #66
-
Added automatic BJS endpoint selection
- The KPL will now select the BJS endpoint when configured for BJS.
- This fixes issue #36
-
Maven Artifact Signing Change
- Artifacts are now signed by the identity
Amazon Kinesis Tools <amazon-kinesis-tools@amazon.com>
- Artifacts are now signed by the identity
-
Windows Support is not Available for this Version.
This version of the Kinesis Producer Library doesn't currently support windows. Windows support will be added back at a later date.
- Log output from the kinesis_producer is now captured, and re-emitted by the LogInputStreamReader
- The daemon is now more aggressive about restarting the native kinesis_producer process.
- Updated AWS SDK dependency.
- The native process now uses version 1.0.5 of the AWS C++ SDK.
- The native process doesn't currently support any of the AWS C++ SDK credentials providers. Support for these providers will be added a later date.
- The native process now attempts to produce stack traces for various fatal signals.
Misc bug fixes and improvements.
Important: Becuase the slf4j-simple dependency has been made optional, you will now need to have a logging implementation in your dependencies before the Java logs will show up. For details about slf4j, see the manual. For a quick walkthrough on how to get basic logging, see this page.
- The default value of the maxConnections setting has been increased from 4 to 24.
- slf4j-simple dependency is now optional.
aws-java-sdk-coreversion increased to1.10.34. Please ensure your AWS SDK components all have the same major version.- Record completion callbacks are now executed in a threadpool rather than on the IPC thread.
- Fixed bug that produced invalidly signed requests on the latest version of OSX.
Bug fixes and improved temp file management in Java wrapper.
- The wrapper no longer creates unique a copy of the native binary on disk per instance of KinesisProducer. Multiple instances can now share the same file. Clobbering between versions is prevented by adding the hash of the contents to the file name.
- Idle CPU usage has been reduced (Issue 15)
- The native process should now terminate when the wrapper process is killed (Issues 14, 16)
Significant platform compatibility improvements and easier credentials configuration in the Java wrapper.
- The KPL now works on Windows (Server 2008 and later)
- The lower bound on the
RecordMaxBufferedTimeconfig has been removed. You can now set it to 0, although this is discouraged
- The java packages have been renamed to be consistent with the package names of the KCL (it's now com.amazonaws.services.kinesis.producer).
- The
Configurationclass has been renamedKinesisProducerConfiguration. KinesisProducerConfigurationnow accepts the AWS Java SDK'sAWSCredentialsProviderinstances for configuring credentials.- In addition, a different set of credentials can now be provided for uploading metrics.
- Glibc version requirement has been reduced to 2.5 (from 2.17).
- The binary is now mostly statically linked, such that configuring
(DY)LD_LIBRARY_PATHshould no longer be necessary. - No longer uses
std::shared_timed_mutex, so updating libc++ on OS X is no longer necessary - Removed dependencies on glog, libunwind and gperftools.
- First release
The KPL is written in C++ and runs as a child process to the main user process. Precompiled native binaries are bundled with the Java release and are managed by the Java wrapper.
The Java package should run without the need to install any additional native libraries on the following operating systems:
- Linux distributions with glibc 2.9 or later
- Apple OS X 10.9 and later
- Windows Server 2008 and later
Note the release is 64-bit only.
A sample java project is available in java/amazon-kinesis-sample.
Rather than compiling from source, Java developers are encouraged to use the KPL release in Maven, which includes pre-compiled native binaries for Linux, macOS.
Compilation of the native KPL components is currently migrating to CMake. Updating of the build instructions is currently being tracked in Issue #67.
There are two options. You can either pack the binaries into the jar like we did for the official release, or you can deploy the native binaries separately and point the java code at it.
You will need JDK 1.7+, Apache Maven and Python 2.7 installed.
If you're on Windows, do the following in the git bash shell we used for building. You will need to add java and python to the PATH, as well as set JAVA_HOME for maven to work.
Run python pack.py
Then
pushd java/amazon-kinesis-producer
mvn clean package source:jar javadoc:jar install
popd
This installs the jar into your local maven repo. The jar itself is available in java/amazon-kinesis-producer/targets/
The java wrapper contains logic that will extract and run the binaries during initialization.
The KinesisProducerConfiguration class provides an option setNativeExecutable(String val). You can use this to provide a path to the kinesis_producer[.exe] executable you have built. You have to use backslashes to delimit paths on Windows if giving a string literal.