Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
ELK elasticsearch indexing
See original GitHub issueThe current scripts whereby tweets are loaded with logstash result in a long list of indices (of the form logstash-<date>. Elasticsearch seems to get hung up when loaded with >100K tweets. It seems to me that we should be creating one index (could be wrong here).
This may be what’s crashing Elasticsearch, which is preventing realistic use of the ELK container. It is a high-priority request from Program on Extremism to have the ELK container work for their data set, which currently consists of roughly 900,000 tweets.
Issue Analytics
- State:
- Created 7 years ago
- Comments:14 (13 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Nope. ES indexes are stored outside of the container.
@Tanych @justinlittman Thanks for your thorough testing and work on this.