[APEXMALHAR-2169] KafkaInputoperator: Remove the stuff related to Partition Based on throughput.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.5.0
• Assignee: Chaitanya Chebolu
• Reporter: Chaitanya Chebolu
• Created: 27/Jul/16 08:40
• Updated: 04/Sep/16 01:40
• Resolved: 23/Aug/16 23:59

Description

Dynamic Partition is not working in case of ONE_TO_MANY partition strategy.
Affected Operator: AbstractKafkaInputOperator (0.8 version)

Steps to reproduce:
(1) Created a topic with 3 partitions
(2) Created an application as KAFKA -> Console with below configuration:
strategy : one_to_many
initialPartitionCount: 2
(3) Launched the above application.
(4) After some time, re-partition the topic to 5

Observations:
(1) Operator re-partitioning is not happened.
(2) Operator is not emitting the messages.
(3) Following warning messages in log:
INFO com.datatorrent.contrib.kafka.AbstractKafkaInputOperator: [ONE_TO_MANY]: Repartition the operator(s) under 9223372036854775807 msgs/s and 9223372036854775807 bytes/s hard limit
WARN com.datatorrent.stram.plan.physical.PhysicalPlan: Empty partition list after repartition: OperatorMeta{name=Input, operator=com.datatorrent.contrib.kafka.KafkaSinglePortByteArrayInputOperator@1b822fcc, attributes={Attribute

{defaultValue=1024, name=com.datatorrent.api.Context.OperatorContext.MEMORY_MB, codec=com.datatorrent.api.StringCodec$Integer2String@4682eba5}

=1024}}

Issue Links

• links to: GitHub Pull Request #351