[ 
https://issues.apache.org/jira/browse/APEXMALHAR-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15439212#comment-15439212
 ] 

Yogi Devendra commented on APEXMALHAR-2206:
-------------------------------------------

This fix is mainly focused on checking if each lc.runAsync() has corresponding 
lc.shutDown().

Found following occurrences of runAsync():

com.datatorrent.api.LocalMode.Controller.runAsync()
com.datatorrent.contrib.rabbitmq.RabbitMQOutputOperatorTest.runTest(int)
com.datatorrent.contrib.hbase.HBasePOJOInputOperatorTest.test()
com.datatorrent.lib.db.jdbc.JdbcIOAppTest.testApplication()
com.datatorrent.lib.io.fs.FSInputModuleAppTest.testApplication()
org.apache.apex.malhar.lib.dedup.DeduperOrderingTest.testApplication()
com.datatorrent.contrib.mqtt.MqttOutputOperatorTest.testDag()
org.apache.apex.malhar.lib.dedup.DeduperPartitioningTest.testDeduperStreamCodec()
org.apache.apex.malhar.lib.fs.FSRecordReaderTest.testDelimitedRecords()
org.apache.apex.malhar.lib.fs.FSRecordReaderTest.testFixedWidthRecords()
com.datatorrent.contrib.mqtt.MqttInputOperatorTest.testInputOperator()
org.apache.apex.malhar.lib.join.POJOPartitionJoinOperatorTest.testJoinOpStreamCodec()
com.datatorrent.contrib.kafka.KafkaExactlyOnceOutputOperatorTest.testKafkaExactOnceOutputOperator()
com.datatorrent.contrib.kafka.KafkaInputOperatorTest.testKafkaInputOperator(int,
 int, KafkaConsumer, boolean, boolean)
com.datatorrent.contrib.kafka.KafkaOutputOperatorTest.testKafkaOutputOperator()
com.datatorrent.contrib.kinesis.KinesisInputOperatorTest.testKinesisInputOperator()
com.datatorrent.contrib.kinesis.KinesisOutputOperatorTest.testKinesisOutputOperator()
org.apache.apex.malhar.lib.fs.FSRecordReaderTest.testMissingRecordLength()
com.datatorrent.contrib.kafka.OffsetManagerTest.testPartitionableInputOperator(KafkaConsumer,
 int)
com.datatorrent.contrib.kafka.KafkaPartitionableInputOperatorTest.testPartitionableInputOperator(KafkaConsumer)
com.datatorrent.contrib.kinesis.KinesisPartitionableInputOperatorTest.testPartitionableInputOperator(KinesisConsumer)
com.datatorrent.contrib.kinesis.ShardManagerTest.testPartitionableInputOperator(KinesisConsumer)
com.datatorrent.contrib.kafka.KafkaOutputOperatorTest.testPOJOKafkaOutputOperator()
com.datatorrent.lib.io.fs.S3InputModuleAppTest.testS3Application()
com.datatorrent.contrib.kinesis.ShardManagerTest.testShardManager()
com.datatorrent.lib.io.fs.FileSplitterBaseTest.testSplitterInApp() 

Verified that all of them have corresponding lc.shutdown().



> Some Application tests taking too long
> --------------------------------------
>
>                 Key: APEXMALHAR-2206
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2206
>             Project: Apache Apex Malhar
>          Issue Type: Bug
>            Reporter: Bhupesh Chawda
>            Assignee: Yogi Devendra
>            Priority: Minor
>
> Some Application Tests seems to be running for a long time.
> Additionally the size of the target folder increases too much ~ 2GB



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to