[jira] [Comment Edited] (PIG-5384) OOM while spilling large bag
[
https://issues.apache.org/jira/browse/PIG-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16796477#comment-16796477
]
Koji Noguchi edited comment on PIG-5384 at 3/19/19 9:44 PM:
Requirement of Pig keeping the entire -bag- list (mcontents) in memory until
the corresponding spill is done comes from the fact that Pig can continue to
run when spilling to a file fails. (It drops the spill file and keeps on using
the -bag- list (mcontents) in memory.)
Spilling can fail when disks are full but I'm guessing task would eventually
fail when that happens.
Spilling can also fail when a user passes a custom List instance that doesn't
support clear(). But for this case, this bag shouldn't be part of spillables
in the first place.
So wondering if we can provide an option to fail the task when spilling fails
and let Pig release each Tuple as soon as it writes to a spill file (before
closing).
was (Author: knoguchi):
Requirement of Pig keeping the entire bag in memory until the corresponding
spill is done comes from the fact that Pig can continue to run when spilling to
a file fails. (It drops the spill file and keeps on using the bag in memory.)
Spilling can fail when disks are full but I'm guessing task would eventually
fail when that happens.
Spilling can also fail when a user passes a custom List instance that doesn't
support clear(). But for this case, this bag shouldn't be part of spillables
in the first place.
So wondering if we can provide an option to fail the task when spilling fails
and let Pig release each Tuple as soon as it writes to a spill file (before
closing).
> OOM while spilling large bag
> -
>
> Key: PIG-5384
> URL: https://issues.apache.org/jira/browse/PIG-5384
> Project: Pig
> Issue Type: Improvement
>Reporter: Koji Noguchi
>Assignee: Koji Noguchi
>Priority: Major
>
> One of the common OOM issue in Pig is, Pig hitting OOM while trying to spill
> a large bag. Current solutions is to give higher heapsize or tweak
> {noformat}
> pig.spill.memory.usage.threshold.fraction
> pig.spill.collection.threshold.fraction
> pig.spill.unused.memory.threshold.size
> {noformat}
> and make sure spilling starts early enough. These params are still critical
> but wondering if any improvement can be made to increase the chances of
> avoiding OOM while spilling a single large bag.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PIG-5384) OOM while spilling large bag
[
https://issues.apache.org/jira/browse/PIG-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16796483#comment-16796483
]
Koji Noguchi commented on PIG-5384:
---
My first thought was to let the spill() create multiple spill files but this
require the change on the reader side. Given user may have their own custom
Bag, I don't think this would work.
Second was to let the spill() call {{out.flush()} for every N
records/bytes/seconds and release that part of the tuples. This may be a good
middle ground but requires the exception handling to re-read the flushed spill
file to recover the memory state.
> OOM while spilling large bag
> -
>
> Key: PIG-5384
> URL: https://issues.apache.org/jira/browse/PIG-5384
> Project: Pig
> Issue Type: Improvement
>Reporter: Koji Noguchi
>Assignee: Koji Noguchi
>Priority: Major
>
> One of the common OOM issue in Pig is, Pig hitting OOM while trying to spill
> a large bag. Current solutions is to give higher heapsize or tweak
> {noformat}
> pig.spill.memory.usage.threshold.fraction
> pig.spill.collection.threshold.fraction
> pig.spill.unused.memory.threshold.size
> {noformat}
> and make sure spilling starts early enough. These params are still critical
> but wondering if any improvement can be made to increase the chances of
> avoiding OOM while spilling a single large bag.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (PIG-5384) OOM while spilling large bag
[
https://issues.apache.org/jira/browse/PIG-5384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16796477#comment-16796477
]
Koji Noguchi commented on PIG-5384:
---
Requirement of Pig keeping the entire bag in memory until the corresponding
spill is done comes from the fact that Pig can continue to run when spilling to
a file fails. (It drops the spill file and keeps on using the bag in memory.)
Spilling can fail when disks are full but I'm guessing task would eventually
fail when that happens.
Spilling can also fail when a user passes a custom List instance that doesn't
support clear(). But for this case, this bag shouldn't be part of spillables
in the first place.
So wondering if we can provide an option to fail the task when spilling fails
and let Pig release each Tuple as soon as it writes to a spill file (before
closing).
> OOM while spilling large bag
> -
>
> Key: PIG-5384
> URL: https://issues.apache.org/jira/browse/PIG-5384
> Project: Pig
> Issue Type: Improvement
>Reporter: Koji Noguchi
>Assignee: Koji Noguchi
>Priority: Major
>
> One of the common OOM issue in Pig is, Pig hitting OOM while trying to spill
> a large bag. Current solutions is to give higher heapsize or tweak
> {noformat}
> pig.spill.memory.usage.threshold.fraction
> pig.spill.collection.threshold.fraction
> pig.spill.unused.memory.threshold.size
> {noformat}
> and make sure spilling starts early enough. These params are still critical
> but wondering if any improvement can be made to increase the chances of
> avoiding OOM while spilling a single large bag.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (PIG-5384) OOM while spilling large bag
Koji Noguchi created PIG-5384:
-
Summary: OOM while spilling large bag
Key: PIG-5384
URL: https://issues.apache.org/jira/browse/PIG-5384
Project: Pig
Issue Type: Improvement
Reporter: Koji Noguchi
Assignee: Koji Noguchi
One of the common OOM issue in Pig is, Pig hitting OOM while trying to spill a
large bag. Current solutions is to give higher heapsize or tweak
{noformat}
pig.spill.memory.usage.threshold.fraction
pig.spill.collection.threshold.fraction
pig.spill.unused.memory.threshold.size
{noformat}
and make sure spilling starts early enough. These params are still critical
but wondering if any improvement can be made to increase the chances of
avoiding OOM while spilling a single large bag.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] Subscription: PIG patch available
Issue Subscription Filter: PIG patch available (36 issues) Subscriber: pigdaily Key Summary PIG-5377Move supportsParallelWriteToStoreLocation from StoreFunc to StoreFuncInterfce https://issues.apache.org/jira/browse/PIG-5377 PIG-5369Add llap-client dependency https://issues.apache.org/jira/browse/PIG-5369 PIG-5360Pig sets working directory of input file systems causes exception thrown https://issues.apache.org/jira/browse/PIG-5360 PIG-5338Prevent deep copy of DataBag into Jython List https://issues.apache.org/jira/browse/PIG-5338 PIG-5323Implement LastInputStreamingOptimizer in Tez https://issues.apache.org/jira/browse/PIG-5323 PIG-5273_SUCCESS file should be created at the end of the job https://issues.apache.org/jira/browse/PIG-5273 PIG-5256Bytecode generation for POFilter and POForeach https://issues.apache.org/jira/browse/PIG-5256 PIG-5160SchemaTupleFrontend.java is not thread safe, cause PigServer thrown NPE in multithread env https://issues.apache.org/jira/browse/PIG-5160 PIG-5115Builtin AvroStorage generates incorrect avro schema when the same pig field name appears in the alias https://issues.apache.org/jira/browse/PIG-5115 PIG-5106Optimize when mapreduce.input.fileinputformat.input.dir.recursive set to true https://issues.apache.org/jira/browse/PIG-5106 PIG-5081Can not run pig on spark source code distribution https://issues.apache.org/jira/browse/PIG-5081 PIG-5080Support store alias as spark table https://issues.apache.org/jira/browse/PIG-5080 PIG-5057IndexOutOfBoundsException when pig reducer processOnePackageOutput https://issues.apache.org/jira/browse/PIG-5057 PIG-5029Optimize sort case when data is skewed https://issues.apache.org/jira/browse/PIG-5029 PIG-4926Modify the content of start.xml for spark mode https://issues.apache.org/jira/browse/PIG-4926 PIG-4913Reduce jython function initiation during compilation https://issues.apache.org/jira/browse/PIG-4913 PIG-4849pig on tez will cause tez-ui to crash,because the content from timeline server is too long. https://issues.apache.org/jira/browse/PIG-4849 PIG-4750REPLACE_MULTI should compile Pattern once and reuse it https://issues.apache.org/jira/browse/PIG-4750 PIG-4684Exception should be changed to warning when job diagnostics cannot be fetched https://issues.apache.org/jira/browse/PIG-4684 PIG-4656Improve String serialization and comparator performance in BinInterSedes https://issues.apache.org/jira/browse/PIG-4656 PIG-4598Allow user defined plan optimizer rules https://issues.apache.org/jira/browse/PIG-4598 PIG-4551Partition filter is not pushed down in case of SPLIT https://issues.apache.org/jira/browse/PIG-4551 PIG-4539New PigUnit https://issues.apache.org/jira/browse/PIG-4539 PIG-4515org.apache.pig.builtin.Distinct throws ClassCastException https://issues.apache.org/jira/browse/PIG-4515 PIG-4373Implement PIG-3861 in Tez https://issues.apache.org/jira/browse/PIG-4373 PIG-4323PackageConverter hanging in Spark https://issues.apache.org/jira/browse/PIG-4323 PIG-4313StackOverflowError in LIMIT operation on Spark https://issues.apache.org/jira/browse/PIG-4313 PIG-4251Pig on Storm https://issues.apache.org/jira/browse/PIG-4251 PIG-4002Disable combiner when map-side aggregation is used https://issues.apache.org/jira/browse/PIG-4002 PIG-3952PigStorage accepts '-tagSplit' to return full split information https://issues.apache.org/jira/browse/PIG-3952 PIG-3911Define unique fields with @OutputSchema https://issues.apache.org/jira/browse/PIG-3911 PIG-3877Getting Geo Latitude/Longitude from Address Lines https://issues.apache.org/jira/browse/PIG-3877 PIG-3873Geo distance calculation using Haversine https://issues.apache.org/jira/browse/PIG-3873 PIG-3668COR built-in function when atleast one of the coefficient values is NaN https://issues.apache.org/jira/browse/PIG-3668 PIG-3587add functionality for rolling over dates https://issues.apache.org/jira/browse/PIG-3587 PIG-1804Alow Jython function to implement Algebraic and/or Accumulator interfaces https://issues.apache.org/jira/browse/PIG-1804 You may edit this subscription at: https://issues.apache.org/jira/secure/EditSubscription!default.jspa?subId=16328=12322384
