I found the issue. Drill was fine, but I had one of the new nodes which had IP tables blocking some ports. Good lesson learned here for me.
Thanks, Scott On Wed, Aug 31, 2016 at 3:55 PM, Jinfeng Ni <[email protected]> wrote: > Can you please check the query profiles for both cases, and see if the > query plans are different? With more nodes, it's possible that the > same query might use different plan. > > Is your query like "select count(*) from bigTable"? What is the > storage plugin/format for the bigTable? > > > On Wed, Aug 31, 2016 at 8:28 AM, scott <[email protected]> wrote: > > Hello, > > I'm having some performance issues testing Drill on a large MapR cluster. > > I've been building a cluster of 100 nodes for the past few weeks. When > the > > cluster had only 40 nodes, I ran a benchmark test where Drill performed > > very well, returning in 80 seconds from counting a large table. After > > adding the additional 60 nodes, the same benchmark test is not finishing. > > It times out after approx. 5 minutes due to configured timeout value of > > 300000. My understanding of Drill is that performance should improve when > > you increase the cluster size. Each drillbit is configured with 16G. Can > > someone tell me if there are some configuration settings that can improve > > this? Or, is there some point where Drill performance decreases when the > > size of the cluster is too large? > > > > Thanks, > > Scott >
