sixtus commented on issue #8840: index_hadoop tasks fail on wrong file format 
when run inside indexer
URL: 
https://github.com/apache/incubator-druid/issues/8840#issuecomment-563153306
 
 
   I think I found something:
   
   the staging system started working as expected when I used a middleManager
   rather than an indexer.
   
   a) any idea where to look?
   b) can I pin a certain type of work to a specific middleManager (I only
   seen by data source)
   c) can I run a 2nd (independent) set over overlord/middlemanager to split
   index_kafka and index_hadoop? The thread model of the middleManager is
   killing performance for index_kafka
   
   Thanks!
   Hagen
   
   On Mon, Dec 9, 2019 at 9:09 AM Hagen Rother <hagen.rot...@liquidm.com>
   wrote:
   
   > I am using my own chef recipe (just for context: we are the first
   > production installation outside metamarket, we are using druid in
   > production since 2012), just for paranoia I used grep. Nothing "local".
   > Also the recipe used to work on 0.13.
   >
   > On the staging system, I switched to Minio (s3) and there I get a valid
   > segment in minio, but "local" as type in the payload.
   >
   > On Fri, Dec 6, 2019 at 3:40 AM Jonathan Wei <notificati...@github.com>
   > wrote:
   >
   >> It sounds like the config is specifying druid.storage.type=local
   >> somewhere, is it possible that there's a stray/stale entry for that
   >> somewhere in your runtime properties?
   >>
   >> When the Druid processes start up, they'll log their configuration
   >> properties; for the indexer process, do you see it using
   >> druid.storage.type=hdfs at that point?
   >>
   >> —
   >> You are receiving this because you were mentioned.
   >> Reply to this email directly, view it on GitHub
   >> 
<https://github.com/apache/incubator-druid/issues/8840?email_source=notifications&email_token=AAAWNUM5VKUJMK6QXAKTKO3QXG3QHA5CNFSM4JKFAJS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGC2TVI#issuecomment-562407893>,
   >> or unsubscribe
   >> 
<https://github.com/notifications/unsubscribe-auth/AAAWNUOJKPKIWRMY7KRMUMLQXG3QHANCNFSM4JKFAJSQ>
   >> .
   >>
   >
   >
   > --
   >
   > *Hagen Rother*
   > Lead Architect | LiquidM
   > ------------------------------
   > LiquidM Technology GmbH
   > Invalidenstraße 74 | 10557 Berlin | Germany
   > Phone: +49 176 15 00 38 77
   > Internet: www.liquidm.com | LinkedIn
   > <
   > 
http://www.linkedin.com/company/3488199?trk=tyah&trkInfo=tas%3AliquidM%2Cidx%3A1-2-2>
   >
   > ------------------------------
   > Managing Directors | Philipp Simon & Thomas Hille
   > Jurisdiction | Local Court Berlin-Charlottenburg HRB 152426 B
   >
   >
   
   -- 
   
   *Hagen Rother*
   Lead Architect | LiquidM
   ------------------------------
   LiquidM Technology GmbH
   Invalidenstraße 74 | 10557 Berlin | Germany
   Phone: +49 176 15 00 38 77
   Internet: www.liquidm.com | LinkedIn
   <
   
http://www.linkedin.com/company/3488199?trk=tyah&trkInfo=tas%3AliquidM%2Cidx%3A1-2-2>
   
   ------------------------------
   Managing Directors | Philipp Simon & Thomas Hille
   Jurisdiction | Local Court Berlin-Charlottenburg HRB 152426 B
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@druid.apache.org
For additional commands, e-mail: commits-h...@druid.apache.org

Reply via email to