Skip to content

GEOWAVE-546 & GEOWAVE-696 Fixes / Updates#759

Merged
rwgdrummer merged 3 commits intolocationtech:0.9.1from
datasedai:0.9.1-BIT
May 7, 2016
Merged

GEOWAVE-546 & GEOWAVE-696 Fixes / Updates#759
rwgdrummer merged 3 commits intolocationtech:0.9.1from
datasedai:0.9.1-BIT

Conversation

@datasedai
Copy link
Copy Markdown
Contributor

@datasedai datasedai commented May 5, 2016

For GEOWAVE #546: If a kafka properties file isn't selected, then it won't apply command line options to the kafka config properties. Changed it so that it will do it whether the config file is specified or not.

For GEOWAVE #696: Fixed IndexCallbackList to implement Flushable, which will then allow the IndexWriter.flush() method to flush properly. Also, modified IT tearDown code to work in reverse order. For Kafka IT, it was tearing down Accumulo (with zookeeper) before tearing down kafka, and the kafka client was in an infinite loop trying to re-connect to zookeeper at the end of the IT.

Also, modified the BasicKafkaIT to not wait randomly 60 seconds, but instead to wait until all the data has been ingested, and the consumer times out before continuing the integration test. This will allow different systems with different performance specs to run the IT reliably. Added it back to GeoWaveITSuite.

datasedai added 3 commits May 5, 2016 12:33
Suite
- Change Kafka Driver to return list of Futures for topics, users can then
  wait on these until the topic times out
- Change Kakfa Test Environment to Timeout the Consumer after it is done
  reading the IT data.  After 5 seconds, it will timeout, and the rest of
  the IT will execute.  Removed 60 second sleep.
final KafkaIngestRunData ingestRunData,
final List<String> queue )
throws Exception {
final ExecutorService executorService = Executors.newFixedThreadPool(queue.size());
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just realized something here.. Is this creating a thread pool of X size for every single topic? Like if I had 3 topics it would create 3 threadpools of 3 max threads each? I think it would probably only actually create 3 threads but there might be overhead from the extra pools...

@rwgdrummer rwgdrummer merged commit 0f725f5 into locationtech:0.9.1 May 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants