Skip to content

changelog.md

Latest commit

 

History

History
73 lines (70 loc) · 4.66 KB

changelog.md

File metadata and controls

73 lines (70 loc) · 4.66 KB
Raw

  • 1.5.20

    • Fix producer reconnect timer on OTP 24.

  • 1.5.19

    • Handle record_list_too_large error returned from Kafka. Similar to message_too_large error, the batch is split, then dropped if single call is still too large.

  • 1.5.18

    • Partition metadata handling.
      • Fixed an issue introduced in 1.5.15 where temporarily missing partitions in the metadata response could leave a wolff_producer process permanently disconnected. wolff_producer now always attempts to reconnect, even if a partition disappears and reappears.
      • Ensured that partition numbers in the metadata response are always sequential, even when Kafka returns malformed metadata.

  • 1.5.17

    • Avoid badfun error when release hot upgrade.

  • 1.5.16

    • Handle metadata fetch error. {error, Reason} tuple was not handled by wolff_producer (only expects {conn_down, Reason} tuple), causing the partition-leader re-discovery timer to be expired permanently.

  • 1.5.15

    • Upgrade kafka_protocol to 2.3.6.6
    • Handle topic recreation with fewer partitions. Previously, Wolff only handled topic alteration with more partitions, but not topic re-creation with fewer partitions. Now deleted partition producers will be gracefully shut down once new metadata is fetched, and the buffered messages will be dropped. NOTE: As before, topic deletion (unknown_topic_or_partition) does not cause all partition producers to shut down.
    • Improve logging for leader connection down reason. Previously, if the connection is closed immediately after connected, the producer process may not get the chance to monitor the pid to get its exit reason. Now wolff_client handles the 'EXIT' signal and keep it for future logging purpose.

  • 1.5.14

    • Split batch if it's too large for Kafka.

  • 1.5.13

    • Use long-lived metadata connection. This is to avoid having to excessively re-establish connection when there are many concurrent connectivity checks.

  • 1.5.12

    • Fix connection error reason translation, the error log is now more compact when e.g. connect timeout happens.

  • 1.5.11

    • Fixed a try catch pattern in gen_server call towards client process, this should prevent wolff_producers from crash if wolff_client is killed during initialization.

  • 1.5.10

    • Enhance: use off_heap spawn option in producer processes for better gc performance.

  • 1.5.9

    • Fix: when picking a producer PID, if it was dead, it could lead to an error being raised. #38

  • 1.5.8

    • Fix type specs for producers and producer config. #31

  • 1.5.7

    • Stop supervised producer if failed to start. Otherwise the caller may have to call the wolff:stop_and_delete_supervised_producers/3 after matching an error return. If they don't, then it may appear as a resource leak. #26
    • Ensure {{Topic, Partition}, Connection} record exists even if there are errors returned at partition level metadata. Fixed in PR #29. There were two issues before this fix:
      • wolff_client may crash when trying to find partition leader connection for a producer worker. When there is error code in partition metadata, the connection record is not added, causing a badmatch error in this expression {_, MaybePid} = lists:keyfind(Partition, 1, Partitions).
      • wolff_producers may crash when fewer partitions found in partition counter refresh. Although Kafka does not support topic down-scale, the assertion has been removed.

  • 1.5.6

    • New producer option 'drop_if_highmem' to limit the growth of replayq(in mem) size
    • Drop otp22 support
    • Bring in local control application

  • 1.5.5

    • Fix: fix badarg pid monitoring error log when trying to close a dead connection. (PR #20)
    • Enhance: expose wolff_client:check_connectivity/2 for connectivity check before starting a client. (PR #18)
    • Fix: better error logs (PR #16, PR #17)
      • No need to report stacktrace for timeout and connection refused errors.
      • Report host:port in connection failure reasons.
      • Fixed a bad logging arg which causes failure attempts to be logged as strings

  • 1.5.4

    • Fix: no delay before the first re-connect attempt after disconnected while idling.

  • 1.5.3

    • Enhancement: refine logging, reduce the number of retry logs, report error level log every 10 failures.

  • 1.5.2

    • Enhancement: On-the-fly upgrade of anonymous function in client gen_server state to avoid badfun during hot-beam upgrade
    • Started using github action for CI

  • 1.5.1

    • Fix: connection DOWN reason. Should not be a pid, otherwise a producer may not attempt to reconnect.