[jira] [Updated] (YARN-1197) Support changing resources of an allocated container

[ https://issues.apache.org/jira/browse/YARN-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-1197: - Assignee: (was: Wangda Tan) Support changing resources of an allocated container

[jira] [Commented] (YARN-1068) Add admin support for HA operations

[ https://issues.apache.org/jira/browse/YARN-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771196#comment-13771196 ] Bikas Saha commented on YARN-1068: -- What are the pros and cons of making the new service

[jira] [Commented] (YARN-1068) Add admin support for HA operations

[ https://issues.apache.org/jira/browse/YARN-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771249#comment-13771249 ] Bikas Saha commented on YARN-1068: -- I meant the first one. Was wondering whether we should

[jira] [Commented] (YARN-1214) Register ClientToken MasterKey in SecretManager after it is saved

[ https://issues.apache.org/jira/browse/YARN-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771353#comment-13771353 ] Bikas Saha commented on YARN-1214: -- We can probably return a client token in

[jira] [Created] (YARN-1222) Make improvements in ZKRMStateStore for fencing

Bikas Saha created YARN-1222: Summary: Make improvements in ZKRMStateStore for fencing Key: YARN-1222 URL: https://issues.apache.org/jira/browse/YARN-1222 Project: Hadoop YARN Issue Type:

[jira] [Commented] (YARN-1222) Make improvements in ZKRMStateStore for fencing

[ https://issues.apache.org/jira/browse/YARN-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772273#comment-13772273 ] Bikas Saha commented on YARN-1222: -- Other improvements carried over from YARN-353 We

[jira] [Commented] (YARN-353) Add Zookeeper-based store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772275#comment-13772275 ] Bikas Saha commented on YARN-353: - We should be storing the information inside the data of

[jira] [Commented] (YARN-1068) Add admin support for HA operations

[ https://issues.apache.org/jira/browse/YARN-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772340#comment-13772340 ] Bikas Saha commented on YARN-1068: -- Another downside is having yet another port to

[jira] [Commented] (YARN-1214) Register ClientToken MasterKey in SecretManager after it is saved

[ https://issues.apache.org/jira/browse/YARN-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772329#comment-13772329 ] Bikas Saha commented on YARN-1214: -- [~vinodkv] Should master key be given to clients only

[jira] [Commented] (YARN-1214) Register ClientToken MasterKey in SecretManager after it is saved

[ https://issues.apache.org/jira/browse/YARN-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772325#comment-13772325 ] Bikas Saha commented on YARN-1214: -- Can you please mark the following with

[jira] [Commented] (YARN-1068) Add admin support for HA operations

[ https://issues.apache.org/jira/browse/YARN-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13773296#comment-13773296 ] Bikas Saha commented on YARN-1068: -- If I understand this correctly, the jira is adding RPC

[jira] [Commented] (YARN-1026) Test and verify ACL based ZKRMStateStore fencing for RM State Store

[ https://issues.apache.org/jira/browse/YARN-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13774221#comment-13774221 ] Bikas Saha commented on YARN-1026: -- Thats great. There is still something to check. In

[jira] [Commented] (YARN-1229) Shell$ExitCodeException could happen if AM fails to start

[ https://issues.apache.org/jira/browse/YARN-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775918#comment-13775918 ] Bikas Saha commented on YARN-1229: -- We should probably just rename it to MapreduceShuffle.

[jira] [Updated] (YARN-1229) Shell$ExitCodeException could happen if AM fails to start

[ https://issues.apache.org/jira/browse/YARN-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-1229: - Priority: Blocker (was: Critical) Shell$ExitCodeException could happen if AM fails to start

[jira] [Updated] (YARN-1229) Shell$ExitCodeException could happen if AM fails to start

[ https://issues.apache.org/jira/browse/YARN-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-1229: - Hadoop Flags: Incompatible change Shell$ExitCodeException could happen if AM fails to start

[jira] [Commented] (YARN-1089) Add YARN compute units alongside virtual cores

[ https://issues.apache.org/jira/browse/YARN-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13775920#comment-13775920 ] Bikas Saha commented on YARN-1089: -- I am afraid this is getting confusing.

[jira] [Commented] (YARN-1229) Shell$ExitCodeException could happen if AM fails to start

[ https://issues.apache.org/jira/browse/YARN-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13776546#comment-13776546 ] Bikas Saha commented on YARN-1229: -- base32 encoding is a good idea if we dont want to

[jira] [Commented] (YARN-1068) Add admin support for HA operations

[ https://issues.apache.org/jira/browse/YARN-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13776634#comment-13776634 ] Bikas Saha commented on YARN-1068: -- It would be educative to compare the HAAdmin server

[jira] [Commented] (YARN-986) YARN should have a ClusterId/ServiceId

[ https://issues.apache.org/jira/browse/YARN-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13776637#comment-13776637 ] Bikas Saha commented on YARN-986: - This should be used to set the service address for

[jira] [Updated] (YARN-986) YARN should have a ClusterId/ServiceId

[ https://issues.apache.org/jira/browse/YARN-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-986: Summary: YARN should have a ClusterId/ServiceId (was: YARN should have a ClusterId/ServiceId that should be

[jira] [Commented] (YARN-1229) Shell$ExitCodeException could happen if AM fails to start

[ https://issues.apache.org/jira/browse/YARN-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13776765#comment-13776765 ] Bikas Saha commented on YARN-1229: -- Looks good to me.

[jira] [Commented] (YARN-1214) Register ClientToken MasterKey in SecretManager after it is saved

[ https://issues.apache.org/jira/browse/YARN-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13776802#comment-13776802 ] Bikas Saha commented on YARN-1214: -- +1 Register ClientToken MasterKey in

[jira] [Updated] (YARN-1229) Shell$ExitCodeException could happen if AM fails to start

[ https://issues.apache.org/jira/browse/YARN-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-1229: - Fix Version/s: (was: 2.1.1-beta) 2.1.2-beta Shell$ExitCodeException could

[jira] [Updated] (YARN-1128) FifoPolicy.computeShares throws NPE on empty list of Schedulables

[ https://issues.apache.org/jira/browse/YARN-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-1128: - Fix Version/s: 2.1.2-beta FifoPolicy.computeShares throws NPE on empty list of Schedulables

[jira] [Updated] (YARN-1214) Register ClientToken MasterKey in SecretManager after it is saved

[ https://issues.apache.org/jira/browse/YARN-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-1214: - Priority: Critical (was: Major) Register ClientToken MasterKey in SecretManager after it is saved

[jira] [Commented] (YARN-1089) Add YARN compute units alongside virtual cores

[ https://issues.apache.org/jira/browse/YARN-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777051#comment-13777051 ] Bikas Saha commented on YARN-1089: -- At this point, I am not seeing the benefit of creating

[jira] [Commented] (YARN-986) YARN should have a ClusterId/ServiceId

[ https://issues.apache.org/jira/browse/YARN-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1396#comment-1396 ] Bikas Saha commented on YARN-986: - This jira has been repurposed beyond tokens. We need a

[jira] [Commented] (YARN-1232) Configuration support for RM HA

[ https://issues.apache.org/jira/browse/YARN-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777832#comment-13777832 ] Bikas Saha commented on YARN-1232: -- A description of overall approach will help understand

[jira] [Commented] (YARN-1232) Configuration support for RM HA

[ https://issues.apache.org/jira/browse/YARN-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777839#comment-13777839 ] Bikas Saha commented on YARN-1232: -- Secondly, it would be very helpful for existing

[jira] [Commented] (YARN-1068) Add admin support for HA operations

[ https://issues.apache.org/jira/browse/YARN-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777849#comment-13777849 ] Bikas Saha commented on YARN-1068: -- Lets see how YARN-986 and YARN-1232 develop and make a

[jira] [Created] (YARN-1239) Save version information in the state store

Bikas Saha created YARN-1239: Summary: Save version information in the state store Key: YARN-1239 URL: https://issues.apache.org/jira/browse/YARN-1239 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Commented] (YARN-1215) Yarn URL should include userinfo

[ https://issues.apache.org/jira/browse/YARN-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13778076#comment-13778076 ] Bikas Saha commented on YARN-1215: -- Do we need a PB for URL. Can we not serialize URL as a

[jira] [Commented] (YARN-2314) ContainerManagementProtocolProxy can create thousands of threads for a large cluster

[ https://issues.apache.org/jira/browse/YARN-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171408#comment-14171408 ] Bikas Saha commented on YARN-2314: -- Folks, this is something that would be of interest in

[jira] [Commented] (YARN-2314) ContainerManagementProtocolProxy can create thousands of threads for a large cluster

[ https://issues.apache.org/jira/browse/YARN-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171429#comment-14171429 ] Bikas Saha commented on YARN-2314: -- To be clear, my question was only to clarify if Tez

[jira] [Commented] (YARN-2314) ContainerManagementProtocolProxy can create thousands of threads for a large cluster

[ https://issues.apache.org/jira/browse/YARN-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14171459#comment-14171459 ] Bikas Saha commented on YARN-2314: -- My understanding from the comments was that in most

[jira] [Created] (YARN-78) Change UnmanagedAMLauncher to use YarnClientImpl

Bikas Saha created YARN-78: -- Summary: Change UnmanagedAMLauncher to use YarnClientImpl Key: YARN-78 URL: https://issues.apache.org/jira/browse/YARN-78 Project: Hadoop YARN Issue Type: Bug

[jira] [Created] (YARN-79) Calling YarnClientImpl.close throws Exception

Bikas Saha created YARN-79: -- Summary: Calling YarnClientImpl.close throws Exception Key: YARN-79 URL: https://issues.apache.org/jira/browse/YARN-79 Project: Hadoop YARN Issue Type: Bug

[jira] [Updated] (YARN-78) Change UnmanagedAMLauncher to use YarnClientImpl

[ https://issues.apache.org/jira/browse/YARN-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-78: --- Attachment: YARN-78.1.patch Change UnmanagedAMLauncher to use YarnClientImpl

[jira] [Commented] (YARN-79) Calling YarnClientImpl.close throws Exception

[ https://issues.apache.org/jira/browse/YARN-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13448153#comment-13448153 ] Bikas Saha commented on YARN-79: Looks ok +1. Surprising that the AMRMProtocol.close() did

[jira] [Commented] (YARN-78) Change UnmanagedAMLauncher to use YarnClientImpl

[ https://issues.apache.org/jira/browse/YARN-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13449027#comment-13449027 ] Bikas Saha commented on YARN-78: I have updated the patch to now call stop() and existing

[jira] [Updated] (YARN-78) Change UnmanagedAMLauncher to use YarnClientImpl

[ https://issues.apache.org/jira/browse/YARN-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-78: --- Attachment: YARN-78.2.patch Change UnmanagedAMLauncher to use YarnClientImpl

[jira] [Commented] (YARN-83) Change package of YarnClient to include apache

[ https://issues.apache.org/jira/browse/YARN-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13449081#comment-13449081 ] Bikas Saha commented on YARN-83: Thats because this was broken into 2 patches. 1 for YARN and

[jira] [Updated] (YARN-78) Change UnmanagedAMLauncher to use YarnClientImpl

[ https://issues.apache.org/jira/browse/YARN-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-78: --- Attachment: YARN-78.3.patch Change UnmanagedAMLauncher to use YarnClientImpl

[jira] [Updated] (YARN-78) Change UnmanagedAMLauncher to use YarnClientImpl

[ https://issues.apache.org/jira/browse/YARN-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-78: --- Attachment: YARN-78.4.patch Fixing pom dependency that wasnt exposed until I did a clean install build.

[jira] [Updated] (YARN-103) Add a yarn AM - RM client module

[ https://issues.apache.org/jira/browse/YARN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-103: Attachment: YARN-103.1.patch Add a yarn AM - RM client module

[jira] [Commented] (YARN-72) NM should handle cleaning up containers when it shuts down ( and kill containers from an earlier instance when it comes back up after an unclean shutdown )

[ https://issues.apache.org/jira/browse/YARN-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13462386#comment-13462386 ] Bikas Saha commented on YARN-72: Pids might get reused. so we need to guard against that. Is

[jira] [Updated] (YARN-103) Add a yarn AM - RM client module

[ https://issues.apache.org/jira/browse/YARN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-103: Attachment: YARN-103.4.patch Add a yarn AM - RM client module

[jira] [Commented] (YARN-103) Add a yarn AM - RM client module

[ https://issues.apache.org/jira/browse/YARN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13471344#comment-13471344 ] Bikas Saha commented on YARN-103: - - Changed to addResourceRequest. - Changed javadoc. -

[jira] [Updated] (YARN-103) Add a yarn AM - RM client module

[ https://issues.apache.org/jira/browse/YARN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-103: Attachment: YARN-103.4.wrapper.patch Add a yarn AM - RM client module

[jira] [Commented] (YARN-103) Add a yarn AM - RM client module

[ https://issues.apache.org/jira/browse/YARN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13471345#comment-13471345 ] Bikas Saha commented on YARN-103: - Per your comments in MAPREDUCE-4671, I have attached

[jira] [Commented] (YARN-103) Add a yarn AM - RM client module

[ https://issues.apache.org/jira/browse/YARN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13473049#comment-13473049 ] Bikas Saha commented on YARN-103: - This version of the client is for advanced apps like MR

[jira] [Updated] (YARN-103) Add a yarn AM - RM client module

[ https://issues.apache.org/jira/browse/YARN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-103: Attachment: YARN-103.5.patch Add a yarn AM - RM client module

[jira] [Commented] (YARN-178) Fix custom ProcessTree instance creation

[ https://issues.apache.org/jira/browse/YARN-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13482068#comment-13482068 ] Bikas Saha commented on YARN-178: - The change looks reasonable. What is not clear is why

[jira] [Commented] (YARN-178) Fix custom ProcessTree instance creation

[ https://issues.apache.org/jira/browse/YARN-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13482247#comment-13482247 ] Bikas Saha commented on YARN-178: - Then why add it to the constructor of the abstract base

[jira] [Commented] (YARN-178) Fix custom ProcessTree instance creation

[ https://issues.apache.org/jira/browse/YARN-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13482917#comment-13482917 ] Bikas Saha commented on YARN-178: - Sure. Please go ahead. Fix custom

[jira] [Commented] (YARN-72) NM should handle cleaning up containers when it shuts down ( and kill containers from an earlier instance when it comes back up after an unclean shutdown )

[ https://issues.apache.org/jira/browse/YARN-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13485330#comment-13485330 ] Bikas Saha commented on YARN-72: Do we intend to stall shutdown indefinitely for this

[jira] [Commented] (YARN-3) Add support for CPU isolation/monitoring of containers

[ https://issues.apache.org/jira/browse/YARN-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13485570#comment-13485570 ] Bikas Saha commented on YARN-3: --- Why is mountCGroups a method in LinuxContainerExecutor code?

[jira] [Commented] (YARN-3) Add support for CPU isolation/monitoring of containers

[ https://issues.apache.org/jira/browse/YARN-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13485571#comment-13485571 ] Bikas Saha commented on YARN-3: --- Does anything need to be done in a context similar to YARN-72

[jira] [Commented] (YARN-103) Add a yarn AM - RM client module

[ https://issues.apache.org/jira/browse/YARN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13486111#comment-13486111 ] Bikas Saha commented on YARN-103: - Ping Add a yarn AM - RM client module

[jira] [Moved] (YARN-199) yarn cmd line scripts for windows

[ https://issues.apache.org/jira/browse/YARN-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha moved MAPREDUCE-4768 to YARN-199: Target Version/s: (was: trunk-win) Affects Version/s: (was:

[jira] [Commented] (YARN-199) yarn cmd line scripts for windows

[ https://issues.apache.org/jira/browse/YARN-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13489956#comment-13489956 ] Bikas Saha commented on YARN-199: - yarn-config.cmd seems to miss some stuff thats present in

[jira] [Commented] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13491635#comment-13491635 ] Bikas Saha commented on YARN-128: - Devaraj, I think the current approach+code based on

[jira] [Commented] (YARN-199) yarn cmd line scripts for windows

[ https://issues.apache.org/jira/browse/YARN-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13492114#comment-13492114 ] Bikas Saha commented on YARN-199: - Thanks! MALLOC_ARENA_MAX seems to be still missing from

[jira] [Created] (YARN-209) Capacity scheduler can leave application in pending state

Bikas Saha created YARN-209: --- Summary: Capacity scheduler can leave application in pending state Key: YARN-209 URL: https://issues.apache.org/jira/browse/YARN-209 Project: Hadoop YARN Issue Type:

[jira] [Updated] (YARN-209) Capacity scheduler can leave application in pending state

[ https://issues.apache.org/jira/browse/YARN-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-209: Attachment: (was: YARN-209.1.patch) Capacity scheduler can leave application in pending state

[jira] [Updated] (YARN-209) Capacity scheduler can leave application in pending state

[ https://issues.apache.org/jira/browse/YARN-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-209: Attachment: YARN-209-test.patch Capacity scheduler can leave application in pending state

[jira] [Commented] (YARN-209) Capacity scheduler can leave application in pending state

[ https://issues.apache.org/jira/browse/YARN-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13494622#comment-13494622 ] Bikas Saha commented on YARN-209: - Attaching a fix for the issue. Also attaching a test that

[jira] [Commented] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13494892#comment-13494892 ] Bikas Saha commented on YARN-128: - Updating patches for new code and combined patch. Changes

[jira] [Updated] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-128: Attachment: YARN-128.combined.2.patch Resurrect RM Restart -

[jira] [Updated] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-128: Attachment: YARN-128.new-code-added.3.patch YARN-128.old-code-removed.3.patch Resurrect

[jira] [Commented] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13495097#comment-13495097 ] Bikas Saha commented on YARN-128: - Attaching rebased patches Resurrect RM

[jira] [Updated] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-128: Attachment: YARN-128.full-code.3.patch Resurrect RM Restart -

[jira] [Updated] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-128: Attachment: (was: YARN-128-combined.patch) Resurrect RM Restart -

[jira] [Updated] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-128: Attachment: (was: YARN-128.new-code.1.patch) Resurrect RM Restart -

[jira] [Updated] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-128: Attachment: (was: YARN-128.combined.2.patch) Resurrect RM Restart -

[jira] [Updated] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-128: Attachment: YARN-128.new-code-added-4.patch Resurrect RM Restart -

[jira] [Updated] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-128: Attachment: YARN-128.full-code-4.patch Resurrect RM Restart -

[jira] [Updated] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-128: Attachment: (was: YARN-128.full-code-4.patch) Resurrect RM Restart -

[jira] [Updated] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-128: Attachment: (was: YARN-128.new-code-added-4.patch) Resurrect RM Restart -

[jira] [Updated] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-128: Attachment: YARN-128.new-code-added-4.patch YARN-128.old-code-removed.4.patch Resurrect

[jira] [Updated] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-128: Attachment: YARN-128.full-code-4.patch Resurrect RM Restart -

[jira] [Commented] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13496129#comment-13496129 ] Bikas Saha commented on YARN-128: - Attaching rebased patches + change RMStateStore to throw

[jira] [Commented] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13498726#comment-13498726 ] Bikas Saha commented on YARN-128: - 1) Unless I am mistaken, the test condition is correct.

[jira] [Updated] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-128: Attachment: restart-12-11-zkstore.patch Resurrect RM Restart -

[jira] [Commented] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13498876#comment-13498876 ] Bikas Saha commented on YARN-128: - @Arinto Thanks for using the code! 1) Yes. Both are the

[jira] [Commented] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501172#comment-13501172 ] Bikas Saha commented on YARN-128: - Attaching final patch with full changes for a test run.

[jira] [Commented] (YARN-218) Distiguish between failed and killed app attempts

[ https://issues.apache.org/jira/browse/YARN-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501174#comment-13501174 ] Bikas Saha commented on YARN-218: - Another thing to fix would be checking for maxRetries

[jira] [Created] (YARN-229) Remove old code for restart

Bikas Saha created YARN-229: --- Summary: Remove old code for restart Key: YARN-229 URL: https://issues.apache.org/jira/browse/YARN-229 Project: Hadoop YARN Issue Type: Sub-task Reporter:

[jira] [Created] (YARN-231) Add ZooKeeper based store for RM

Bikas Saha created YARN-231: --- Summary: Add ZooKeeper based store for RM Key: YARN-231 URL: https://issues.apache.org/jira/browse/YARN-231 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Created] (YARN-232) Add FileSystem based store for RM

Bikas Saha created YARN-232: --- Summary: Add FileSystem based store for RM Key: YARN-232 URL: https://issues.apache.org/jira/browse/YARN-232 Project: Hadoop YARN Issue Type: Sub-task

[jira] [Updated] (YARN-229) Remove old code for restart

[ https://issues.apache.org/jira/browse/YARN-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-229: Attachment: YARN-229.1.patch This patch removes the old code. Would be good to commit this quickly.

[jira] [Updated] (YARN-230) Make changes for RM restart phase 1

[ https://issues.apache.org/jira/browse/YARN-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-230: Attachment: YARN-230.1.patch Make changes for RM restart phase 1 ---

[jira] [Commented] (YARN-230) Make changes for RM restart phase 1

[ https://issues.apache.org/jira/browse/YARN-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501213#comment-13501213 ] Bikas Saha commented on YARN-230: - Attached patch applies on top of patch for YARN-229

[jira] [Updated] (YARN-231) Add persistent store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-231: Description: Add stores that write RM state data to ZooKeeper and FileSystem (was: Add a store that writes

[jira] [Updated] (YARN-231) Add persistent store implementation for RMStateStore

[ https://issues.apache.org/jira/browse/YARN-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-231: Attachment: YARN-231.1.patch This patch applies on top of the patches for YARN-229 and YARN-230

[jira] [Commented] (YARN-128) Resurrect RM Restart

[ https://issues.apache.org/jira/browse/YARN-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13501221#comment-13501221 ] Bikas Saha commented on YARN-128: - Done creating sub-tasks and attaching final patches for

[jira] [Resolved] (YARN-232) Add FileSystem based store for RM

[ https://issues.apache.org/jira/browse/YARN-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha resolved YARN-232. - Resolution: Implemented Patch submitted to YARN-231 Add FileSystem based store for RM

[jira] [Updated] (YARN-230) Make changes for RM restart phase 1

[ https://issues.apache.org/jira/browse/YARN-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-230: Attachment: Test.patch Store.patch Recovery.patch

[jira] [Updated] (YARN-230) Make changes for RM restart phase 1

[ https://issues.apache.org/jira/browse/YARN-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-230: Attachment: (was: Recovery.patch) Make changes for RM restart phase 1

[jira] [Updated] (YARN-230) Make changes for RM restart phase 1

[ https://issues.apache.org/jira/browse/YARN-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bikas Saha updated YARN-230: Attachment: (was: Store.patch) Make changes for RM restart phase 1

<    1   2   3   4   5   6   7   8   9   10   >