Looks like it will be in the next release of flume
Thanks, Hari On Thu, Dec 4, 2014 at 2:22 AM, Jean-Philippe Caruana <[email protected]> wrote: > ok, but you told me to submit a patch... > Maybe a dedicated section in the documentation about flume-env.sh would > prevent people from doing mistakes, like me ? > Le 04/12/2014 11:03, Ashish a écrit : >> Related JIRA that has already been fixed >> https://issues.apache.org/jira/browse/FLUME-2337 >> >> On Thu, Dec 4, 2014 at 3:18 PM, Jean-Philippe Caruana >> <[email protected]> wrote: >>> https://issues.apache.org/jira/browse/FLUME-2569 >>> >>> Le 04/12/2014 09:57, Hari Shreedharan a écrit : >>> >>> Reasons are mostly historical. Feel free to submit a patch to bump it up >>> >>> Thanks, Hari >>> >>> >>> On Thu, Dec 4, 2014 at 12:55 AM, Jean-Philippe Caruana >>> <[email protected]> >>> wrote: >>>> Yes, flume-env.sh starts the JVM with 20 Mo and GCS opens a 64 Mo buffer. >>>> >>>> Any idea/reason why flume starts with such a low heap space ? >>>> >>>> Le 04/12/2014 01:19, Hari Shreedharan a écrit : >>>> >>>> It looks like you are just running out of heap space. Try increasing the >>>> heap space by specifying a higher value in the flume-env.sh file. >>>> >>>> Thanks, >>>> Hari >>>> >>>> >>>> On Mon, Dec 1, 2014 at 9:02 AM, Jean-Philippe Caruana >>>> <[email protected]> >>>> wrote: >>>>> I also asked the question on SO : >>>>> https://stackoverflow.com/questions/27232966/what-causes-flume-with-gcs-sink-to-throw-a-outofmemoryexepction > -- > Jean-Philippe Caruana > http://www.barreverte.fr
