[jira] [Updated] (FALCON-2175) java.lang.IllegalArgumentException in LogMover service
[
https://issues.apache.org/jira/browse/FALCON-2175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2175:
Fix Version/s: 0.11
> java.lang.IllegalArgumentException in LogMover service
> ---
>
> Key: FALCON-2175
> URL: https://issues.apache.org/jira/browse/FALCON-2175
> Project: Falcon
> Issue Type: Bug
>Reporter: Pallavi Rao
>Assignee: Pallavi Rao
> Fix For: trunk, 0.11
>
>
> 2016-10-25 19:19:02,581 DEBUG - [ActiveMQ Session Task-12:] ~ Sending
> workflow end notification to listeners with context :
> WorkflowExecutionContext{{nominalTime=2016-10-25-19-00,
> workflowEndTime=1477423129270, parentId=008-161025181049892-oozie-oozi-C,
> entityType=PROCESS, cluster=ProcessSLATest-corp-b16d2875,
> workflowId=008-161025181049892-oozie-oozi-C@11, operation=GENERATE,
> status=TIMEDOUT, entityName=ProcessSLATest-1, workflowUser=dataqa,
> contextType=COORDINATOR_ACTION,
> subflowId=008-161025181049892-oozie-oozi-C@11@user-action,
> workflowStartTime=1477423142578}} (WorkflowJobEndNotificationService:234)
> 2016-10-25 19:19:02,581 ERROR - [pool-4-thread-5:] ~ Exception in log mover:
> (JobLogMover:140)
> java.lang.IllegalArgumentException: oozieUrl cannot be null
> at
> org.apache.oozie.client.OozieClient.notEmpty(OozieClient.java:2789)
> at
> org.apache.oozie.client.OozieClient.(OozieClient.java:260)
> at
> org.apache.falcon.logging.JobLogMover.run(JobLogMover.java:87)
> at
> org.apache.falcon.logging.JobLogMover.moveLog(JobLogMover.java:78)
> at
> org.apache.falcon.service.LogMoverService$LogMover.run(LogMoverService.java:118)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2202) Falcon Unit changes to support extensions
[ https://issues.apache.org/jira/browse/FALCON-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2202: Fix Version/s: 0.11 trunk > Falcon Unit changes to support extensions > -- > > Key: FALCON-2202 > URL: https://issues.apache.org/jira/browse/FALCON-2202 > Project: Falcon > Issue Type: Improvement > Components: extensions >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Falcon Unit needs to enhanced to accommodate extensions and also validate > user extensions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2173) BacklogEmitterService should emit 0 for process which donot have backlog
[ https://issues.apache.org/jira/browse/FALCON-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2173: Fix Version/s: 0.11 > BacklogEmitterService should emit 0 for process which donot have backlog > > > Key: FALCON-2173 > URL: https://issues.apache.org/jira/browse/FALCON-2173 > Project: Falcon > Issue Type: Improvement >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > Currently the backlog emitter service doesn't emit anything if the process > does not have a backlog ,ideally it should emit zero in such cases. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2116) Queue defined in is not getting used in actual retention job
[
https://issues.apache.org/jira/browse/FALCON-2116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2116:
Fix Version/s: 0.11
> Queue defined in is not getting used in actual retention job
> --
>
> Key: FALCON-2116
> URL: https://issues.apache.org/jira/browse/FALCON-2116
> Project: Falcon
> Issue Type: Bug
>Reporter: sandeep samudrala
>Assignee: sandeep samudrala
> Fix For: trunk, 0.11
>
>
> Following feed definition segment is not working properly, Both replication
> and retention jobs are running in "m10n" queue and queue from retention-stage
> is not getting picked up:
> {noformat}
>
>
>
>
>
>
> hours(1)
> default
> NORMAL
>
> value="days(10)"/>
>
>
>
> {noformat}
> Here we have a feed which replicates data from local to global cluster. We
> have queue "m10n" in global, but not in local colos. So we have specified
> "default" queue for retention jobs and "m10n" for replication jobs.
> But both are getting "m10n" queue. Due to which retention jobs in local colos
> are getting suspended.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2238) Falcon extension describe feature is broken
[
https://issues.apache.org/jira/browse/FALCON-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2238:
Fix Version/s: 0.11
> Falcon extension describe feature is broken
> ---
>
> Key: FALCON-2238
> URL: https://issues.apache.org/jira/browse/FALCON-2238
> Project: Falcon
> Issue Type: Bug
> Components: extensions
>Affects Versions: trunk
>Reporter: Pragya Mittal
>Assignee: Pracheer Agarwal
> Fix For: trunk, 0.11
>
>
> Falcon extension describe fails with following error :
> {noformat}
> dataqa@falcon1001:~$ falcon extension -describe -extensionName
> extension-example
> Hadoop is installed, adding hadoop classpath to falcon classpath
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/mnt/falcon/prism/client/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/usr/hdp/2.2.4.2-2/hadoop/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> Jan 09, 2017 10:33:38 AM com.sun.jersey.api.client.ClientResponse getEntity
> SEVERE: A message body reader for Java class
> org.apache.falcon.resource.APIResult, and Java type class
> org.apache.falcon.resource.APIResult, and MIME media type text/html;
> charset=iso-8859-1 was not found
> Jan 09, 2017 10:33:38 AM com.sun.jersey.api.client.ClientResponse getEntity
> SEVERE: The registered message body readers compatible with the MIME media
> type are:
> */* ->
> com.sun.jersey.core.impl.provider.entity.FormProvider
> com.sun.jersey.core.impl.provider.entity.MimeMultipartProvider
> com.sun.jersey.core.impl.provider.entity.StringProvider
> com.sun.jersey.core.impl.provider.entity.ByteArrayProvider
> com.sun.jersey.core.impl.provider.entity.FileProvider
> com.sun.jersey.core.impl.provider.entity.InputStreamProvider
> com.sun.jersey.core.impl.provider.entity.DataSourceProvider
> com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General
> com.sun.jersey.core.impl.provider.entity.ReaderProvider
> com.sun.jersey.core.impl.provider.entity.DocumentProvider
> com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader
> com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader
> com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader
> com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General
> com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General
> com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General
> com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General
> com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General
> com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General
> com.sun.jersey.core.impl.provider.entity.EntityHolderReader
> com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General
> com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General
> com.sun.jersey.json.impl.provider.entity.JacksonProviderProxy
> ERROR: Internal Server Error;
>
>
> Error 500 Internal Server Error
>
> HTTP ERROR 500
> Problem accessing /api/extension/describe/extension-example. Reason:
> Internal Server ErrorPowered by
> Jetty://
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2272) Extension update succeeds while it is disabled
[
https://issues.apache.org/jira/browse/FALCON-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2272:
Fix Version/s: 0.11
> Extension update succeeds while it is disabled
> --
>
> Key: FALCON-2272
> URL: https://issues.apache.org/jira/browse/FALCON-2272
> Project: Falcon
> Issue Type: Bug
> Components: extensions
>Affects Versions: trunk
>Reporter: Pragya Mittal
>Assignee: sandeep samudrala
> Fix For: trunk, 0.11
>
>
> {noformat}
> pragya.mittal@falcon1001:~$ falcon extension -disable -extensionName
> extension-example
> Status of extension: extension-examplechanged to disabled state state.
> {noformat}
> {noformat}
> pragya.mittal@falcon1001:~$ fepdef sample3-ProcessRecipe-test
>
> xmlns="uri:falcon:process:0.1">
>
> _falcon_extension_name=extension-example,_falcon_extension_job=sample3
> testSample1
>
>
>
>
>
> 1
> FIFO
> minutes(3)
> UTC
>
> end="now(0,0)"/>
>
>
> instance="now(0,5)"/>
>
>
>
> value="${formatTime(dateOffset(instanceTime(), 1, 'DAY'), '-MMM-dd')}"/>
>
>
>
>
>
>
> {noformat}
> Updating the extension to change process frequency from minutes(3) to
> minutes(5) should fail as extension is disabled. But it succeeds.
> {noformat}
> pragya.mittal@falcon1001:~$ falcon extension -update -extensionName
> extension-example -jobName sample3 -file abc
> Updated successfully
> {noformat}
> New process definition is :
> {noformat}
> pragya.mittal@falcon1001:~$ fepdef sample3-ProcessRecipe-test
>
> xmlns="uri:falcon:process:0.1">
>
> _falcon_extension_name=extension-example,_falcon_extension_job=sample3
> testSample1
>
>
>
>
>
> 1
> FIFO
> minutes(5)
> UTC
>
> end="now(0,0)"/>
>
>
> instance="now(0,5)"/>
>
>
>
> value="${formatTime(dateOffset(instanceTime(), 1, 'DAY'), '-MMM-dd')}"/>
>
>
>
>
>
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2123) Make Blocking Queue configurable in LogMoverService
[ https://issues.apache.org/jira/browse/FALCON-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2123: Fix Version/s: 0.11 > Make Blocking Queue configurable in LogMoverService > --- > > Key: FALCON-2123 > URL: https://issues.apache.org/jira/browse/FALCON-2123 > Project: Falcon > Issue Type: Improvement >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > Right now the queue size is hard coded to 50 which might be fine in > production but its better to have it configurable. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2213) Falcon logs does not contain response message when recipe operations are performed.
[ https://issues.apache.org/jira/browse/FALCON-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2213: Fix Version/s: 0.11 trunk > Falcon logs does not contain response message when recipe operations are > performed. > --- > > Key: FALCON-2213 > URL: https://issues.apache.org/jira/browse/FALCON-2213 > Project: Falcon > Issue Type: Bug > Components: extensions >Affects Versions: trunk >Reporter: Pragya Mittal > Fix For: trunk, 0.11 > > > If register/unregister/submit or any command is called via falcon cli for > extensions then log does not contain response message. It is a problem while > debugging to look at the logs and find the cause for it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2097) Feed update with replication delay creates random number of holes/overlaps
[ https://issues.apache.org/jira/browse/FALCON-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2097: Fix Version/s: 0.11 > Feed update with replication delay creates random number of holes/overlaps > --- > > Key: FALCON-2097 > URL: https://issues.apache.org/jira/browse/FALCON-2097 > Project: Falcon > Issue Type: Bug > Components: replication >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Caused by FALCON-298 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2200) Update API support for extension job (user extension)
[ https://issues.apache.org/jira/browse/FALCON-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2200: Fix Version/s: 0.11 > Update API support for extension job (user extension) > - > > Key: FALCON-2200 > URL: https://issues.apache.org/jira/browse/FALCON-2200 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: Pallavi Rao >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2194) Enhance validate API to support config validation for user extensions
[ https://issues.apache.org/jira/browse/FALCON-2194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2194: Fix Version/s: 0.11 > Enhance validate API to support config validation for user extensions > - > > Key: FALCON-2194 > URL: https://issues.apache.org/jira/browse/FALCON-2194 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: Pallavi Rao >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Just like entity validate command, Extension User should be able to validate > the user configs with the Extension Developer's Builder. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-1856) Fix ProcessInstanceStatusTest
[ https://issues.apache.org/jira/browse/FALCON-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-1856: Fix Version/s: 0.11 trunk > Fix ProcessInstanceStatusTest > - > > Key: FALCON-1856 > URL: https://issues.apache.org/jira/browse/FALCON-1856 > Project: Falcon > Issue Type: Improvement > Components: regression >Affects Versions: trunk, 0.10 >Reporter: Pragya Mittal >Assignee: Pragya Mittal > Fix For: trunk, 0.11 > > > ProcessInstanceStatusTest is failing due to READY state coming into > picture.Fixing the same. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2226) Submit ,Schedule and submitAndSchedule API for extension in distributed mode
[ https://issues.apache.org/jira/browse/FALCON-2226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2226: Fix Version/s: 0.11 trunk > Submit ,Schedule and submitAndSchedule API for extension in distributed mode > > > Key: FALCON-2226 > URL: https://issues.apache.org/jira/browse/FALCON-2226 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > As a part of this jira I will be working on adding 3 api i.e submit ,schedule > and submitAndSchedule. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-1999) Merge pending patches and update fix version
[ https://issues.apache.org/jira/browse/FALCON-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-1999: Fix Version/s: (was: 0.10) 0.11 trunk > Merge pending patches and update fix version > > > Key: FALCON-1999 > URL: https://issues.apache.org/jira/browse/FALCON-1999 > Project: Falcon > Issue Type: Sub-task > Components: general >Reporter: Balu Vellanki >Assignee: Balu Vellanki > Fix For: trunk, 0.11 > > > We need to merge pending patches what ever we can accommodate in QA before > 0.10 release of Falcon. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2270) Extension job details returns incomplete response
[
https://issues.apache.org/jira/browse/FALCON-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2270:
Fix Version/s: 0.11
> Extension job details returns incomplete response
> -
>
> Key: FALCON-2270
> URL: https://issues.apache.org/jira/browse/FALCON-2270
> Project: Falcon
> Issue Type: Bug
> Components: extensions
>Affects Versions: trunk
>Reporter: Pragya Mittal
>Assignee: Pallavi Rao
> Fix For: trunk, 0.11
>
>
> {noformat}
> pragya.mittal@falcon1001:~$ falcon extension -detail -jobName sample1
> {
> "jobName": "sample1",
> "extensionName": "extension-example",
> "feeds": {
>"name": "sample1-output-feed",
>"status": "EXISTS"
> },
> "processes": {
>"name": "sample1-ProcessRecipe-test",
>"status": "EXISTS"
> },
> "creationTime": "Tue Jan 31 06:58:29 GMT 2017",
> "lastUpdatedTime": "Tue Jan 31 06:58:29 GMT 2017",
> "location": "hdfs://192.168.138.236:8020/tmp/extensions/extension-example",
> "type": "Custom extension"
> }
> {noformat}
> sample1-input-feed is missing
> Following is the extension job process definition :
> {noformat}
> pragya.mittal@falcon1001:~$ fepdef sample1-ProcessRecipe-test
>
>
>
> _falcon_extension_name=extension-example,_falcon_extension_job=sample1
>testSample1
>
>
>
>
>
>1
>FIFO
>minutes(3)
>UTC
>
> end="now(0,0)"/>
>
>
> instance="now(0,5)"/>
>
>
>
> value="${formatTime(dateOffset(instanceTime(), 1, 'DAY'), '-MMM-dd')}"/>
>
>
>
>
>
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2225) Falcon fails to start with ExtensionService
[
https://issues.apache.org/jira/browse/FALCON-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2225:
Fix Version/s: 0.11
> Falcon fails to start with ExtensionService
>
>
> Key: FALCON-2225
> URL: https://issues.apache.org/jira/browse/FALCON-2225
> Project: Falcon
> Issue Type: Sub-task
> Components: extensions
>Reporter: Praveen Adlakha
>Assignee: Pracheer Agarwal
> Fix For: trunk, 0.11
>
>
> Hi All,
> Falcon fails to start with extension service.
> {code}
> 2016-12-19 17:56:35,433 ERROR - [main:] ~ Failed to initialize service
> org.apache.falcon.extensions.ExtensionService (ServiceInitializer:49)
> java.lang.ExceptionInInitializerError
> at
> org.apache.falcon.extensions.ExtensionService.getExtensionStore(ExtensionService.java:47)
> at
> org.apache.falcon.extensions.ExtensionService.init(ExtensionService.java:39)
> at
> org.apache.falcon.service.ServiceInitializer.initialize(ServiceInitializer.java:47)
> at
> org.apache.falcon.listener.ContextStartupListener.contextInitialized(ContextStartupListener.java:56)
> at
> org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:550)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
> at
> org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1282)
> at
> org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:519)
> at
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> at org.mortbay.jetty.Server.doStart(Server.java:224)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.apache.falcon.util.EmbeddedServer.start(EmbeddedServer.java:58)
> at org.apache.falcon.FalconServer.main(FalconServer.java:118)
> Caused by: java.lang.IllegalStateException: No user logged into the system
> at org.apache.falcon.security.CurrentUser.getUser(CurrentUser.java:176)
> at
> org.apache.falcon.extensions.store.ExtensionStore.initializeDbTable(ExtensionStore.java:107)
> at
> org.apache.falcon.extensions.store.ExtensionStore.(ExtensionStore.java:94)
> at
> org.apache.falcon.extensions.store.ExtensionStore.(ExtensionStore.java:79)
> ... 15 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2195) Add API to get details of an extension job
[ https://issues.apache.org/jira/browse/FALCON-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2195: Fix Version/s: 0.11 > Add API to get details of an extension job > -- > > Key: FALCON-2195 > URL: https://issues.apache.org/jira/browse/FALCON-2195 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: Pallavi Rao >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Given an extension name and job Name, the API must return the following > details: > 1. the Feed names and process names created. > 2. The config used by the user while creating this job. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-1992) Prepare Falcon Release v0.10
[ https://issues.apache.org/jira/browse/FALCON-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-1992: Fix Version/s: (was: 0.10) 0.11 trunk > Prepare Falcon Release v0.10 > > > Key: FALCON-1992 > URL: https://issues.apache.org/jira/browse/FALCON-1992 > Project: Falcon > Issue Type: Task > Components: ease >Affects Versions: 0.9 >Reporter: Balu Vellanki >Assignee: Balu Vellanki > Labels: release > Fix For: trunk, 0.11 > > > This is a parent holding ticket for tracking all tasks relating to 0.10 > release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2163) Feed replication based on partition does not produce expected output
[
https://issues.apache.org/jira/browse/FALCON-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2163:
Fix Version/s: 0.11
> Feed replication based on partition does not produce expected output
>
>
> Key: FALCON-2163
> URL: https://issues.apache.org/jira/browse/FALCON-2163
> Project: Falcon
> Issue Type: Bug
> Components: feed, prism
>Affects Versions: trunk
>Reporter: Pragya Mittal
>Assignee: Pallavi Rao
> Fix For: trunk, 0.11
>
>
> Feed :
> {noformat}
> name="PrismFeedReplicationPartitionExpTest-InputFeed-021eefe6"
> description="Input File">
>
>
>
>
>
>
> minutes(5)
>
>
> name="PrismFeedReplicationPartitionExpTest-falcon2-stg4-5698a59c"
> type="source" partition="${cluster.colo}">
>
>
>
> path="/tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/source1/${YEAR}/${MONTH}/${DAY}/${HOUR}/${MINUTE}"/>
>
>
> name="PrismFeedReplicationPartitionExpTest-falcon2-stg4-7a96289d"
> type="target">
>
>
>
> path="/tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/clusterPath/localDC/rc/billing/replicated/${YEAR}/${MONTH}/${DAY}/${HOUR}/${MINUTE}"/>
>
>
> name="PrismFeedReplicationPartitionExpTest-falcon2-stg4-d4fbf2d9"
> type="source" partition="${cluster.colo}">
>
>
>
> path="/tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/localDC/rc/billing/${YEAR}/${MONTH}/${DAY}/${HOUR}/${MINUTE}"/>
>
>
>
>
> path="/data/regression/fetlrc/billing/${YEAR}/${MONTH}/${DAY}/${HOUR}/${MINUTE}"/>
>
> path="/data/regression/fetlrc/billing/metadata"/>
>
>
> provider="protobuf"/>
>
>
>
>
>
> {noformat}
> Cluster 1 data :
> {noformat}
> dataqa@falcon1001:~$ hlr
> /tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/source1/2012/10/01/12/*/*
> 16/09/28 10:53:02 INFO util.Shell: ===Loading custom Shell class
> JIRA:GRIDOPS-4518 ==
> lsr: DEPRECATED: Please use 'ls -R' instead.
> -rw-r--r-- 3 pragya hdfs 2298 2016-09-28 10:33
> /tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/source1/2012/10/01/12/00/ua1/dataFile.xml
> -rw-r--r-- 3 pragya hdfs 2298 2016-09-28 10:33
> /tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/source1/2012/10/01/12/00/ua2/dataFile.xml
> -rw-r--r-- 3 pragya hdfs 2298 2016-09-28 10:33
> /tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/source1/2012/10/01/12/00/ua3/dataFile.xml
> -rw-r--r-- 3 pragya hdfs922 2016-09-28 10:33
> /tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/source1/2012/10/01/12/05/ua1/id.pig
> -rw-r--r-- 3 pragya hdfs922 2016-09-28 10:33
> /tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/source1/2012/10/01/12/05/ua2/id.pig
> -rw-r--r-- 3 pragya hdfs922 2016-09-28 10:33
> /tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/source1/2012/10/01/12/05/ua3/id.pig
> {noformat}
> Cluster 3 data :
> {noformat}
> dataqa@hydra:~$ hlr
> /tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/dataBillingRC/fetlrc/billing/2012/10/01/12/*/*
> lsr: DEPRECATED: Please use 'ls -R' instead.
> -rw-r--r-- 3 pragya hdfs 2298 2016-09-28 10:33
> /tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/dataBillingRC/fetlrc/billing/2012/10/01/12/00/ua1/dataFile.xml
> -rw-r--r-- 3 pragya hdfs 2298 2016-09-28 10:33
> /tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/dataBillingRC/fetlrc/billing/2012/10/01/12/00/ua2/dataFile.xml
> -rw-r--r-- 3 pragya hdfs 2298 2016-09-28 10:33
> /tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/dataBillingRC/fetlrc/billing/2012/10/01/12/00/ua3/dataFile.xml
> -rw-r--r-- 3 pragya hdfs922 2016-09-28 10:33
> /tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/dataBillingRC/fetlrc/billing/2012/10/01/12/05/ua1/id.pig
> -rw-r--r-- 3 pragya hdfs922 2016-09-28 10:33
> /tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/dataBillingRC/fetlrc/billing/2012/10/01/12/05/ua2/id.pig
> -rw-r--r-- 3 pragya hdfs922 2016-09-28 10:33
> /tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/dataBillingRC/fetlrc/billing/2012/10/01/12/05/ua3/id.pig
> -rw-r--r-- 3 pragya hdfs 1711 2016-09-28 10:33
> /tmp/falcon-regression/PrismFeedReplicationPartitionExpTest/dataBillingRC/fetlrc/billing/2012/10/01/12/10/ua1/cluster-0.1.xml
> -rw-r--r-- 3 pragya hdfs 1711 2016-09-28 10:33
>
[jira] [Updated] (FALCON-1611) Add admin commands to Falcon spring-shell CLI
[ https://issues.apache.org/jira/browse/FALCON-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-1611: Fix Version/s: 0.11 > Add admin commands to Falcon spring-shell CLI > - > > Key: FALCON-1611 > URL: https://issues.apache.org/jira/browse/FALCON-1611 > Project: Falcon > Issue Type: Sub-task >Reporter: Rajat Khandelwal >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2203) Minor issues in EntitySLAmonitoring
[ https://issues.apache.org/jira/browse/FALCON-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2203: Fix Version/s: 0.11 > Minor issues in EntitySLAmonitoring > > > Key: FALCON-2203 > URL: https://issues.apache.org/jira/browse/FALCON-2203 > Project: Falcon > Issue Type: Bug >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > This issue is for tracking is minor issues in EntitySLAMonitoring. > The code in this pull request was written by [~sandeep.samudrala] > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2111) Build failed due to checkstyle violation
[
https://issues.apache.org/jira/browse/FALCON-2111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2111:
Fix Version/s: 0.11
> Build failed due to checkstyle violation
> -
>
> Key: FALCON-2111
> URL: https://issues.apache.org/jira/browse/FALCON-2111
> Project: Falcon
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Balu Vellanki
>Assignee: Balu Vellanki
> Fix For: trunk, 0.11
>
>
> {code}
> [INFO] Exclude: **/falcon-cli-hist.log
> [INFO]
> [INFO] --- maven-checkstyle-plugin:2.9.1:check (checkstyle-check) @
> falcon-common ---
> [INFO] Starting audit...
> :53:
> Line is longer than 120 characters.
> Audit done.
> [INFO] There are 1 checkstyle errors.
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Falcon .. SUCCESS [ 14.095
> s]
> [INFO] Apache Falcon UI ... SUCCESS [ 15.386
> s]
> [INFO] Build Tools SUCCESS [ 6.158
> s]
> [INFO] Apache Falcon Java client .. SUCCESS [ 41.506
> s]
> [INFO] Apache Falcon Shell SUCCESS [ 15.622
> s]
> [INFO] Apache Falcon Metrics .. SUCCESS [ 17.478
> s]
> [INFO] Apache Falcon Hadoop Dependencies .. SUCCESS [ 14.766
> s]
> [INFO] Apache Falcon Test Utility . SUCCESS [ 13.427
> s]
> [INFO] Apache Falcon Commons .. FAILURE [02:34
> min]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-1610) Add instance commands to Falcon spring-shell CLI
[ https://issues.apache.org/jira/browse/FALCON-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-1610: Fix Version/s: 0.11 > Add instance commands to Falcon spring-shell CLI > > > Key: FALCON-1610 > URL: https://issues.apache.org/jira/browse/FALCON-1610 > Project: Falcon > Issue Type: Sub-task >Reporter: Rajat Khandelwal >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2143) Documentation of BacklogEmitter Service
[ https://issues.apache.org/jira/browse/FALCON-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2143: Fix Version/s: 0.11 > Documentation of BacklogEmitter Service > --- > > Key: FALCON-2143 > URL: https://issues.apache.org/jira/browse/FALCON-2143 > Project: Falcon > Issue Type: Task >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > The code for Backlog emitter service has already been pushed to trunk but > documentation for the service is missing. > Creating this jira to track it. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2218) Add a profile for lgpl
[ https://issues.apache.org/jira/browse/FALCON-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2218: Fix Version/s: 0.11 trunk > Add a profile for lgpl > --- > > Key: FALCON-2218 > URL: https://issues.apache.org/jira/browse/FALCON-2218 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > This jira is to make a separate profile for including jars which are under > LGPL licenses. > Currently, we need to add mysql jar in prism and server. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2221) Submitting an existing job fails with MySQLIntegrityConstraintViolationException
[
https://issues.apache.org/jira/browse/FALCON-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2221:
Fix Version/s: 0.11
trunk
> Submitting an existing job fails with
> MySQLIntegrityConstraintViolationException
>
>
> Key: FALCON-2221
> URL: https://issues.apache.org/jira/browse/FALCON-2221
> Project: Falcon
> Issue Type: Bug
> Components: extensions
>Affects Versions: trunk
>Reporter: Pragya Mittal
>Assignee: Pracheer Agarwal
>Priority: Minor
> Fix For: trunk, 0.11
>
>
> Submitting an already existing job should succeed saying 'Job already
> submitted' (as is the case with process submission). Instead it throws the
> followinf error :
> {noformat}
> dataqa@falcon1001:~$ falcon extension -submit -jobName sample -file abc
> -extensionName extension-example
> Dec 15, 2016 7:15:31 AM com.sun.jersey.api.client.ClientResponse getEntity
> SEVERE: A message body reader for Java class
> org.apache.falcon.resource.APIResult, and Java type class
> org.apache.falcon.resource.APIResult, and MIME media type text/html;
> charset=iso-8859-1 was not found
> Dec 15, 2016 7:15:31 AM com.sun.jersey.api.client.ClientResponse getEntity
> SEVERE: The registered message body readers compatible with the MIME media
> type are:
> */* ->
> com.sun.jersey.core.impl.provider.entity.FormProvider
> com.sun.jersey.core.impl.provider.entity.MimeMultipartProvider
> com.sun.jersey.core.impl.provider.entity.StringProvider
> com.sun.jersey.core.impl.provider.entity.ByteArrayProvider
> com.sun.jersey.core.impl.provider.entity.FileProvider
> com.sun.jersey.core.impl.provider.entity.InputStreamProvider
> com.sun.jersey.core.impl.provider.entity.DataSourceProvider
> com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General
> com.sun.jersey.core.impl.provider.entity.ReaderProvider
> com.sun.jersey.core.impl.provider.entity.DocumentProvider
> com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader
> com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader
> com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader
> com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General
> com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General
> com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General
> com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General
> com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General
> com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General
> com.sun.jersey.core.impl.provider.entity.EntityHolderReader
> com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General
> com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General
> com.sun.jersey.json.impl.provider.entity.JacksonProviderProxy
> ERROR: Internal Server Error;
>
>
> Error 500 The transaction has been rolled back. See the nested
> exceptions for details on the errors that occurred.
>
> HTTP ERROR 500
> Problem accessing /api/extension/submit/extension-example. Reason:
> The transaction has been rolled back. See the nested exceptions for
> details on the errors that occurred.Caused
> by:openjpa-2.4.0-r422266:1674604 fatal store error
> org.apache.openjpa.persistence.RollbackException: The transaction has been
> rolled back. See the nested exceptions for details on the errors that
> occurred.
> FailedObject: org.apache.falcon.persistence.ExtensionJobsBean@24f6b1a0
> at
> org.apache.openjpa.persistence.EntityManagerImpl.commit(EntityManagerImpl.java:593)
> at
> org.apache.falcon.extensions.jdbc.ExtensionMetaStore.commitAndCloseTransaction(ExtensionMetaStore.java:175)
> at
> org.apache.falcon.extensions.jdbc.ExtensionMetaStore.storeExtensionJob(ExtensionMetaStore.java:141)
> at
> org.apache.falcon.resource.extensions.ExtensionManager.submitEntities(ExtensionManager.java:433)
> at
> org.apache.falcon.resource.extensions.ExtensionManager.submit(ExtensionManager.java:318)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at
>
[jira] [Updated] (FALCON-2269) Extension api fails via server in distributed mode
[
https://issues.apache.org/jira/browse/FALCON-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2269:
Fix Version/s: 0.11
trunk
> Extension api fails via server in distributed mode
> --
>
> Key: FALCON-2269
> URL: https://issues.apache.org/jira/browse/FALCON-2269
> Project: Falcon
> Issue Type: Bug
> Components: extensions
>Affects Versions: trunk
>Reporter: Pragya Mittal
>Assignee: Pracheer Agarwal
> Fix For: trunk, 0.11
>
>
> Except register/unregister/submit extensions all the apis should work via
> server in distributed mode. This is failing with the following error :
> {noformat}
> pragya.mittal@falcon1001:/mnt/falcon/server/bin$ ./falcon extension -list
> -extensionName extension-example -orderby asc
> Jan 31, 2017 7:37:46 AM com.sun.jersey.api.client.ClientResponse getEntity
> SEVERE: A message body reader for Java class
> org.apache.falcon.resource.APIResult, and Java type class
> org.apache.falcon.resource.APIResult, and MIME media type text/html;
> charset=iso-8859-1 was not found
> Jan 31, 2017 7:37:46 AM com.sun.jersey.api.client.ClientResponse getEntity
> SEVERE: The registered message body readers compatible with the MIME media
> type are:
> */* ->
> com.sun.jersey.core.impl.provider.entity.FormProvider
> com.sun.jersey.core.impl.provider.entity.MimeMultipartProvider
> com.sun.jersey.core.impl.provider.entity.StringProvider
> com.sun.jersey.core.impl.provider.entity.ByteArrayProvider
> com.sun.jersey.core.impl.provider.entity.FileProvider
> com.sun.jersey.core.impl.provider.entity.InputStreamProvider
> com.sun.jersey.core.impl.provider.entity.DataSourceProvider
> com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General
> com.sun.jersey.core.impl.provider.entity.ReaderProvider
> com.sun.jersey.core.impl.provider.entity.DocumentProvider
> com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader
> com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader
> com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader
> com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General
> com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General
> com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General
> com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General
> com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General
> com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General
> com.sun.jersey.core.impl.provider.entity.EntityHolderReader
> com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General
> com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General
> com.sun.jersey.json.impl.provider.entity.JacksonProviderProxy
> ERROR: Not Found;
>
>
> Error 404 Not Found
>
> HTTP ERROR 404
> Problem accessing /api/extension/list/extension-example. Reason:
> Not FoundPowered by
> Jetty://
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2227) Intitutive error handling in Falcon Client
[
https://issues.apache.org/jira/browse/FALCON-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2227:
Fix Version/s: 0.11
> Intitutive error handling in Falcon Client
> ---
>
> Key: FALCON-2227
> URL: https://issues.apache.org/jira/browse/FALCON-2227
> Project: Falcon
> Issue Type: Sub-task
> Components: extensions
>Reporter: Praveen Adlakha
>Assignee: sandeep samudrala
> Fix For: trunk, 0.11
>
>
> In submitting extensions we are catching some error and not throwing it:
> {code}
> catch (Exception e) {
> OUT.get().println("Error in building the extension");
> throw new FalconCLIException("Failed to prepare entities for
> the given extension");
> }
> if (entities == null || entities.isEmpty()) {
> OUT.get().println("No entities got built");
> throw new FalconCLIException("Failed to prepare entities for
> the given extension");
> }
> {code}
> Its pretty intuitive to know the error.Please wrap the exception.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2216) Recipe job submission api is non intutive
[
https://issues.apache.org/jira/browse/FALCON-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2216:
Fix Version/s: 0.11
trunk
> Recipe job submission api is non intutive
> -
>
> Key: FALCON-2216
> URL: https://issues.apache.org/jira/browse/FALCON-2216
> Project: Falcon
> Issue Type: Task
> Components: extensions
>Affects Versions: trunk
>Reporter: Pragya Mittal
> Fix For: trunk, 0.11
>
>
> Currently the api to submit job is following :
> {noformat}
> http://localhost:16000/api/options?user.name=dataqa
> {noformat}
> Please modify it to a more intutive path.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2223) Distributed mode support for User Extension
[ https://issues.apache.org/jira/browse/FALCON-2223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2223: Fix Version/s: 0.11 trunk > Distributed mode support for User Extension > --- > > Key: FALCON-2223 > URL: https://issues.apache.org/jira/browse/FALCON-2223 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > This issue is to track distributed mode support for user extension.In this > jira I will be making changes for: > register > unregister > detail > describe API. > as these are logically grouped together which will be running on prism only. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2209) Registering user extensions in embedded/distributed mode
[ https://issues.apache.org/jira/browse/FALCON-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2209: Fix Version/s: 0.11 trunk > Registering user extensions in embedded/distributed mode > > > Key: FALCON-2209 > URL: https://issues.apache.org/jira/browse/FALCON-2209 > Project: Falcon > Issue Type: Sub-task > Components: extensions, prism >Reporter: sandeep samudrala >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Extensions information is stored in DB and so Prism needs to have acess to DB > and also start extension service in the prism. As part of the same, prism > needs to start Falcon JPA service and Extension Service -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2096) Feed instance listing doesn't give instance status of all the clusters.
[ https://issues.apache.org/jira/browse/FALCON-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2096: Fix Version/s: 0.11 > Feed instance listing doesn't give instance status of all the clusters. > --- > > Key: FALCON-2096 > URL: https://issues.apache.org/jira/browse/FALCON-2096 > Project: Falcon > Issue Type: Bug > Components: common >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Currently when feed instance listing is being called, it shows the instance > listing of only 1 cluster. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2261) Job submission fails with IllegalArgumentException
[
https://issues.apache.org/jira/browse/FALCON-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2261:
Fix Version/s: 0.11
> Job submission fails with IllegalArgumentException
> --
>
> Key: FALCON-2261
> URL: https://issues.apache.org/jira/browse/FALCON-2261
> Project: Falcon
> Issue Type: Bug
> Components: extensions
>Affects Versions: trunk
>Reporter: Pragya Mittal
>Assignee: sandeep samudrala
> Fix For: trunk, 0.11
>
>
> I tried registering and submitting jobs via webhdfs and got the following
> error :
> {noformat}
> pragya.mittal@falcon1001:~$ falcon extension -register -extensionName
> example-1 -path
> webhdfs://192.168.138.236:14000/tmp/extensions/extension-example
> Extension :example-1 registered successfully.
> pragya.mittal@falcon1001:~$ falcon extension -submitAndSchedule
> -extensionName example-1 -jobName job-instance1 -file abc
> Error in building the extension:java.lang.IllegalArgumentException: Wrong FS:
> webhdfs://192.168.138.236:14000/tmp/extensions/extension-example/libs/build,
> expected: hdfs://192.168.138.236:8020
> at org.apache.hadoop.fs.FileSystem.checkPath(FileSystem.java:645)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.getPathName(DistributedFileSystem.java:193)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.access$000(DistributedFileSystem.java:105)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$18.doCall(DistributedFileSystem.java:1118)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$18.doCall(DistributedFileSystem.java:1114)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.getFileStatus(DistributedFileSystem.java:1114)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:337)
> at org.apache.hadoop.fs.FileUtil.copy(FileUtil.java:289)
> at org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1970)
> at org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1939)
> at org.apache.hadoop.fs.FileSystem.copyToLocalFile(FileSystem.java:1915)
> at
> org.apache.falcon.ExtensionHandler.copyExtensionPackage(ExtensionHandler.java:163)
> at
> org.apache.falcon.ExtensionHandler.loadAndPrepare(ExtensionHandler.java:102)
> at
> org.apache.falcon.client.FalconClient.getEntities(FalconClient.java:1164)
> at
> org.apache.falcon.client.FalconClient.validateExtensionAndGetEntities(FalconClient.java:1130)
> at
> org.apache.falcon.client.FalconClient.getEntitiesForm(FalconClient.java:1099)
> at
> org.apache.falcon.client.FalconClient.submitAndScheduleExtensionJob(FalconClient.java:1180)
> at
> org.apache.falcon.cli.FalconExtensionCLI.extensionCommand(FalconExtensionCLI.java:127)
> at org.apache.falcon.cli.FalconCLI.run(FalconCLI.java:128)
> at org.apache.falcon.cli.FalconCLI.main(FalconCLI.java:62)
> ERROR: Error in building the extension:Wrong FS:
> webhdfs://192.168.138.236:14000/tmp/extensions/extension-example/libs/build,
> expected: hdfs://192.168.138.236:8020
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2006) Update documentation on site and announce the release
[ https://issues.apache.org/jira/browse/FALCON-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2006: Fix Version/s: (was: 0.10) 0.11 trunk > Update documentation on site and announce the release > - > > Key: FALCON-2006 > URL: https://issues.apache.org/jira/browse/FALCON-2006 > Project: Falcon > Issue Type: Sub-task > Components: ease >Reporter: Balu Vellanki >Assignee: Balu Vellanki > Fix For: trunk, 0.11 > > > * Update the documentation on site. > * Announce the release. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2235) Suspend/Resume API support for extension job (user extension)
[ https://issues.apache.org/jira/browse/FALCON-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2235: Fix Version/s: 0.11 > Suspend/Resume API support for extension job (user extension) > - > > Key: FALCON-2235 > URL: https://issues.apache.org/jira/browse/FALCON-2235 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > This will add the suspend/resume api functionality to user extensions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2231) Support Schedule for User Extensions
[ https://issues.apache.org/jira/browse/FALCON-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2231: Fix Version/s: 0.11 trunk > Support Schedule for User Extensions > > > Key: FALCON-2231 > URL: https://issues.apache.org/jira/browse/FALCON-2231 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Falcon Client and Falcon Server changes for supporting Schedule on User > Extensions -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2110) Glyphicon license for Falcon
[ https://issues.apache.org/jira/browse/FALCON-2110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2110: Fix Version/s: 0.11 > Glyphicon license for Falcon > > > Key: FALCON-2110 > URL: https://issues.apache.org/jira/browse/FALCON-2110 > Project: Falcon > Issue Type: Task > Components: license >Reporter: Srikanth Sundarrajan >Assignee: Srikanth Sundarrajan >Priority: Trivial > Fix For: trunk, 0.11 > > > Glyphicon free, which is licensed under Creative Commons Attribution 3.0 > Unported (CC BY 3.0) doesn't include halflings used by falcon. However > explicit persmission has been granted for use under same license as > bootstrap, when used from within bootstrap. > Recording this here for future reference. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2127) Fix the falcon regression compilation issue and delete the deprecated recipe test cases
[ https://issues.apache.org/jira/browse/FALCON-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2127: Fix Version/s: 0.11 > Fix the falcon regression compilation issue and delete the deprecated recipe > test cases > --- > > Key: FALCON-2127 > URL: https://issues.apache.org/jira/browse/FALCON-2127 > Project: Falcon > Issue Type: Bug > Components: merlin >Affects Versions: trunk >Reporter: Murali Ramasami >Assignee: Murali Ramasami >Priority: Critical > Fix For: trunk, 0.11 > > > Currently falcon regression compilation is failing because of FalconCLI is > removed and FalconCLI is used on all the recipe test cases. Also recipe tests > cases are no longer valid due to the extension support deleting the > deprecated recipe test cases also. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2003) Check licenses and copyright information
[ https://issues.apache.org/jira/browse/FALCON-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2003: Fix Version/s: (was: 0.10) 0.11 trunk > Check licenses and copyright information > > > Key: FALCON-2003 > URL: https://issues.apache.org/jira/browse/FALCON-2003 > Project: Falcon > Issue Type: Sub-task > Components: docs >Affects Versions: 0.9 >Reporter: Balu Vellanki >Assignee: Balu Vellanki > Fix For: trunk, 0.11 > > > Update the license text with the copyright info. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2185) Falcon Client changes for Falcon user extensions
[ https://issues.apache.org/jira/browse/FALCON-2185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2185: Fix Version/s: 0.11 > Falcon Client changes for Falcon user extensions > > > Key: FALCON-2185 > URL: https://issues.apache.org/jira/browse/FALCON-2185 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > The new user extensions can be submitted by falcon client and the all the > prepare and build work is done by the falcon client. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2142) Close stale pull requests
[ https://issues.apache.org/jira/browse/FALCON-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2142: Fix Version/s: (was: 1.0) 0.11 trunk > Close stale pull requests > - > > Key: FALCON-2142 > URL: https://issues.apache.org/jira/browse/FALCON-2142 > Project: Falcon > Issue Type: Task >Reporter: Ajay Yadava >Assignee: Ajay Yadava > Fix For: trunk, 0.11 > > > Several pull requests have changes which are already merged / not required or > need some work but have been lying unresponsive for quite some time, despite > reminders. The list of these pull requests is as below: > https://github.com/apache/falcon/pull/3 > https://github.com/apache/falcon/pull/4 > https://github.com/apache/falcon/pull/5 > https://github.com/apache/falcon/pull/7 > https://github.com/apache/falcon/pull/10 > https://github.com/apache/falcon/pull/26 > https://github.com/apache/falcon/pull/32 > https://github.com/apache/falcon/pull/33 > https://github.com/apache/falcon/pull/34 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-1780) Add falcon-cli executable and link that to falcon executable when no arguments are provided
[ https://issues.apache.org/jira/browse/FALCON-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-1780: Fix Version/s: 0.11 > Add falcon-cli executable and link that to falcon executable when no > arguments are provided > --- > > Key: FALCON-1780 > URL: https://issues.apache.org/jira/browse/FALCON-1780 > Project: Falcon > Issue Type: Sub-task >Reporter: Rajat Khandelwal >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2077) Api support for Process SLA
[ https://issues.apache.org/jira/browse/FALCON-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2077: Fix Version/s: 0.11 > Api support for Process SLA > > > Key: FALCON-2077 > URL: https://issues.apache.org/jira/browse/FALCON-2077 > Project: Falcon > Issue Type: Improvement >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > Right now API only supports feed sla monitoring code for process SLA is > already checked in need to extend the api to support process also. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2210) Server side changes for submit and submitAndSchedule for user extensions
[ https://issues.apache.org/jira/browse/FALCON-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2210: Fix Version/s: 0.11 trunk > Server side changes for submit and submitAndSchedule for user extensions > > > Key: FALCON-2210 > URL: https://issues.apache.org/jira/browse/FALCON-2210 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2171) When feed from multiple colos are replicated, the colo folders get overwritten
[ https://issues.apache.org/jira/browse/FALCON-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2171: Fix Version/s: 0.11 > When feed from multiple colos are replicated, the colo folders get overwritten > -- > > Key: FALCON-2171 > URL: https://issues.apache.org/jira/browse/FALCON-2171 > Project: Falcon > Issue Type: Bug >Reporter: Pallavi Rao >Assignee: Pallavi Rao > Fix For: trunk, 0.11 > > > Regression caused by FALCON-1844. > Work around as discussed is to add the following property to the feed > definition: > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2233) Make changes in falcon unit to enable/disable extensions
[ https://issues.apache.org/jira/browse/FALCON-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2233: Fix Version/s: 0.11 > Make changes in falcon unit to enable/disable extensions > > > Key: FALCON-2233 > URL: https://issues.apache.org/jira/browse/FALCON-2233 > Project: Falcon > Issue Type: Sub-task > Components: falcon-unit >Reporter: Pracheer Agarwal >Assignee: Pracheer Agarwal > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2266) Non-intuitive response while registering/unregistering/submitting extension via server
[
https://issues.apache.org/jira/browse/FALCON-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2266:
Fix Version/s: 0.11
> Non-intuitive response while registering/unregistering/submitting extension
> via server
> --
>
> Key: FALCON-2266
> URL: https://issues.apache.org/jira/browse/FALCON-2266
> Project: Falcon
> Issue Type: Bug
> Components: extensions
>Affects Versions: trunk
>Reporter: Pragya Mittal
>Assignee: Pracheer Agarwal
> Fix For: trunk, 0.11
>
>
> Registering extension via server throws the following error
> {noformat}
> pragya.mittal@falcon1001:/mnt/falcon/server/bin$ ./falcon extension -register
> -extensionName extension-example-1 -path
> hdfs://192.168.138.236:8020/tmp/extensions/extension-example
> Hadoop is installed, adding hadoop classpath to falcon classpath
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/mnt/falcon/server/client/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/usr/hdp/2.2.4.2-2/hadoop/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> Jan 31, 2017 7:12:57 AM com.sun.jersey.api.client.ClientResponse getEntity
> SEVERE: A message body reader for Java class
> org.apache.falcon.resource.APIResult, and Java type class
> org.apache.falcon.resource.APIResult, and MIME media type text/html;
> charset=iso-8859-1 was not found
> Jan 31, 2017 7:12:57 AM com.sun.jersey.api.client.ClientResponse getEntity
> SEVERE: The registered message body readers compatible with the MIME media
> type are:
> */* ->
> com.sun.jersey.core.impl.provider.entity.FormProvider
> com.sun.jersey.core.impl.provider.entity.MimeMultipartProvider
> com.sun.jersey.core.impl.provider.entity.StringProvider
> com.sun.jersey.core.impl.provider.entity.ByteArrayProvider
> com.sun.jersey.core.impl.provider.entity.FileProvider
> com.sun.jersey.core.impl.provider.entity.InputStreamProvider
> com.sun.jersey.core.impl.provider.entity.DataSourceProvider
> com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General
> com.sun.jersey.core.impl.provider.entity.ReaderProvider
> com.sun.jersey.core.impl.provider.entity.DocumentProvider
> com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader
> com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader
> com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader
> com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General
> com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General
> com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General
> com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General
> com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General
> com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General
> com.sun.jersey.core.impl.provider.entity.EntityHolderReader
> com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General
> com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General
> com.sun.jersey.json.impl.provider.entity.JacksonProviderProxy
> ERROR: Not Found;
>
>
> Error 404 Not Found
>
> HTTP ERROR 404
> Problem accessing /api/extension/register/extension-example-1. Reason:
> Not FoundPowered by
> Jetty://
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> {noformat}
> It should say operation not permitted instead of showing the full stack trace
> which is non intuitive in nature.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2156) Logmover listener gets stuck while listening to WorkflowJobEndNotificationService
[ https://issues.apache.org/jira/browse/FALCON-2156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2156: Fix Version/s: 0.11 trunk > Logmover listener gets stuck while listening to > WorkflowJobEndNotificationService > - > > Key: FALCON-2156 > URL: https://issues.apache.org/jira/browse/FALCON-2156 > Project: Falcon > Issue Type: Sub-task > Components: messaging >Affects Versions: trunk >Reporter: Pragya Mittal >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > On enabling LogMover service, log mover listener attains deadlock and gets > stuck at the first SUCCEEDED message received via > WorkflowJobEndNotificationService. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2181) Support for storing metadata of non trusted recipe
[ https://issues.apache.org/jira/browse/FALCON-2181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2181: Fix Version/s: 0.11 > Support for storing metadata of non trusted recipe > --- > > Key: FALCON-2181 > URL: https://issues.apache.org/jira/browse/FALCON-2181 > Project: Falcon > Issue Type: Sub-task >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > We are planning to add support of non trusted recipe in falcon.Will be adding > the metadata in the database. > Will add more details with schema etc in comments. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2184) Support to delete a non trusted recipe metadata from server
[ https://issues.apache.org/jira/browse/FALCON-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2184: Fix Version/s: 0.11 > Support to delete a non trusted recipe metadata from server > --- > > Key: FALCON-2184 > URL: https://issues.apache.org/jira/browse/FALCON-2184 > Project: Falcon > Issue Type: Sub-task >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > As suggested in Falcon 2181 we will be cooking non trusted recipes on the > client. > We need to register and delete metadata from the server.In this jira will be > adding rest api and client support for deletion of the jira. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2128) Status api shows timeout instances as failed
[ https://issues.apache.org/jira/browse/FALCON-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2128: Fix Version/s: 0.11 > Status api shows timeout instances as failed > > > Key: FALCON-2128 > URL: https://issues.apache.org/jira/browse/FALCON-2128 > Project: Falcon > Issue Type: Bug > Components: prism >Affects Versions: trunk, 0.10 >Reporter: Pragya Mittal >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > If instances timedout falcon status api shows the status as FAILED. In my > opinion we should differentiate FAILED instances from TIMEDOUT instances for > better user understanding. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2230) Extension API failure after APIResult changes
[ https://issues.apache.org/jira/browse/FALCON-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2230: Fix Version/s: 0.11 trunk > Extension API failure after APIResult changes > - > > Key: FALCON-2230 > URL: https://issues.apache.org/jira/browse/FALCON-2230 > Project: Falcon > Issue Type: Bug >Reporter: Pracheer Agarwal >Assignee: Pracheer Agarwal > Fix For: trunk, 0.11 > > > Extension API failure after APIResult changes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2232) Check for null feeds in getFeeds() in ExtensionBean
[ https://issues.apache.org/jira/browse/FALCON-2232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2232: Fix Version/s: 0.11 trunk > Check for null feeds in getFeeds() in ExtensionBean > --- > > Key: FALCON-2232 > URL: https://issues.apache.org/jira/browse/FALCON-2232 > Project: Falcon > Issue Type: Bug > Components: extensions >Reporter: Pracheer Agarwal >Assignee: Pracheer Agarwal > Fix For: trunk, 0.11 > > > When we are returning feeds for an extension job, it is being returned as an > array Arrays.asList(feeds). Array.asList throws NPE if feeds argument is null. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2240) Enable/disable feature is broken
[
https://issues.apache.org/jira/browse/FALCON-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2240:
Fix Version/s: 0.11
> Enable/disable feature is broken
>
>
> Key: FALCON-2240
> URL: https://issues.apache.org/jira/browse/FALCON-2240
> Project: Falcon
> Issue Type: Bug
> Components: extensions
>Affects Versions: trunk
>Reporter: Pragya Mittal
>Assignee: Pracheer Agarwal
> Fix For: trunk, 0.11
>
>
> Enable :
> {noformat}
> dataqa@falcon1001:~$ falcon extension -enable -extensionName extension-example
> ERROR: Invalid/missing extension command. Supported commands include
> enumerate, definition, describe, list, instances, submit, submitAndSchedule,
> schedule, suspend, resume, delete, update, validate, enable, disable. Please
> refer to Falcon CLI twiki for more details.
> {noformat}
> Disable :
> {noformat}
> dataqa@falcon1001:~$ falcon extension -disable extension-example
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> ERROR: Invalid/missing extension command. Supported commands include
> enumerate, definition, describe, list, instances, submit, submitAndSchedule,
> schedule, suspend, resume, delete, update, validate, enable, disable. Please
> refer to Falcon CLI twiki for more details.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2159) Update document for adding BackLogEmitterService
[
https://issues.apache.org/jira/browse/FALCON-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2159:
Fix Version/s: 0.11
trunk
> Update document for adding BackLogEmitterService
>
>
> Key: FALCON-2159
> URL: https://issues.apache.org/jira/browse/FALCON-2159
> Project: Falcon
> Issue Type: Sub-task
> Components: prism
>Affects Versions: trunk
>Reporter: Pragya Mittal
>Assignee: Praveen Adlakha
> Fix For: trunk, 0.11
>
>
> The following configuration is missing from startup.properties
> {noformat}
> *.workflow.execution.listeners=org.apache.falcon.handler.SLAMonitoringHandler,\
>
> org.apache.falcon.service.BacklogMetricEmitterService
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2190) Add server side checks to not let any entity mutations on entities generated by extensions
[ https://issues.apache.org/jira/browse/FALCON-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2190: Fix Version/s: 0.11 > Add server side checks to not let any entity mutations on entities generated > by extensions > -- > > Key: FALCON-2190 > URL: https://issues.apache.org/jira/browse/FALCON-2190 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Entities generated by the extension should be locked down for any mutations > directly. Mutations should happen only via Extension commands/calls(extension > update,submit,delete). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2207) Only the owner of the extension, should be able to unregister, disable, enable.
[ https://issues.apache.org/jira/browse/FALCON-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2207: Fix Version/s: 0.11 > Only the owner of the extension, should be able to unregister, disable, > enable. > --- > > Key: FALCON-2207 > URL: https://issues.apache.org/jira/browse/FALCON-2207 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: Pallavi Rao >Assignee: Pracheer Agarwal > Fix For: trunk, 0.11 > > > It is possible that owner of extension's hdfs location and the user who is > registering that extension might be different. > There is a need to capture the owner of the extension (the user who > registered it) and not allow other users to operate (unregister, enable, > disable) on the same. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2120) falcon-regression build is failing because of CLI and hive changes
[
https://issues.apache.org/jira/browse/FALCON-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2120:
Fix Version/s: 0.11
trunk
> falcon-regression build is failing because of CLI and hive changes
> --
>
> Key: FALCON-2120
> URL: https://issues.apache.org/jira/browse/FALCON-2120
> Project: Falcon
> Issue Type: Bug
>Reporter: Praveen Adlakha
>Assignee: Praveen Adlakha
> Fix For: trunk, 0.11
>
>
> Hi All,
> Regression build is failing with two errors :
> {code}
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Falcon Regression ... SUCCESS [ 0.369
> s]
> [INFO] Apache Falcon Regression Suite Core FAILURE [ 0.343
> s]
> [INFO] Apache Falcon Regression Suite . SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 1.082 s
> [INFO] Finished at: 2016-08-23T12:51:39+05:30
> [INFO] Final Memory: 21M/303M
> [INFO]
>
> [ERROR] Failed to execute goal on project falcon-merlin-core: Could not
> resolve dependencies for project
> org.apache.falcon.regression:falcon-merlin-core:jar:0.11-SNAPSHOT: Failure to
> find org.pentaho:pentaho-aggdesigner-algorithm:jar:5.1.5-jhyde in
> http://repo1.maven.org/maven2 was cached in the local repository, resolution
> will not be reattempted until the update interval of central has elapsed or
> updates are forced -> [Help 1]
> [ERROR]
> {code}
> Second:
> {code}
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Falcon Regression ... SUCCESS [ 1.964
> s]
> [INFO] Apache Falcon Regression Suite Core FAILURE [ 3.604
> s]
> [INFO] Apache Falcon Regression Suite . SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 5.732 s
> [INFO] Finished at: 2016-08-23T12:56:16+05:30
> [INFO] Final Memory: 63M/799M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
> (default-compile) on project falcon-merlin-core: Compilation failure:
> Compilation failure:
> [ERROR]
> /home/praveen/git/myfalcon/falcon/falcon-regression/merlin-core/src/main/java/org/apache/falcon/regression/core/bundle/Bundle.java:[22,28]
> error: package org.apache.falcon.cli does not exist
> [ERROR]
> /home/praveen/git/myfalcon/falcon/falcon-regression/merlin-core/src/main/java/org/apache/falcon/regression/Entities/RecipeMerlin.java:[29,28]
> error: package org.apache.falcon.cli does not exist
> [ERROR]
> /home/praveen/git/myfalcon/falcon/falcon-regression/merlin-core/src/main/java/org/apache/falcon/regression/Entities/RecipeMerlin.java:[79,20]
> error: package FalconCLI does not exist
> [ERROR]
> /home/praveen/git/myfalcon/falcon/falcon-regression/merlin-core/src/main/java/org/apache/falcon/regression/Entities/RecipeMerlin.java:[83,21]
> error: package FalconCLI does not exist
> [ERROR]
> /home/praveen/git/myfalcon/falcon/falcon-regression/merlin-core/src/main/java/org/apache/falcon/regression/Entities/RecipeMerlin.java:[243,52]
> error: package FalconCLI does not exist
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2047) HiveDR tests are failed due to data-mirroring does not have correct ownership/permissions
[
https://issues.apache.org/jira/browse/FALCON-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2047:
Fix Version/s: 0.11
> HiveDR tests are failed due to data-mirroring does not have correct
> ownership/permissions
> -
>
> Key: FALCON-2047
> URL: https://issues.apache.org/jira/browse/FALCON-2047
> Project: Falcon
> Issue Type: Bug
> Components: replication
>Affects Versions: 0.10
>Reporter: Murali Ramasami
>Assignee: Sowmya Ramesh
>Priority: Critical
> Fix For: trunk, 0.11
>
>
> When I executed the hiveDR cases in unsecure cluster it is failed because of
> /apps/data-mirroring does not have correct ownership/permissions. Please see
> the error message below:
> {noformat}
> LogType:stderr
> Log Upload Time:Tue Jun 21 21:02:06 + 2016
> LogLength:860
> Log Contents:
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/grid/0/hadoop/yarn/local/filecache/317/slf4j-log4j12-1.6.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/grid/0/hadoop/yarn/local/filecache/39/mapreduce.tar.gz/hadoop/share/hadoop/common/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> Invalid arguments: Base dir
> hdfs://mramasami-falcon-multicluster-10.openstacklocal:8020/apps/data-mirroring
> does not have correct ownership/permissions. Please set group to users and
> permissions to rwxrwx---
> Intercepting System.exit(-1)
> Failing Oozie Launcher, Main class [org.apache.oozie.action.hadoop.JavaMain],
> exit code [-1]
> End of LogType:stderr
> LogType:stdout
> Log Upload Time:Tue Jun 21 21:02:06 + 2016
> LogLength:192002
> Log Contents:
> Oozie Launcher starts
> {noformat}
> Permission :
> {noformat}
> hrt_qa@mramasami-falcon-multicluster-13:/grid/0/hadoopqe/tests/falcon/falcon-regression/falcon-regression/merlin/target/surefire-reports$
> hdfs dfs -ls /apps/
> Found 3 items
> drwxrwxrwx - falcon hdfs 0 2016-06-21 19:04 /apps/data-mirroring
> drwxrwxrwx - falcon hdfs 0 2016-06-21 19:04 /apps/falcon
> drwxr-xr-x - hdfs hdfs 0 2016-06-21 19:07 /apps/hive
> {noformat}
> So /apps/data-mirroring contains full permission but it expects 770.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2201) Falcon Unit changes to support extensions
[ https://issues.apache.org/jira/browse/FALCON-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2201: Fix Version/s: 0.11 > Falcon Unit changes to support extensions > -- > > Key: FALCON-2201 > URL: https://issues.apache.org/jira/browse/FALCON-2201 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Falcon Unit needs to enhanced to accommodate extensions and also validate > user extensions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2271) Scheduling non existing job fails with non intuitive response
[
https://issues.apache.org/jira/browse/FALCON-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2271:
Fix Version/s: 0.11
> Scheduling non existing job fails with non intuitive response
> -
>
> Key: FALCON-2271
> URL: https://issues.apache.org/jira/browse/FALCON-2271
> Project: Falcon
> Issue Type: Bug
> Components: extensions
>Affects Versions: trunk
>Reporter: Pragya Mittal
>Assignee: sandeep samudrala
> Fix For: trunk, 0.11
>
>
> {noformat}
> pragya.mittal@falcon1001:~$ falcon extension -list -extensionName
> extension-example
> 5
> sample1 extension-example
> sample5 extension-example
> sample4 extension-example
> sample3 extension-example
> sample2 extension-example
> {noformat}
> sample6 job does not exist.
> {noformat}
> pragya.mittal@falcon1001:~$ falcon extension -schedule -jobName sample6
> Hadoop is installed, adding hadoop classpath to falcon classpath
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/mnt/falcon/prism/client/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/usr/hdp/2.2.4.2-2/hadoop/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> Jan 31, 2017 8:39:23 AM com.sun.jersey.api.client.ClientResponse getEntity
> SEVERE: A message body reader for Java class
> org.apache.falcon.resource.APIResult, and Java type class
> org.apache.falcon.resource.APIResult, and MIME media type text/html;
> charset=iso-8859-1 was not found
> Jan 31, 2017 8:39:23 AM com.sun.jersey.api.client.ClientResponse getEntity
> SEVERE: The registered message body readers compatible with the MIME media
> type are:
> */* ->
> com.sun.jersey.core.impl.provider.entity.FormProvider
> com.sun.jersey.core.impl.provider.entity.MimeMultipartProvider
> com.sun.jersey.core.impl.provider.entity.StringProvider
> com.sun.jersey.core.impl.provider.entity.ByteArrayProvider
> com.sun.jersey.core.impl.provider.entity.FileProvider
> com.sun.jersey.core.impl.provider.entity.InputStreamProvider
> com.sun.jersey.core.impl.provider.entity.DataSourceProvider
> com.sun.jersey.core.impl.provider.entity.XMLJAXBElementProvider$General
> com.sun.jersey.core.impl.provider.entity.ReaderProvider
> com.sun.jersey.core.impl.provider.entity.DocumentProvider
> com.sun.jersey.core.impl.provider.entity.SourceProvider$StreamSourceReader
> com.sun.jersey.core.impl.provider.entity.SourceProvider$SAXSourceReader
> com.sun.jersey.core.impl.provider.entity.SourceProvider$DOMSourceReader
> com.sun.jersey.json.impl.provider.entity.JSONJAXBElementProvider$General
> com.sun.jersey.json.impl.provider.entity.JSONArrayProvider$General
> com.sun.jersey.json.impl.provider.entity.JSONObjectProvider$General
> com.sun.jersey.core.impl.provider.entity.XMLRootElementProvider$General
> com.sun.jersey.core.impl.provider.entity.XMLListElementProvider$General
> com.sun.jersey.core.impl.provider.entity.XMLRootObjectProvider$General
> com.sun.jersey.core.impl.provider.entity.EntityHolderReader
> com.sun.jersey.json.impl.provider.entity.JSONRootElementProvider$General
> com.sun.jersey.json.impl.provider.entity.JSONListElementProvider$General
> com.sun.jersey.json.impl.provider.entity.JacksonProviderProxy
> ERROR: Internal Server Error;
>
>
> Error 500 INTERNAL_SERVER_ERROR
>
> HTTP ERROR 500
> Problem accessing /api/extension/schedule/sample6. Reason:
> INTERNAL_SERVER_ERRORCaused
> by:java.lang.NullPointerException
> at
> org.apache.falcon.resource.proxy.ExtensionManagerProxy.schedule(ExtensionManagerProxy.java:160)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
> at
> com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
> at
> com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
> at
> com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)
> at
>
[jira] [Updated] (FALCON-2260) Enhance extension List api to support for user extensions
[ https://issues.apache.org/jira/browse/FALCON-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2260: Fix Version/s: 0.11 > Enhance extension List api to support for user extensions > - > > Key: FALCON-2260 > URL: https://issues.apache.org/jira/browse/FALCON-2260 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Enhance extension List api to support for user extensions. As of now list > supports only for TRUSTED extensions. List of an extension will have to give > all the instantiations of the extension. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-1015) Falcon instance kill operation doesn't kill instances in waiting
[ https://issues.apache.org/jira/browse/FALCON-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-1015: Fix Version/s: 0.11 trunk > Falcon instance kill operation doesn't kill instances in waiting > - > > Key: FALCON-1015 > URL: https://issues.apache.org/jira/browse/FALCON-1015 > Project: Falcon > Issue Type: Improvement > Components: process >Affects Versions: trunk > Environment: QA >Reporter: Karishma Gulati > Fix For: trunk, 0.11 > > > Instances that are in waiting continue to remain in waiting when Instance > kill operation is performed -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2259) Unregister an extension only if no extension jobs are dependant on the extension
[ https://issues.apache.org/jira/browse/FALCON-2259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2259: Fix Version/s: 0.11 trunk > Unregister an extension only if no extension jobs are dependant on the > extension > > > Key: FALCON-2259 > URL: https://issues.apache.org/jira/browse/FALCON-2259 > Project: Falcon > Issue Type: Bug >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Right now an extension can be unregistered irrespective of the any dependent > extensions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2146) EntitySlaAlertService runs only once irrespective of the configured frequency
[
https://issues.apache.org/jira/browse/FALCON-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2146:
Fix Version/s: 0.11
> EntitySlaAlertService runs only once irrespective of the configured frequency
> -
>
> Key: FALCON-2146
> URL: https://issues.apache.org/jira/browse/FALCON-2146
> Project: Falcon
> Issue Type: Bug
> Components: prism
>Affects Versions: trunk
>Reporter: Pragya Mittal
>Assignee: Praveen Adlakha
> Fix For: trunk, 0.11
>
>
> Initially I have 20 pending instances which have missed their sla. The logs
> say the same.
> After some time I have 33 instances of a process which have missed their sla
> {noformat}
> dataqa@falcon1001:/mnt/users/pragya/functionality/sla-alerts$ falcon entity
> -type process -slaAlert -name ProcessSLATest-agregator-coord16-dcd226b3
> -start 2016-09-16T08:50Z -end 2016-09-16T12:10Z| grep -i name | wc -l
> 33
> {noformat}
> But server logs show only 20 instances and also it is running just once
> {noformat}
> dataqa@falcon1001:/mnt/falcon$ cat server/logs/falcon.application.log| grep
> processSLACandidates
> 2016-09-16 10:01:20,117 DEBUG - [pool-13-thread-1:] ~ In processSLACandidates
> :20 (EntitySLAAlertService:115)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2154) On deleting entity backlog emitter does not go back to zero
[ https://issues.apache.org/jira/browse/FALCON-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2154: Fix Version/s: 0.11 trunk > On deleting entity backlog emitter does not go back to zero > --- > > Key: FALCON-2154 > URL: https://issues.apache.org/jira/browse/FALCON-2154 > Project: Falcon > Issue Type: Sub-task > Components: messaging >Affects Versions: trunk >Reporter: Pragya Mittal >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Currently backlog emitter service does not fall back to zero when entity is > deleted from config store. It attains a static value forever. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2281) HiveDRTest tests are getting permissions denied
[
https://issues.apache.org/jira/browse/FALCON-2281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2281:
Fix Version/s: 0.11
> HiveDRTest tests are getting permissions denied
> ---
>
> Key: FALCON-2281
> URL: https://issues.apache.org/jira/browse/FALCON-2281
> Project: Falcon
> Issue Type: Bug
>Affects Versions: trunk
> Environment: Centos 6
>Reporter: Cheng Xu
>Assignee: Sowmya Ramesh
> Fix For: trunk, 0.11
>
>
> HiveDRTest tests are getting permissions denied.
> {noformat}
> 2016-11-17 09:31:22,681 INFO - [pool-28-thread-1:] ~
> java.lang.AssertionError: Status should be SUCCEEDED. Message: default/Failed
> to copy extension artifacts to clusterAbe0e31d0-180c1ef2
> CausedBy: Permission denied: user=falcon, access=READ,
> inode="/apps/falcon/extensions/mirroring/Events/HiveDRTest7df2bcd6/HiveDRTest7df2bcd6.id":hrt_qa:users:-rwx--
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.check(FSPermissionChecker.java:319)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:219)
> at
> org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.checkPermission(FSPermissionChecker.java:190)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1827)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPermission(FSDirectory.java:1811)
> at
> org.apache.hadoop.hdfs.server.namenode.FSDirectory.checkPathAccess(FSDirectory.java:1785)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getBlockLocationsInt(FSNamesystem.java:1868)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getBlockLocations(FSNamesystem.java:1837)
> at
> org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getBlockLocations(FSNamesystem.java:1750)
> at
> org.apache.hadoop.hdfs.server.namenode.NameNodeRpcServer.getBlockLocations(NameNodeRpcServer.java:693)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolServerSideTranslatorPB.getBlockLocations(ClientNamenodeProtocolServerSideTranslatorPB.java:373)
> at
> org.apache.hadoop.hdfs.protocol.proto.ClientNamenodeProtocolProtos$ClientNamenodeProtocol$2.callBlockingMethod(ClientNamenodeProtocolProtos.java)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Server$ProtoBufRpcInvoker.call(ProtobufRpcEngine.java:640)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:982)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2313)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:2309)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1724)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:2307)
> expected [SUCCEEDED] but found [FAILED]
> at org.testng.Assert.fail(Assert.java:94)
> at org.testng.Assert.failNotEquals(Assert.java:494)
> at org.testng.Assert.assertEquals(Assert.java:123)
> at
> org.apache.falcon.regression.core.util.AssertUtil.assertSucceeded(AssertUtil.java:199)
> at
> org.apache.falcon.regression.core.bundle.Bundle.submitClusters(Bundle.java:597)
> at
> org.apache.falcon.regression.core.bundle.Bundle.submitClusters(Bundle.java:590)
> at
> org.apache.falcon.regression.extensions.HiveDRTest.setUp(HiveDRTest.java:92)
> at
> org.apache.falcon.regression.extensions.HiveDRTest.drChangeCommentAndPropertyTest(HiveDRTest.java:452)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> at
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> (TestngListener:122)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-705) Feed Retention at Instance Level
[ https://issues.apache.org/jira/browse/FALCON-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-705: --- Fix Version/s: 0.11 trunk > Feed Retention at Instance Level > > > Key: FALCON-705 > URL: https://issues.apache.org/jira/browse/FALCON-705 > Project: Falcon > Issue Type: New Feature > Components: retention >Reporter: Pracheer Agarwal >Assignee: Pracheer Agarwal > Fix For: trunk, 0.11 > > > Currently, while specifying retention in feed we need to give some time unit > and number of units like hours(6). > It will be good to have feed retention on instance level like instances(5) > which shows I want to preserve last 5 instances. > This feature is useful when whole pipeline starts after some time. So it that > case we don't have to approximate the retention. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2267) Definition api fails if resources are empty
[
https://issues.apache.org/jira/browse/FALCON-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2267:
Fix Version/s: 0.11
> Definition api fails if resources are empty
> ---
>
> Key: FALCON-2267
> URL: https://issues.apache.org/jira/browse/FALCON-2267
> Project: Falcon
> Issue Type: Bug
> Components: extensions
>Affects Versions: trunk
>Reporter: Pragya Mittal
> Fix For: trunk, 0.11
>
>
> {noformat}
> pragya.mittal@falcon1001:~$ falcon extension -definition -extensionName
> extension-example
> ERROR: Bad Request;Resource path cannot be null or empty
> {noformat}
> Hadoop path is :
> {noformat}
> pragya.mittal@falcon1001:~$ hl -R /tmp/extensions/extension-example
> /tmp/extensions/extension-example/META
> /tmp/extensions/extension-example/META/config
> /tmp/extensions/extension-example/README
> /tmp/extensions/extension-example/libs
> /tmp/extensions/extension-example/libs/build
> /tmp/extensions/extension-example/libs/build/falcon-extensions-0.11-SNAPSHOT-tests.jar
> /tmp/extensions/extension-example/libs/runtime
> /tmp/extensions/extension-example/resources
> /tmp/extensions/extension-example/resources/build
> /tmp/extensions/extension-example/resources/runtime
> {noformat}
> Extension is :
> {noformat}
> {
>"name": "extension-example",
>"type": "Custom extension",
>"location": "hdfs://192.168.138.236:8020/tmp/extensions/extension-example"
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2133) Disable the LogMover assertions from FeedReplication on Secure Mode
[ https://issues.apache.org/jira/browse/FALCON-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2133: Fix Version/s: 0.11 > Disable the LogMover assertions from FeedReplication on Secure Mode > --- > > Key: FALCON-2133 > URL: https://issues.apache.org/jira/browse/FALCON-2133 > Project: Falcon > Issue Type: Bug > Components: merlin >Affects Versions: trunk >Reporter: Murali Ramasami >Assignee: Murali Ramasami > Fix For: trunk, 0.11 > > > LogMover is only supported in case of un-secure mode. It has to be disable in > the secure mode. In FeedReplication test cases, LogMover assertions will be > done after the functionality tested covered. In this cases, we need to verify > the functionality but only disable LogMover. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2115) UT test failure on FalconCSRFFilterTest
[ https://issues.apache.org/jira/browse/FALCON-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2115: Fix Version/s: 0.11 trunk > UT test failure on FalconCSRFFilterTest > --- > > Key: FALCON-2115 > URL: https://issues.apache.org/jira/browse/FALCON-2115 > Project: Falcon > Issue Type: Bug >Reporter: Ying Zheng >Assignee: Ying Zheng > Fix For: trunk, 0.11 > > > Need to add the property falcon.security.csrf.header to startup properties > when testing custom header for CSRF filter. > Tests run: 5, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 1.186 sec <<< > FAILURE! - in org.apache.falcon.security.FalconCSRFFilterTest > testCSRFEnabledIncludeCustomHeaderFromBrowser(org.apache.falcon.security.FalconCSRFFilterTest) > Time elapsed: 0.012 sec <<< FAILURE! > org.mockito.exceptions.verification.NeverWantedButInvoked: > mockResponse.sendError( > 403, > "Missing Required Header for CSRF Vulnerability Protection" > ); > Never wanted here: > -> at > org.apache.falcon.security.FalconCSRFFilterTest.testCSRFEnabledIncludeCustomHeaderFromBrowser(FalconCSRFFilterTest.java:83) > But invoked here: > -> at > org.apache.falcon.security.RestCsrfPreventionFilter$ServletFilterHttpInteraction.sendError(RestCsrfPreventionFilter.java:173) > at > org.apache.falcon.security.FalconCSRFFilterTest.testCSRFEnabledIncludeCustomHeaderFromBrowser(FalconCSRFFilterTest.java:83) > testCSRFEnabledNoCustomHeaderFromBrowser(org.apache.falcon.security.FalconCSRFFilterTest) > Time elapsed: 0.003 sec <<< FAILURE! > org.mockito.exceptions.verification.TooManyActualInvocations: > mockResponse.sendError( > 403, > "Missing Required Header for CSRF Vulnerability Protection" > ); > Wanted 1 time: > -> at > org.apache.falcon.security.FalconCSRFFilterTest.testCSRFEnabledNoCustomHeaderFromBrowser(FalconCSRFFilterTest.java:73) > But was 2 times. Undesired invocation: > -> at > org.apache.falcon.security.RestCsrfPreventionFilter$ServletFilterHttpInteraction.sendError(RestCsrfPreventionFilter.java:173) > at > org.apache.falcon.security.FalconCSRFFilterTest.testCSRFEnabledNoCustomHeaderFromBrowser(FalconCSRFFilterTest.java:73) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2170) Umbrella jira for bugs in EntitySLAMonitoring and BacklogEmitter service
[ https://issues.apache.org/jira/browse/FALCON-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2170: Fix Version/s: 0.11 > Umbrella jira for bugs in EntitySLAMonitoring and BacklogEmitter service > - > > Key: FALCON-2170 > URL: https://issues.apache.org/jira/browse/FALCON-2170 > Project: Falcon > Issue Type: Improvement >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2160) Update startup.properties to contain valid application services
[
https://issues.apache.org/jira/browse/FALCON-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2160:
Fix Version/s: 0.11
trunk
> Update startup.properties to contain valid application services
> ---
>
> Key: FALCON-2160
> URL: https://issues.apache.org/jira/browse/FALCON-2160
> Project: Falcon
> Issue Type: Sub-task
> Components: prism
>Affects Versions: trunk
>Reporter: Pragya Mittal
>Assignee: Praveen Adlakha
> Fix For: trunk, 0.11
>
>
> In case of incorrect ordering of application services server fails to start.
> Modify the documentation as well as startup.properties to contain the correct
> order.
> The correct set of application services used in distributed mode is :
> {noformat}
> *.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
> org.apache.falcon.metrics.MetricNotificationService,\
>
> org.apache.falcon.workflow.WorkflowJobEndNotificationService, \
> org.apache.falcon.service.ProcessSubscriberService,\
> org.apache.falcon.service.FalconJPAService,\
> org.apache.falcon.extensions.ExtensionService,\
> org.apache.falcon.service.LifecyclePolicyMap,\
> org.apache.falcon.entity.store.ConfigurationStore,\
> org.apache.falcon.rerun.service.RetryService,\
> org.apache.falcon.rerun.service.LateRunService,\
> org.apache.falcon.service.LogCleanupService,\
> org.apache.falcon.service.GroupsService,\
> org.apache.falcon.service.ProxyUserService,\
> org.apache.falcon.service.EntitySLAMonitoringService,\
> org.apache.falcon.service.EntitySLAAlertService,\
> org.apache.falcon.service.BacklogMetricEmitterService
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2263) Deletion of entities for an extension has to have a specific order of deleting processes first and then feeds
[ https://issues.apache.org/jira/browse/FALCON-2263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2263: Fix Version/s: 0.11 > Deletion of entities for an extension has to have a specific order of > deleting processes first and then feeds > - > > Key: FALCON-2263 > URL: https://issues.apache.org/jira/browse/FALCON-2263 > Project: Falcon > Issue Type: Bug >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Deletion of entities for an extension has to have a specific order of > deleting processes first and then feeds. > As of now it tries to delete feeds first and fails for dependency on the > dependent process -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2078) Documentation for Process SLA
[ https://issues.apache.org/jira/browse/FALCON-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2078: Fix Version/s: 0.11 > Documentation for Process SLA > - > > Key: FALCON-2078 > URL: https://issues.apache.org/jira/browse/FALCON-2078 > Project: Falcon > Issue Type: Task >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > Need to do the documentation for process SLA will be extending the feed > documentation which is already there. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2147) Excess logging due to SlaMonitoring service and Backlog emitter service
[ https://issues.apache.org/jira/browse/FALCON-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2147: Fix Version/s: 0.11 > Excess logging due to SlaMonitoring service and Backlog emitter service > --- > > Key: FALCON-2147 > URL: https://issues.apache.org/jira/browse/FALCON-2147 > Project: Falcon > Issue Type: Bug > Components: prism >Affects Versions: trunk >Reporter: Pragya Mittal >Assignee: Pallavi Rao > Fix For: trunk, 0.11 > > > With the SlaMonitoring service clubbed with Backlog emitter service, there > has been too much logging information which is filling up the disk space. > Please minimize the same and add relevant logging. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2208) Falcon CLI(client) need hadoop in the classpath
[ https://issues.apache.org/jira/browse/FALCON-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2208: Fix Version/s: 0.11 > Falcon CLI(client) need hadoop in the classpath > --- > > Key: FALCON-2208 > URL: https://issues.apache.org/jira/browse/FALCON-2208 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > With extensions, falcon downloads the libs and resources from hdfs and so it > needs hadoop in its classpath. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2268) Extension list api does not follow default ASC order
[
https://issues.apache.org/jira/browse/FALCON-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2268:
Fix Version/s: 0.11
> Extension list api does not follow default ASC order
>
>
> Key: FALCON-2268
> URL: https://issues.apache.org/jira/browse/FALCON-2268
> Project: Falcon
> Issue Type: Bug
> Components: extensions
>Affects Versions: trunk
>Reporter: Pragya Mittal
>Assignee: Pracheer Agarwal
> Fix For: trunk, 0.11
>
>
> {noformat}
> pragya.mittal@falcon1001:~$ falcon extension -list -extensionName
> extension-example
> 5
> sample1extension-example
> sample5extension-example
> sample4extension-example
> sample3extension-example
> sample2extension-example
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-1997) Verify source tarball and run few end to end tests
[ https://issues.apache.org/jira/browse/FALCON-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-1997: Fix Version/s: (was: 0.10) 0.11 trunk > Verify source tarball and run few end to end tests > -- > > Key: FALCON-1997 > URL: https://issues.apache.org/jira/browse/FALCON-1997 > Project: Falcon > Issue Type: Sub-task > Components: build-tools >Affects Versions: 0.9 >Reporter: Balu Vellanki >Assignee: Balu Vellanki > Fix For: trunk, 0.11 > > > Verify released source tarball and run few tests on distributed and > standalone mode. > Additionally track +1 from community. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2113) Falcon retry happens in few cases inspite of a manual kill from the user
[ https://issues.apache.org/jira/browse/FALCON-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2113: Fix Version/s: 0.11 > Falcon retry happens in few cases inspite of a manual kill from the user > > > Key: FALCON-2113 > URL: https://issues.apache.org/jira/browse/FALCON-2113 > Project: Falcon > Issue Type: Bug > Components: common >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Falcon retry happens in few cases inspite of a manual kill from the user. > When a kill is issued by the user, falcon needs to move it to a different > state(ignore) and check for that state before retrying to stop it from > retrying. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2214) Falcon extension registered without fully qualified hdfs path
[
https://issues.apache.org/jira/browse/FALCON-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2214:
Fix Version/s: 0.11
> Falcon extension registered without fully qualified hdfs path
> -
>
> Key: FALCON-2214
> URL: https://issues.apache.org/jira/browse/FALCON-2214
> Project: Falcon
> Issue Type: Bug
> Components: extensions
>Affects Versions: trunk
>Reporter: Pragya Mittal
>Assignee: Praveen Adlakha
> Fix For: trunk, 0.11
>
>
> While registering extension , we need to provide fully qualified name but
> this is not the case.
> {noformat}
> falcon extension -register -extensionName extension-example -path
> /tmp/extensions/extension-example
> {
> "name": "extension-example",
> "type": "Custom extension",
> "location": "/tmp/extensions/extension-example"
> },
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-1612) Add Metadata commands to Falcon spring-shell CLI
[ https://issues.apache.org/jira/browse/FALCON-1612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-1612: Fix Version/s: 0.11 > Add Metadata commands to Falcon spring-shell CLI > > > Key: FALCON-1612 > URL: https://issues.apache.org/jira/browse/FALCON-1612 > Project: Falcon > Issue Type: Sub-task >Reporter: Rajat Khandelwal >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2054) Send entityType to FeedAlertListeners
[ https://issues.apache.org/jira/browse/FALCON-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2054: Fix Version/s: 0.11 trunk > Send entityType to FeedAlertListeners > - > > Key: FALCON-2054 > URL: https://issues.apache.org/jira/browse/FALCON-2054 > Project: Falcon > Issue Type: Improvement >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > We need to send entityType to the listeners. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2119) Minor Licensing Issue
[ https://issues.apache.org/jira/browse/FALCON-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2119: Fix Version/s: 0.11 > Minor Licensing Issue > - > > Key: FALCON-2119 > URL: https://issues.apache.org/jira/browse/FALCON-2119 > Project: Falcon > Issue Type: Improvement >Reporter: Ajay Yadava >Assignee: Ajay Yadava > Fix For: trunk, 0.11 > > > falcon-sources-0.10/falcon-ui/app/css/styles/angular-notify.less > is actually not an original work and is exactly same as MIT Licensed (but not > mentioned in LICENSE.txt) except for few commented lines. > https://github.com/cgross/angular-notify/blob/master/angular-notify.css -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2148) Entries not removed from sla list when instance succeeds
[ https://issues.apache.org/jira/browse/FALCON-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2148: Fix Version/s: 0.11 > Entries not removed from sla list when instance succeeds > > > Key: FALCON-2148 > URL: https://issues.apache.org/jira/browse/FALCON-2148 > Project: Falcon > Issue Type: Bug > Components: prism >Affects Versions: trunk >Reporter: Pragya Mittal >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Entries corresponding to a process sla should be removed if the process goes > from WAITING to SUCCEEDED state. The same is not happening. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2098) Create release notes for 0.10
[ https://issues.apache.org/jira/browse/FALCON-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2098: Fix Version/s: (was: 0.10) 0.11 trunk > Create release notes for 0.10 > - > > Key: FALCON-2098 > URL: https://issues.apache.org/jira/browse/FALCON-2098 > Project: Falcon > Issue Type: Sub-task > Components: ease >Reporter: Balu Vellanki >Assignee: Balu Vellanki > Fix For: trunk, 0.11 > > Attachments: FalconReleaseNotes-0.10.docx, FalconReleaseNotes-0.10.pdf > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2241) Job submission for registered extension is broken
[
https://issues.apache.org/jira/browse/FALCON-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2241:
Fix Version/s: 0.11
trunk
> Job submission for registered extension is broken
> -
>
> Key: FALCON-2241
> URL: https://issues.apache.org/jira/browse/FALCON-2241
> Project: Falcon
> Issue Type: Bug
> Components: extensions
>Affects Versions: trunk
>Reporter: Pragya Mittal
>Assignee: sandeep samudrala
> Fix For: trunk, 0.11
>
>
> {noformat}
> dataqa@falcon1001:~$ falcon extension -submit -jobName sample3 -file abc
> -extensionName extension-example
> ERROR: Error in building the extension
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (FALCON-2157) Pending instances are not getting deleted from database even though the instance finishes
[ https://issues.apache.org/jira/browse/FALCON-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2157: Fix Version/s: 0.11 trunk > Pending instances are not getting deleted from database even though the > instance finishes > - > > Key: FALCON-2157 > URL: https://issues.apache.org/jira/browse/FALCON-2157 > Project: Falcon > Issue Type: Sub-task > Components: prism >Affects Versions: trunk >Reporter: Pragya Mittal >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > On scheduling a process in distributed mode entity instances goes in waiting > state and backlog gets updated. > On resolving dependencies of instances the entries should get deleted from db > table - BACKLOG_METRIC, PENDING_INSTANCES. > But this is not happening, the db is not getting updated as expected and > also backlog should reduce but it is also not happening. > Process frequency : 1 minute > LookAhead window : 1 minute > (lookahead window is same as entity frequency) > Entries are deleted but again getting created. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2072) Hive2 URLs in Falcon should allow additional configuration elements in the URL
[ https://issues.apache.org/jira/browse/FALCON-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2072: Fix Version/s: 0.11 > Hive2 URLs in Falcon should allow additional configuration elements in the URL > -- > > Key: FALCON-2072 > URL: https://issues.apache.org/jira/browse/FALCON-2072 > Project: Falcon > Issue Type: Bug >Affects Versions: 0.6.1, 0.8, 0.9, 0.10 >Reporter: Venkat Ranganathan >Assignee: Sowmya Ramesh > Fix For: trunk, 0.11 > > > When configuring the Hive2 URLs, SSL, trust store password may need to be > specified. > Furthermore, the URL can be configured to use zookeeper discovery mode where > zookeeper can be used as a single point of configuration changes that are > automatically available to the Hive2 clients. This mode also supports HA > for the HiveServer -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2280) Unable to create mirror on WASB target due to "Cluster entity not found"
[ https://issues.apache.org/jira/browse/FALCON-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2280: Fix Version/s: 0.11 > Unable to create mirror on WASB target due to "Cluster entity not found" > > > Key: FALCON-2280 > URL: https://issues.apache.org/jira/browse/FALCON-2280 > Project: Falcon > Issue Type: Bug > Components: extensions >Reporter: Sowmya Ramesh >Assignee: Sowmya Ramesh > Fix For: trunk, 0.11 > > > 1. Create a mirror which source cluster is the one created , and dummy target > cluster > 2. Save > Submitting the mirror from CLI （see log below）: > 1) with WASB url on "targetCluster", it complained that the WASB was invalid > or > 2) with nothing on "targetCluster", it complained that "Cluster entity not > found" > # cat /tmp/hdfsMirroring.props > jobName=testjob > jobClusterName=primaryCluster > jobValidityStart=2017-01-13T00:00Z > jobValidityEnd=2017-12-30T00:00Z > jobFrequency=minutes(5) > sourceDir=/data/testdir > sourceCluster=primaryCluster > targetDir=/data/testdir > targetCluster= > # su - falcon > # /usr/hdp/current/falcon-server/bin/falcon extension -submit -extensionName > hdfs-mirroring -file /tmp/hdfsMirroring.props > ERROR: Internal Server Error;Cluster entity not found -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2161) Process Sla API does not show sla for last instance
[ https://issues.apache.org/jira/browse/FALCON-2161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2161: Fix Version/s: 0.11 trunk > Process Sla API does not show sla for last instance > --- > > Key: FALCON-2161 > URL: https://issues.apache.org/jira/browse/FALCON-2161 > Project: Falcon > Issue Type: Sub-task > Components: prism >Affects Versions: trunk >Reporter: Pragya Mittal >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > For last instance of a process the entry exists in PENDING_INSTANCES list in > db but the same is not reflected by slaAlert cli. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2211) Falcon Fails to start in distributed mode
[
https://issues.apache.org/jira/browse/FALCON-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Praveen Adlakha updated FALCON-2211:
Fix Version/s: 0.11
> Falcon Fails to start in distributed mode
> -
>
> Key: FALCON-2211
> URL: https://issues.apache.org/jira/browse/FALCON-2211
> Project: Falcon
> Issue Type: Sub-task
> Components: extensions
>Reporter: Praveen Adlakha
>Assignee: Praveen Adlakha
> Fix For: trunk, 0.11
>
>
> Hi All,
> If we start ExtensionService on prism and server it fails to start with
> following exception
> {noformat}
> 2016-12-08 12:21:10,220 ERROR - [main:] ~ Exception in ExtensionMetaStore:
> (ExtensionStore:109)
> org.apache.falcon.entity.store.StoreAccessException: java.lang.Exception:
> For extension mirroring there are no artifacts at the extension store path
> file:/mnt/falcon/prism/extensions
> at
> org.apache.falcon.extensions.store.ExtensionStore.getExtensionArtifacts(ExtensionStore.java:150)
> at
> org.apache.falcon.extensions.store.ExtensionStore.getResource(ExtensionStore.java:317)
> at
> org.apache.falcon.extensions.store.ExtensionStore.getShortDescription(ExtensionStore.java:116)
> at
> org.apache.falcon.extensions.store.ExtensionStore.initializeDbTable(ExtensionStore.java:103)
> at
> org.apache.falcon.extensions.store.ExtensionStore.(ExtensionStore.java:93)
> at
> org.apache.falcon.extensions.store.ExtensionStore.(ExtensionStore.java:78)
> at
> org.apache.falcon.extensions.ExtensionService.getExtensionStore(ExtensionService.java:47)
> at
> org.apache.falcon.extensions.ExtensionService.init(ExtensionService.java:39)
> at
> org.apache.falcon.service.ServiceInitializer.initialize(ServiceInitializer.java:47)
> at
> org.apache.falcon.listener.ContextStartupListener.contextInitialized(ContextStartupListener.java:56)
> at
> org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:550)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
> at
> org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1282)
> at
> org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:519)
> at
> org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> at org.mortbay.jetty.Server.doStart(Server.java:224)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.apache.falcon.util.EmbeddedServer.start(EmbeddedServer.java:58)
> at org.apache.falcon.FalconServer.main(FalconServer.java:118)
> Caused by: java.lang.Exception: For extension mirroring there are no
> artifacts at the extension store path file:/mnt/falcon/prism/extensions
> {noformat}
> Although /mnt/falcon/prism/extensions is not empty
> {noformat}
> dataqa@falcon1001:/mnt/falcon$ ls -R /mnt/falcon/prism/extensions
> /mnt/falcon/prism/extensions:
> hdfs-mirroring hdfs-snapshot-mirroring hive-mirroring mirroring
> /mnt/falcon/prism/extensions/hdfs-mirroring:
> libs META README resources
> /mnt/falcon/prism/extensions/hdfs-mirroring/libs:
> build runtime
> /mnt/falcon/prism/extensions/hdfs-mirroring/libs/build:
> /mnt/falcon/prism/extensions/hdfs-mirroring/libs/runtime:
> /mnt/falcon/prism/extensions/hdfs-mirroring/META:
> hdfs-mirroring-properties.json
> /mnt/falcon/prism/extensions/hdfs-mirroring/resources:
> build runtime
> /mnt/falcon/prism/extensions/hdfs-mirroring/resources/build:
> /mnt/falcon/prism/extensions/hdfs-mirroring/resources/runtime:
> hdfs-mirroring-template.xml hdfs-mirroring-workflow.xml
> /mnt/falcon/prism/extensions/hdfs-snapshot-mirroring:
> libs META README resources
> /mnt/falcon/prism/extensions/hdfs-snapshot-mirroring/libs:
> build runtime
> /mnt/falcon/prism/extensions/hdfs-snapshot-mirroring/libs/build:
> /mnt/falcon/prism/extensions/hdfs-snapshot-mirroring/libs/runtime:
> /mnt/falcon/prism/extensions/hdfs-snapshot-mirroring/META:
> hdfs-snapshot-mirroring-properties.json
> /mnt/falcon/prism/extensions/hdfs-snapshot-mirroring/resources:
> build runtime
> /mnt/falcon/prism/extensions/hdfs-snapshot-mirroring/resources/build:
> /mnt/falcon/prism/extensions/hdfs-snapshot-mirroring/resources/runtime:
> hdfs-snapshot-mirroring-template.xml hdfs-snapshot-mirroring-workflow.xml
> /mnt/falcon/prism/extensions/hive-mirroring:
> libs META README resources
> /mnt/falcon/prism/extensions/hive-mirroring/libs:
> build runtime
> /mnt/falcon/prism/extensions/hive-mirroring/libs/build:
> /mnt/falcon/prism/extensions/hive-mirroring/libs/runtime:
>
[jira] [Updated] (FALCON-2162) Feed replication based on partition does not produce expected output
[ https://issues.apache.org/jira/browse/FALCON-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2162: Fix Version/s: 0.11 trunk > Feed replication based on partition does not produce expected output > > > Key: FALCON-2162 > URL: https://issues.apache.org/jira/browse/FALCON-2162 > Project: Falcon > Issue Type: Bug > Components: feed, prism >Affects Versions: trunk >Reporter: Pragya Mittal > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2172) User: falcon is not allowed to impersonate ambari-qa
[ https://issues.apache.org/jira/browse/FALCON-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2172: Fix Version/s: 0.11 trunk > User: falcon is not allowed to impersonate ambari-qa > - > > Key: FALCON-2172 > URL: https://issues.apache.org/jira/browse/FALCON-2172 > Project: Falcon > Issue Type: Bug >Affects Versions: 0.10 >Reporter: Dasiy > Fix For: trunk, 0.11 > > > I loged in the falcon WebUI with the username "ambari-qa". I try to create > cluster in falcon WebUI, and when I want t to save it, I got the meesage: > "default/Invalid storage server or port: hdfs://master1.bigdata:8020, User: > falcon is not allowed to impersonate ambari-qa CausedBy: User: falcon is not > allowed to impersonate ambari-qa" -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2246) Api to list all the jobs in the system (and what extensions do they refer to)
[ https://issues.apache.org/jira/browse/FALCON-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2246: Fix Version/s: 0.11 > Api to list all the jobs in the system (and what extensions do they refer to) > - > > Key: FALCON-2246 > URL: https://issues.apache.org/jira/browse/FALCON-2246 > Project: Falcon > Issue Type: Improvement > Components: extensions >Affects Versions: trunk >Reporter: Pragya Mittal >Assignee: Pracheer Agarwal > Fix For: trunk, 0.11 > > > jobName being unique in falcon system, we can expose an api to list all the > jobs in the system and what extension do they refer to. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2188) Rest api to register extension
[ https://issues.apache.org/jira/browse/FALCON-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2188: Fix Version/s: 0.11 > Rest api to register extension > --- > > Key: FALCON-2188 > URL: https://issues.apache.org/jira/browse/FALCON-2188 > Project: Falcon > Issue Type: Sub-task > Components: extensions >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > > Hi All, > In this sub task will be creating a rest api to register the new recipe with > validation of the extension. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-1944) Ability to provide additional DistCP options for mirroring extensions and feed replication
[ https://issues.apache.org/jira/browse/FALCON-1944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-1944: Fix Version/s: 0.11 > Ability to provide additional DistCP options for mirroring extensions and > feed replication > -- > > Key: FALCON-1944 > URL: https://issues.apache.org/jira/browse/FALCON-1944 > Project: Falcon > Issue Type: Improvement >Reporter: Sowmya Ramesh >Assignee: Sowmya Ramesh > Fix For: trunk, 0.11 > > > Mirroring extensions and feed replication should have the ability to provide > additional DistCp options. Also handle TDE enabled option -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2144) Close stale pull requests - part 2
[ https://issues.apache.org/jira/browse/FALCON-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2144: Fix Version/s: (was: 1.0) 0.11 trunk > Close stale pull requests - part 2 > -- > > Key: FALCON-2144 > URL: https://issues.apache.org/jira/browse/FALCON-2144 > Project: Falcon > Issue Type: Task >Reporter: Ajay Yadava >Assignee: Ajay Yadava > Fix For: trunk, 0.11 > > > Sorry I missed one in the earlier patch which I thought the author closed and > found another one. > https://github.com/apache/falcon/pull/33 > https://github.com/apache/falcon/pull/258 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-1596) Spring shell based CLI for falcon
[ https://issues.apache.org/jira/browse/FALCON-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-1596: Fix Version/s: 0.11 > Spring shell based CLI for falcon > - > > Key: FALCON-1596 > URL: https://issues.apache.org/jira/browse/FALCON-1596 > Project: Falcon > Issue Type: New Feature > Components: shell >Reporter: Rajat Khandelwal >Assignee: Praveen Adlakha > Fix For: trunk, 0.11 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (FALCON-2258) Improve error message for definition/describe api in case extension does not exist
[ https://issues.apache.org/jira/browse/FALCON-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Praveen Adlakha updated FALCON-2258: Fix Version/s: 0.11 > Improve error message for definition/describe api in case extension does not > exist > -- > > Key: FALCON-2258 > URL: https://issues.apache.org/jira/browse/FALCON-2258 > Project: Falcon > Issue Type: Sub-task >Reporter: sandeep samudrala >Assignee: sandeep samudrala > Fix For: trunk, 0.11 > > > Extension check is expecting a single result set, causing failure of not > being found. This has to be checked for result set and send the response > message accordingly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
