kop
kop copied to clipboard
streamnative
Kafka-on-Pulsar - A protocol handler that brings native Kafka protocol to Apache Pulsar
**Proxy design guiding principles** - The Proxy is stateless - The Proxy simulates a “big” single broker cluster - The Proxy is aware about Tenants/Namespaces/Topic Bundles and it can execute...
Proxy support for KoP. - #101 Create sub module in current code structure.
**Describe the bug** I am using Pulsar 2.8.0 and KOP 2.8.x (latest tag on 2.8 release line) After some time on the Pulsar broker I see KOP logging these lines...
**Describe the bug** The setup with the envoy proxy does not work, and I see these errors on the envoy proxy: `[2021-08-19 12:14:35.288][140117][debug][kafka] [source/extensions/filters/network/kafka/broker/filter.cc:112] could not process data from Kafka...
**Describe the bug** Deploy broker with kop in k8s, expose ports with nodeport. when `advertisedAddress` is not same with the first address in `advertisedListeners`, lookup can not find broker address...
**Describe the bug** `MetricsProviderTest#testMetricsProvider` is very flaky in CI environment. The key point is ```java Assert.assertTrue(sb.toString().contains("kop_server_REQUEST_LATENCY{success=\"true\",quantile=\"0.99\", " + "request=\"Produce\"}")); ``` I've commented it in #636 to make CI pass. **To...
12:22:09.801 [bookkeeper-ml-workers-OrderedExecutor-0-0] ERROR io.streamnative.pulsar.handlers.kop.format.PulsarEntryFormatter - Meet exception: {} java.lang.IllegalArgumentException: java.lang.IllegalArgumentException: Maximum offset delta exceeded, base offset: 475692710641008640, last offset: 503769839567896576 at sun.reflect.GeneratedConstructorAccessor103.newInstance(Unknown Source) ~[?:?] at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_211] at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_211]...
**Is your feature request related to a problem? Please describe.** #531 added the check for log end offset when fetching messages, but the check for log start offset is missed....
### Describe the Bug When producer send multi batches in one MemoryRecords, such as protocal [V0, V2] and [V8, +), it will packup multi batches in one entry and stored...
# Motivation KoP transaction log and recovery.
Metadata
Owner
Metadata
Kafka-on-Pulsar - A protocol handler that brings native Kafka protocol to Apache Pulsar