[jira] [Created] (FALCON-2312) Document for Feed Based Archival
Pragya Mittal created FALCON-2312: - Summary: Document for Feed Based Archival Key: FALCON-2312 URL: https://issues.apache.org/jira/browse/FALCON-2312 Project: Falcon Issue Type: Sub-task Reporter: Pragya Mittal Assignee: Pragya Mittal Document for Feed Based Archival -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2312) Document for Feed Based Archival
[ https://issues.apache.org/jira/browse/FALCON-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2312: -- Attachment: Feed Lifecycle Archival Stage.pdf > Document for Feed Based Archival > > > Key: FALCON-2312 > URL: https://issues.apache.org/jira/browse/FALCON-2312 > Project: Falcon > Issue Type: Sub-task >Reporter: Pragya Mittal >Assignee: Pragya Mittal > Attachments: Feed Lifecycle Archival Stage.pdf > > > Document for Feed Based Archival -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (FALCON-2311) XSD for Feed Archival
[ https://issues.apache.org/jira/browse/FALCON-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal reassigned FALCON-2311: - Assignee: Pragya Mittal > XSD for Feed Archival > - > > Key: FALCON-2311 > URL: https://issues.apache.org/jira/browse/FALCON-2311 > Project: Falcon > Issue Type: Sub-task >Reporter: Pragya Mittal >Assignee: Pragya Mittal > Attachments: xsd.patch > > > Added archival stage xsd definition with this JIRA. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2311) XSD for Feed Archival
[ https://issues.apache.org/jira/browse/FALCON-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2311: -- Attachment: xsd.patch > XSD for Feed Archival > - > > Key: FALCON-2311 > URL: https://issues.apache.org/jira/browse/FALCON-2311 > Project: Falcon > Issue Type: Sub-task >Reporter: Pragya Mittal > Attachments: xsd.patch > > > Added archival stage xsd definition with this JIRA. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2311) XSD for Feed Archival
[ https://issues.apache.org/jira/browse/FALCON-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2311: -- Description: Added archival stage xsd definition with this JIRA. > XSD for Feed Archival > - > > Key: FALCON-2311 > URL: https://issues.apache.org/jira/browse/FALCON-2311 > Project: Falcon > Issue Type: Sub-task >Reporter: Pragya Mittal > > Added archival stage xsd definition with this JIRA. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2310) Master JIRA : Enabling Feed Archival
[ https://issues.apache.org/jira/browse/FALCON-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2310: -- Description: Currently falcon lifecycle plugin supports retention stage which allows users to delete data in an effective manner. With the introduction of archival stage as part of lifecycle plugin we will be able to move data to external location (say s3/s4) without adhering to the current replication format. > Master JIRA : Enabling Feed Archival > > > Key: FALCON-2310 > URL: https://issues.apache.org/jira/browse/FALCON-2310 > Project: Falcon > Issue Type: New Feature >Reporter: Pragya Mittal >Assignee: Pragya Mittal > > Currently falcon lifecycle plugin supports retention stage which allows users > to delete data in an effective manner. With the introduction of archival > stage as part of lifecycle plugin we will be able to move data to external > location (say s3/s4) without adhering to the current replication format. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (FALCON-2310) Master JIRA : Enabling Feed Archival
Pragya Mittal created FALCON-2310: - Summary: Master JIRA : Enabling Feed Archival Key: FALCON-2310 URL: https://issues.apache.org/jira/browse/FALCON-2310 Project: Falcon Issue Type: New Feature Reporter: Pragya Mittal Assignee: Pragya Mittal -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (FALCON-2286) Falcon upgradation fails to create new tables
[
https://issues.apache.org/jira/browse/FALCON-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pragya Mittal updated FALCON-2286:
--
Description:
While installing falcon it fails to create new tables into existing database.
{noformat}
mysql> show tables;
++
| Tables_in_falcon |
++
| BACKLOG_METRIC |
| ENTITIES |
| ENTITY_SLA_ALERTS |
| FALCON_DB_PROPS|
| INSTANCES |
| MONITORED_ENTITY |
| OPENJPA_SEQUENCE_TABLE |
| PENDING_INSTANCES |
| ProcessInstanceInfo|
++
9 rows in set (0.01 sec)
{noformat}
Creating database :
{noformat}
pragya.mittal@falcon1001:/mnt/falcon/server$ sudo -u ivory ./bin/falcon-db.sh
upgrade -sqlfile falcon.sql -run
DONE
DB schema exists
Get Falcon DB version
DONE
Falcon DB already upgraded to Falcon version '0.11-SNAPSHOT'
{noformat}
Database is not updated with tables : EXTENSIONS<,EXTENSION_JOBS
{noformat}
mysql> show tables;
++
| Tables_in_falcon |
++
| BACKLOG_METRIC |
| ENTITIES |
| ENTITY_SLA_ALERTS |
| FALCON_DB_PROPS|
| INSTANCES |
| MONITORED_ENTITY |
| OPENJPA_SEQUENCE_TABLE |
| PENDING_INSTANCES |
| ProcessInstanceInfo|
++
9 rows in set (0.00 sec)
{noformat}
was:
While installing falcon it fails to create new tables into existing database.
{noformat}
mysql> show tables;
++
| Tables_in_falcon |
++
| BACKLOG_METRIC |
| ENTITIES |
| ENTITY_SLA_ALERTS |
| FALCON_DB_PROPS|
| INSTANCES |
| MONITORED_ENTITY |
| OPENJPA_SEQUENCE_TABLE |
| PENDING_INSTANCES |
| ProcessInstanceInfo|
++
9 rows in set (0.01 sec)
{noformat}
Creating database :
{noformat}
pragya.mittal@falcon1001:/mnt/falcon/server$ sudo -u ivory ./bin/falcon-db.sh
create -sqlfile falcon.sql -run
DONE
DB schema exists
The SQL commands have been written to: falcon.sql
{noformat}
Database is not updated with tables : EXTENSIONS<,EXTENSION_JOBS
{noformat}
mysql> show tables;
++
| Tables_in_falcon |
++
| BACKLOG_METRIC |
| ENTITIES |
| ENTITY_SLA_ALERTS |
| FALCON_DB_PROPS|
| INSTANCES |
| MONITORED_ENTITY |
| OPENJPA_SEQUENCE_TABLE |
| PENDING_INSTANCES |
| ProcessInstanceInfo|
++
9 rows in set (0.00 sec)
{noformat}
> Falcon upgradation fails to create new tables
> -
>
> Key: FALCON-2286
> URL: https://issues.apache.org/jira/browse/FALCON-2286
> Project: Falcon
> Issue Type: Bug
> Components: extensions
>Affects Versions: trunk, 0.10
>Reporter: Pragya Mittal
>
> While installing falcon it fails to create new tables into existing database.
> {noformat}
> mysql> show tables;
> ++
> | Tables_in_falcon |
> ++
> | BACKLOG_METRIC |
> | ENTITIES |
> | ENTITY_SLA_ALERTS |
> | FALCON_DB_PROPS|
> | INSTANCES |
> | MONITORED_ENTITY |
> | OPENJPA_SEQUENCE_TABLE |
> | PENDING_INSTANCES |
> | ProcessInstanceInfo|
> ++
> 9 rows in set (0.01 sec)
> {noformat}
> Creating database :
> {noformat}
> pragya.mittal@falcon1001:/mnt/falcon/server$ sudo -u ivory ./bin/falcon-db.sh
> upgrade -sqlfile falcon.sql -run
> DONE
> DB schema exists
> Get Falcon DB version
> DONE
> Falcon DB already upgraded to Falcon version '0.11-SNAPSHOT'
> {noformat}
> Database is not updated with tables : EXTENSIONS<,EXTENSION_JOBS
> {noformat}
> mysql> show tables;
>
>++
> | Tables_in_falcon |
> ++
> | BACKLOG_METRIC |
> | ENTITIES |
> | ENTITY_SLA_ALERTS |
> | FALCON_DB_PROPS|
> | INSTANCES |
> | MONITORED_ENTITY |
> | OPENJPA_SEQUENCE_TABLE |
> | PENDING_INSTANCES |
> | ProcessInstanceInfo|
> ++
> 9 rows in set (0.00 sec)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (FALCON-2286) Falcon upgradation fails to create new tables
Pragya Mittal created FALCON-2286:
-
Summary: Falcon upgradation fails to create new tables
Key: FALCON-2286
URL: https://issues.apache.org/jira/browse/FALCON-2286
Project: Falcon
Issue Type: Bug
Components: extensions
Affects Versions: trunk, 0.10
Reporter: Pragya Mittal
While installing falcon it fails to create new tables into existing database.
{noformat}
mysql> show tables;
++
| Tables_in_falcon |
++
| BACKLOG_METRIC |
| ENTITIES |
| ENTITY_SLA_ALERTS |
| FALCON_DB_PROPS|
| INSTANCES |
| MONITORED_ENTITY |
| OPENJPA_SEQUENCE_TABLE |
| PENDING_INSTANCES |
| ProcessInstanceInfo|
++
9 rows in set (0.01 sec)
{noformat}
Creating database :
{noformat}
pragya.mittal@falcon1001:/mnt/falcon/server$ sudo -u ivory ./bin/falcon-db.sh
create -sqlfile falcon.sql -run
DONE
DB schema exists
The SQL commands have been written to: falcon.sql
{noformat}
Database is not updated with tables : EXTENSIONS<,EXTENSION_JOBS
{noformat}
mysql> show tables;
++
| Tables_in_falcon |
++
| BACKLOG_METRIC |
| ENTITIES |
| ENTITY_SLA_ALERTS |
| FALCON_DB_PROPS|
| INSTANCES |
| MONITORED_ENTITY |
| OPENJPA_SEQUENCE_TABLE |
| PENDING_INSTANCES |
| ProcessInstanceInfo|
++
9 rows in set (0.00 sec)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (FALCON-2285) Instance kill shows incorrect response if there are already killed entries
Pragya Mittal created FALCON-2285:
-
Summary: Instance kill shows incorrect response if there are
already killed entries
Key: FALCON-2285
URL: https://issues.apache.org/jira/browse/FALCON-2285
Project: Falcon
Issue Type: Bug
Components: extensions
Affects Versions: trunk, 0.10
Reporter: Pragya Mittal
{noformat}
pragya.mittal@falcon1001:~$ falcon instance -type process -name
web-j1-ProcessRecipe-test -start 2017-02-07T01:00Z -end 2017-02-10T12:00Z
-status
2017-02-07T01:00Z local - RUNNING 2017-02-15T07:03Z
2017-02-15T07:03Z -
http://falcon1001.dataqa.ev1.inmobi.com:11000/oozie?job=230-170214054914137-oozie-oozi-W
2017-02-07T01:06Z local - KILLED 2017-02-15T06:57Z
2017-02-15T07:02Z -
http://falcon1001.dataqa.ev1.inmobi.com:11000/oozie?job=232-170214054914137-oozie-oozi-W
2017-02-07T01:12Z local - RUNNING 2017-02-15T07:03Z -
-
http://falcon1001.dataqa.ev1.inmobi.com:11000/oozie?job=234-170214054914137-oozie-oozi-W
2017-02-07T01:18Z local - WAITING - -
hdfs://192.168.138.236:8020/tmp/falcon-regression/ExtensionTest/input/2017/02/07/01/18
-
2017-02-07T01:24Z local - WAITING - -
hdfs://192.168.138.236:8020/tmp/falcon-regression/ExtensionTest/input/2017/02/07/01/24
-
2017-02-07T01:30Z local - WAITING - -
hdfs://192.168.138.236:8020/tmp/falcon-regression/ExtensionTest/input/2017/02/07/01/30
-
2017-02-07T01:36Z local - WAITING - -
hdfs://192.168.138.236:8020/tmp/falcon-regression/ExtensionTest/input/2017/02/07/01/36
-
2017-02-07T01:42Z local - WAITING - -
hdfs://192.168.138.236:8020/tmp/falcon-regression/ExtensionTest/input/2017/02/07/01/42
-
2017-02-07T01:48Z local - WAITING - -
hdfs://192.168.138.236:8020/tmp/falcon-regression/ExtensionTest/input/2017/02/07/01/48
-
2017-02-07T01:54Z local - WAITING - -
hdfs://192.168.138.236:8020/tmp/falcon-regression/ExtensionTest/input/2017/02/07/01/54
-
{noformat}
Error is :
{noformat}
pragya.mittal@falcon1001:~$ falcon instance -type process -name
web-j1-ProcessRecipe-test -start 2017-02-07T01:06Z -end 2017-02-07T01:18Z -kill
ERROR: Bad Request;ua1/IGNORE
{noformat}
Although the status of instances is killed but response says otherwise. STatus
is :
{noformat}
pragya.mittal@falcon1001:~$ fip -name web-j1-ProcessRecipe-test -start
2017-02-07T01:00Z -end 2017-02-10T12:00Z -status| grep local
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]
2017-02-07T01:00Z local - RUNNING 2017-02-15T07:05Z -
-
http://falcon1001.dataqa.ev1.inmobi.com:11000/oozie?job=230-170214054914137-oozie-oozi-W
2017-02-07T01:06Z local - KILLED 2017-02-15T06:57Z
2017-02-15T07:02Z -
http://falcon1001.dataqa.ev1.inmobi.com:11000/oozie?job=232-170214054914137-oozie-oozi-W
2017-02-07T01:12Z local - KILLED 2017-02-15T07:03Z
2017-02-15T07:05Z -
http://falcon1001.dataqa.ev1.inmobi.com:11000/oozie?job=234-170214054914137-oozie-oozi-W
2017-02-07T01:18Z local - WAITING - -
hdfs://192.168.138.236:8020/tmp/falcon-regression/ExtensionTest/input/2017/02/07/01/18
-
2017-02-07T01:24Z local - WAITING - -
hdfs://192.168.138.236:8020/tmp/falcon-regression/ExtensionTest/input/2017/02/07/01/24
-
2017-02-07T01:30Z local - WAITING - -
hdfs://192.168.138.236:8020/tmp/falcon-regression/ExtensionTest/input/2017/02/07/01/30
-
2017-02-07T01:36Z local - WAITING - -
hdfs://192.168.138.236:8020/tmp/falcon-regression/ExtensionTest/input/2017/02/07/01/36
-
2017-02-07T01:42Z local - WAITING - -
hdfs://192.168.138.236:8020/tmp/falcon-regression/ExtensionTest/input/2017/02/07/01/42
-
2017-02-07T01:48Z local - WAITING - -
hdfs://192.168.138.236:8020/tmp/falcon-regression/ExtensionTest/input/2017/02/07/01/48
-
2017-02-07T01:54Z local - WAITING - -
hdfs://192.168.138.236:8020/tmp/falcon-regression/ExtensionTest/input/2017/02/07/01/54
-
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (FALCON-2279) Killed instances are not rerun via falcon
Pragya Mittal created FALCON-2279:
-
Summary: Killed instances are not rerun via falcon
Key: FALCON-2279
URL: https://issues.apache.org/jira/browse/FALCON-2279
Project: Falcon
Issue Type: Bug
Components: rerun
Affects Versions: trunk, 0.10
Reporter: Pragya Mittal
Assignee: sandeep samudrala
{noformat}
pragya.mittal@falcon1001:~$ fip -name A2e5a4c86-83e2f69c -start
2010-01-02T01:05Z -end 2010-01-02T01:10Z -rerun
Consolidated Status: SUCCEEDED
Instances:
InstanceCluster SourceCluster Status
Start End Details Log
---
2010-01-02T01:05Z A2e5a4c86-13c59037 - KILLED
2017-02-08T11:44Z 2017-02-08T11:44Z -
http://falcon1001.dataqa.ev1.inmobi.com:11000/oozie?job=0001286-170203094117942-oozie-oozi-W
Additional Information:
Response: ua1/RERUN
Request Id: ua1/1134825503@qtp-6444850-31 - 207af380-2fd6-42c8-aed6-6f853e9131cd
pragya.mittal@falcon1001:~$ fip -name A2e5a4c86-83e2f69c -start
2010-01-02T01:05Z -end 2010-01-02T01:10Z -status
Consolidated Status: SUCCEEDED
Instances:
InstanceCluster SourceCluster Status
Start End Details Log
---
2010-01-02T01:05Z A2e5a4c86-13c59037 - KILLED
2017-02-08T11:44Z 2017-02-08T11:44Z -
http://falcon1001.dataqa.ev1.inmobi.com:11000/oozie?job=0001286-170203094117942-oozie-oozi-W
actions:
aggregator KILLED
http://falcon1001.dataqa.ev1.inmobi.com:8088/proxy/application_1484039203276_0905/
Additional Information:
Response: ua1/STATUS
Request Id: ua1/1134825503@qtp-6444850-31 - 2b4eccdf-702a-4541-a10a-66647e0fa78a
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (FALCON-2278) Graphite monitoring service fails with IllegalArgumentException
Pragya Mittal created FALCON-2278:
-
Summary: Graphite monitoring service fails with
IllegalArgumentException
Key: FALCON-2278
URL: https://issues.apache.org/jira/browse/FALCON-2278
Project: Falcon
Issue Type: Bug
Affects Versions: trunk
Reporter: Pragya Mittal
{noformat}
2017-02-08 11:47:04,256 ERROR - [598879390@qtp-1229202732-368 -
21c99d9f-4572-4f31-9ede-9d3e83d5b6c0:pragya.mittal:GET//instance/status/process/A2e5a4c86-83e2f69c]
~ Exception in sending metrics to FalconDB: (ProcessExecutionStatsPlugin:73)
java.lang.IllegalArgumentException: Invalid format: "NULL"
at
org.joda.time.format.DateTimeParserBucket.doParseMillis(DateTimeParserBucket.java:187)
at
org.joda.time.format.DateTimeFormatter.parseMillis(DateTimeFormatter.java:780)
at
org.joda.time.convert.StringConverter.getInstantMillis(StringConverter.java:65)
at org.joda.time.base.BaseDateTime.(BaseDateTime.java:175)
at org.joda.time.DateTime.(DateTime.java:257)
at
org.apache.falcon.plugin.ProcessExecutionStatsPlugin.monitor(ProcessExecutionStatsPlugin.java:54)
at
org.apache.falcon.plugin.ChainableMonitoringPlugin.monitor(ChainableMonitoringPlugin.java:104)
at
org.apache.falcon.plugin.ChainableMonitoringPlugin.publishMessage(ChainableMonitoringPlugin.java:113)
at
org.apache.falcon.aspect.AbstractFalconAspect.logAroundMonitored(AbstractFalconAspect.java:62)
at
org.apache.falcon.resource.proxy.InstanceManagerProxy.getStatus(InstanceManagerProxy.java:220)
at sun.reflect.GeneratedMethodAccessor103.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (FALCON-2275) Unable to list instances of an extension
Pragya Mittal created FALCON-2275:
-
Summary: Unable to list instances of an extension
Key: FALCON-2275
URL: https://issues.apache.org/jira/browse/FALCON-2275
Project: Falcon
Issue Type: Bug
Components: extensions
Affects Versions: trunk, 0.10
Reporter: Pragya Mittal
{noformat}
pragya.mittal@falcon1001:~$ falcon extension -instances -extensionName new-ext1
-jobName new-job1
ERROR: Bad Request;Unable to get instance for
org.apache.falcon.workflow.engine.FalconWorkflowEngine
{noformat}
Stack trace :
{noformat}
2017-02-07 10:52:09,973 ERROR - [1004540855@qtp-1229202732-8 -
56871345-1444-4a93-89da-c43ae4303dbc:pragya.mittal:GET//extension/instances/new-job1]
~ Failed to get instances status (AbstractInstanceManager:186)
org.apache.falcon.FalconException: Unable to get instance for
org.apache.falcon.workflow.engine.FalconWorkflowEngine
at
org.apache.falcon.util.ReflectionUtils.getInstanceByClassName(ReflectionUtils.java:52)
at
org.apache.falcon.workflow.WorkflowEngineFactory.getNativeWorkflowEngine(WorkflowEngineFactory.java:118)
at
org.apache.falcon.workflow.WorkflowEngineFactory.getWorkflowEngine(WorkflowEngineFactory.java:55)
at
org.apache.falcon.resource.AbstractEntityManager.getWorkflowEngine(AbstractEntityManager.java:1426)
at
org.apache.falcon.resource.AbstractInstanceManager.getStatus(AbstractInstanceManager.java:181)
at
org.apache.falcon.resource.proxy.ExtensionManagerProxy.getInstances(ExtensionManagerProxy.java:138)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
at
org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
Caused by: java.lang.ClassNotFoundException:
org.apache.falcon.workflow.engine.FalconWorkflowEngine
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at
org.apache.falcon.util.ReflectionUtils.getInstanceByClassName(ReflectionUtils.java:44)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (FALCON-2261) Job submission fails with IllegalArgumentException
Pragya Mittal created FALCON-2261:
-
Summary: 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
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.4#6332)
[jira] [Updated] (FALCON-2247) Include status of the entities of the extensionJob in getDetailExtensionJobs
[ https://issues.apache.org/jira/browse/FALCON-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2247: -- Component/s: extensions > Include status of the entities of the extensionJob in getDetailExtensionJobs > > > Key: FALCON-2247 > URL: https://issues.apache.org/jira/browse/FALCON-2247 > Project: Falcon > Issue Type: Improvement > Components: extensions >Reporter: Pracheer Agarwal >Assignee: Pracheer Agarwal >Priority: Minor > > Include status of the entities of the extensionJob in getDetailExtensionJobs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FALCON-2247) Include status of the entities of the extensionJob in getDetailExtensionJobs
[ https://issues.apache.org/jira/browse/FALCON-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2247: -- Affects Version/s: trunk > Include status of the entities of the extensionJob in getDetailExtensionJobs > > > Key: FALCON-2247 > URL: https://issues.apache.org/jira/browse/FALCON-2247 > Project: Falcon > Issue Type: Improvement > Components: extensions >Affects Versions: trunk >Reporter: Pracheer Agarwal >Assignee: Pracheer Agarwal >Priority: Minor > > Include status of the entities of the extensionJob in getDetailExtensionJobs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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 ] Pragya Mittal updated FALCON-2246: -- Description: jobName being unique in falcon system, we can expose an api to list all teh jobs in the system and what extension do they refer to. > 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 > > jobName being unique in falcon system, we can expose an api to list all teh > jobs in the system and what extension do they refer to. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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 ] Pragya Mittal updated FALCON-2246: -- Description: 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. (was: jobName being unique in falcon system, we can expose an api to list all teh jobs in the system and what extension do they refer to.) > 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 > > 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.4#6332)
[jira] [Created] (FALCON-2246) Api to list all the jobs in the system (and what extensions do they refer to)
Pragya Mittal created FALCON-2246: - Summary: 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FALCON-2245) Improve error message for submitting job during extension jobName check
[ https://issues.apache.org/jira/browse/FALCON-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2245: -- Description: job4 already exists but instead of saying job4 already exists , it says extension-example-3 already exists. falcon extension -submit -extensionName extension-example-3 -jobName job4 -file abc ERROR: Internal Server Error;Extension job with name: extension-example-3 already exists. > Improve error message for submitting job during extension jobName check > --- > > Key: FALCON-2245 > URL: https://issues.apache.org/jira/browse/FALCON-2245 > Project: Falcon > Issue Type: Bug > Components: extensions >Affects Versions: trunk >Reporter: Pragya Mittal > > job4 already exists but instead of saying job4 already exists , it says > extension-example-3 already exists. > falcon extension -submit -extensionName extension-example-3 -jobName job4 > -file abc > ERROR: Internal Server Error;Extension job with name: extension-example-3 > already exists. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FALCON-2245) Improve error message for submitting job during extension jobName check
Pragya Mittal created FALCON-2245: - Summary: Improve error message for submitting job during extension jobName check Key: FALCON-2245 URL: https://issues.apache.org/jira/browse/FALCON-2245 Project: Falcon Issue Type: Bug Components: extensions Affects Versions: trunk Reporter: Pragya Mittal -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FALCON-2243) Extension validation does not check job existance
Pragya Mittal created FALCON-2243:
-
Summary: Extension validation does not check job existance
Key: FALCON-2243
URL: https://issues.apache.org/jira/browse/FALCON-2243
Project: Falcon
Issue Type: Bug
Components: extensions
Affects Versions: trunk
Reporter: Pragya Mittal
Falcon extension validates job without checking whether job is there in the
system or not .
{noformat}
pragya.mittal@falcon1001:~$ falcon extension -validate -extensionName
extension-example -file abc -jobName abc
Validated successfully
pragya.mittal@falcon1001:~$ falcon extension -list -extensionName
extension-example
0
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FALCON-2242) Extension validate feature is broken
Pragya Mittal created FALCON-2242:
-
Summary: Extension validate feature is broken
Key: FALCON-2242
URL: https://issues.apache.org/jira/browse/FALCON-2242
Project: Falcon
Issue Type: Bug
Components: extensions
Affects Versions: trunk
Reporter: Pragya Mittal
{noformat}
dataqa@falcon1001:~$ falcon extension -validate -extensionName
extension-example -file abc
ERROR: Error in building the extension
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FALCON-2241) Job submission for registered extension is broken
Pragya Mittal created FALCON-2241:
-
Summary: 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
{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.4#6332)
[jira] [Created] (FALCON-2240) Enable/disable feature is broken
Pragya Mittal created FALCON-2240:
-
Summary: 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
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.4#6332)
[jira] [Created] (FALCON-2239) Falcon extension definition feature is broken
Pragya Mittal created FALCON-2239:
-
Summary: Falcon extension definition feature is broken
Key: FALCON-2239
URL: https://issues.apache.org/jira/browse/FALCON-2239
Project: Falcon
Issue Type: Bug
Components: extensions
Reporter: Pragya Mittal
Definition feature breaks with the following stack trace :
{noformat}
dataqa@falcon1001:~$ falcon extension -definition -extensionName
extension-example
ERROR: Internal Server Error;Resource path cannot be null or empty
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FALCON-2238) Falcon extension describe feature is broken
Pragya Mittal created FALCON-2238:
-
Summary: 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
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.4#6332)
[jira] [Updated] (FALCON-2224) Change return type of extension APIs to APIResult
[ https://issues.apache.org/jira/browse/FALCON-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2224: -- Description: Currently the return type of the extension API is String we should change it to APIResult. (was: Hi All, Currently the return type of the mentioned API is String we should change it to APIResult. Thanks Praveen) > Change return type of extension APIs to APIResult > - > > Key: FALCON-2224 > URL: https://issues.apache.org/jira/browse/FALCON-2224 > Project: Falcon > Issue Type: Bug >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > > Currently the return type of the extension API is String we should change it > to APIResult. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FALCON-2224) Change return type of extension APIs to APIResult
[ https://issues.apache.org/jira/browse/FALCON-2224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2224: -- Summary: Change return type of extension APIs to APIResult (was: Change return type of Register and Unregister API to ApiResult) > Change return type of extension APIs to APIResult > - > > Key: FALCON-2224 > URL: https://issues.apache.org/jira/browse/FALCON-2224 > Project: Falcon > Issue Type: Bug >Reporter: Praveen Adlakha >Assignee: Praveen Adlakha > > Hi All, > Currently the return type of the mentioned API is String we should change it > to APIResult. > Thanks > Praveen -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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
]
Pragya Mittal updated FALCON-2221:
--
Description:
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
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
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at
[jira] [Updated] (FALCON-2217) Job submission should fail with extension not registered.
[ https://issues.apache.org/jira/browse/FALCON-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2217: -- Description: In case extension is not registered job submission should fail with extension not registered. Instead it says the following : ERROR : File not found. was:In case extension is not registered job submission should fail with > Job submission should fail with extension not registered. > - > > Key: FALCON-2217 > URL: https://issues.apache.org/jira/browse/FALCON-2217 > Project: Falcon > Issue Type: Bug > Components: extensions >Affects Versions: trunk >Reporter: Pragya Mittal > > In case extension is not registered job submission should fail with extension > not registered. Instead it says the following : > ERROR : File not found. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FALCON-2217) Job submission should fail with extension not registered.
[ https://issues.apache.org/jira/browse/FALCON-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2217: -- Description: In case extension is not registered job submission should fail with > Job submission should fail with extension not registered. > - > > Key: FALCON-2217 > URL: https://issues.apache.org/jira/browse/FALCON-2217 > Project: Falcon > Issue Type: Bug > Components: extensions >Affects Versions: trunk >Reporter: Pragya Mittal > > In case extension is not registered job submission should fail with -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FALCON-2217) Job submission should fail with extension not registered.
Pragya Mittal created FALCON-2217: - Summary: Job submission should fail with extension not registered. Key: FALCON-2217 URL: https://issues.apache.org/jira/browse/FALCON-2217 Project: Falcon Issue Type: Bug Components: extensions Affects Versions: trunk Reporter: Pragya Mittal -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FALCON-2216) Recipe job submission api is non intutive
Pragya Mittal created FALCON-2216:
-
Summary: 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
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.4#6332)
[jira] [Updated] (FALCON-2215) Extension job submission throws non intuitive error
[ https://issues.apache.org/jira/browse/FALCON-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2215: -- Description: While submitting job fro a registered extension it fails with following error : dataqa@falcon1001:~$ falcon extension -submit -jobName sample -file /tmp/1234 -extensionName extension-example ERROR: File not found: > Extension job submission throws non intuitive error > --- > > Key: FALCON-2215 > URL: https://issues.apache.org/jira/browse/FALCON-2215 > Project: Falcon > Issue Type: Bug > Components: extensions >Affects Versions: trunk >Reporter: Pragya Mittal > > While submitting job fro a registered extension it fails with following error > : > dataqa@falcon1001:~$ falcon extension -submit -jobName sample -file /tmp/1234 > -extensionName extension-example > ERROR: File not found: -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FALCON-2215) Extension job submission throws non intuitive error
[ https://issues.apache.org/jira/browse/FALCON-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2215: -- Summary: Extension job submission throws non intuitive error (was: Extension job submissions throws non intuitive error) > Extension job submission throws non intuitive error > --- > > Key: FALCON-2215 > URL: https://issues.apache.org/jira/browse/FALCON-2215 > Project: Falcon > Issue Type: Bug > Components: extensions >Affects Versions: trunk >Reporter: Pragya Mittal > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FALCON-2215) Extension job submissions throws non intuitive error
Pragya Mittal created FALCON-2215: - Summary: Extension job submissions throws non intuitive error Key: FALCON-2215 URL: https://issues.apache.org/jira/browse/FALCON-2215 Project: Falcon Issue Type: Bug Components: extensions Affects Versions: trunk Reporter: Pragya Mittal -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FALCON-2214) Falcon extension registered without fully qualified hdfs path
Pragya Mittal created FALCON-2214:
-
Summary: 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
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.4#6332)
[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 ] Pragya Mittal updated FALCON-2213: -- Description: 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. > 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 > > 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.4#6332)
[jira] [Created] (FALCON-2213) Falcon logs does not contain response message when recipe operations are performed.
Pragya Mittal created FALCON-2213: - Summary: 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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
]
Pragya Mittal updated FALCON-2211:
--
Description:
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:
/mnt/falcon/prism/extensions/hive-mirroring/META:
hive-mirroring-properties.json
/mnt/falcon/prism/extensions/hive-mirroring/resources:
build runtime
/mnt/falcon/prism/extensions/hive-mirroring/resources/build:
/mnt/falcon/prism/extensions/hive-mirroring/resources/runtime:
hive-mirroring-secure-workflow.xml hive-mirroring-template.xml
hive-mirroring-workflow.xml
/mnt/falcon/prism/extensions/mirroring:
{noformat}
Thanks
Praveen
was:
Hi All,
If we start ExtensionService on prism it fails to start as trusted extensions
folder are empty.
Thanks
Praveen
[jira] [Resolved] (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 ] Pragya Mittal resolved FALCON-2162. --- Resolution: Duplicate > 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 > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FALCON-2162) Feed replication based on partition does not produce expected output
Pragya Mittal created FALCON-2162: - Summary: 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (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:comment-tabpanel=15529286#comment-15529286
]
Pragya Mittal commented on FALCON-2163:
---
Discovered as part of
org.apache.falcon.regression.prism.PrismFeedReplicationPartitionExpTest#normalTest2Source1TargetPartitionedSource
regression.
> 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
>
> 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
>
[jira] [Created] (FALCON-2163) Feed replication based on partition does not produce expected output
Pragya Mittal created FALCON-2163: - Summary: 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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 ] Pragya Mittal updated FALCON-2161: -- Description: For last instance of a process the entry exists in PENDING_INSTANCES list in db but the same is not reflected by slaAlert cli. > 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: Bug > Components: prism >Affects Versions: trunk >Reporter: Pragya Mittal >Assignee: Praveen Adlakha > > 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.4#6332)
[jira] [Created] (FALCON-2161) Process Sla API does not show sla for last instance
Pragya Mittal created FALCON-2161: - Summary: 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: Bug Components: prism Affects Versions: trunk Reporter: Pragya Mittal Assignee: Praveen Adlakha -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FALCON-2160) Update startup.properties to contain valid application services
Pragya Mittal created FALCON-2160:
-
Summary: Update startup.properties to contain valid application
services
Key: FALCON-2160
URL: https://issues.apache.org/jira/browse/FALCON-2160
Project: Falcon
Issue Type: Improvement
Components: prism
Affects Versions: trunk
Reporter: Pragya Mittal
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.4#6332)
[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
]
Pragya Mittal updated FALCON-2159:
--
Description:
The following configuration is missing from startup.properties
{noformat}
*.workflow.execution.listeners=org.apache.falcon.handler.SLAMonitoringHandler,\
org.apache.falcon.service.BacklogMetricEmitterService
{noformat}
> Update document for adding BackLogEmitterService
>
>
> Key: FALCON-2159
> URL: https://issues.apache.org/jira/browse/FALCON-2159
> Project: Falcon
> Issue Type: Improvement
> Components: prism
>Affects Versions: trunk
>Reporter: Pragya Mittal
>
> 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.4#6332)
[jira] [Created] (FALCON-2159) Update document for adding BackLogEmitterService
Pragya Mittal created FALCON-2159: - Summary: Update document for adding BackLogEmitterService Key: FALCON-2159 URL: https://issues.apache.org/jira/browse/FALCON-2159 Project: Falcon Issue Type: Improvement Components: prism Affects Versions: trunk Reporter: Pragya Mittal -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FALCON-2158) BacklogEmitterService does not delete instances from db
[ https://issues.apache.org/jira/browse/FALCON-2158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2158: -- Description: 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, BACKLOG_METRIC is not getting updated as expected and also backlog should reduce but it is also not happening. > BacklogEmitterService does not delete instances from db > --- > > Key: FALCON-2158 > URL: https://issues.apache.org/jira/browse/FALCON-2158 > Project: Falcon > Issue Type: Bug > Components: prism >Affects Versions: trunk >Reporter: Pragya Mittal > > 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, BACKLOG_METRIC is not getting updated as expected > and also backlog should reduce but it is also not happening. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FALCON-2157) Pending insances are not getting deleted from database
[ https://issues.apache.org/jira/browse/FALCON-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2157: -- Description: 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. was: 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 Entries are deleted but again getting created. > Pending insances are not getting deleted from database > --- > > Key: FALCON-2157 > URL: https://issues.apache.org/jira/browse/FALCON-2157 > Project: Falcon > Issue Type: Bug > Components: prism >Affects Versions: trunk >Reporter: Pragya Mittal > > 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.4#6332)
[jira] [Updated] (FALCON-2157) Pending insances are not getting deleted from database
[ https://issues.apache.org/jira/browse/FALCON-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2157: -- Summary: Pending insances are not getting deleted from database (was: Pending insances are not deleted from database ) > Pending insances are not getting deleted from database > --- > > Key: FALCON-2157 > URL: https://issues.apache.org/jira/browse/FALCON-2157 > Project: Falcon > Issue Type: Bug > Components: prism >Affects Versions: trunk >Reporter: Pragya Mittal > > 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 > Entries are deleted but again getting created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FALCON-2157) Pending insances are not deleted from database
[ https://issues.apache.org/jira/browse/FALCON-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2157: -- Summary: Pending insances are not deleted from database (was: Pending instances are not deleted from database) > Pending insances are not deleted from database > --- > > Key: FALCON-2157 > URL: https://issues.apache.org/jira/browse/FALCON-2157 > Project: Falcon > Issue Type: Bug > Components: prism >Affects Versions: trunk >Reporter: Pragya Mittal > > 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 > Entries are deleted but again getting created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FALCON-2158) BacklogEmitterService does not delete instances from db
Pragya Mittal created FALCON-2158: - Summary: BacklogEmitterService does not delete instances from db Key: FALCON-2158 URL: https://issues.apache.org/jira/browse/FALCON-2158 Project: Falcon Issue Type: Bug Components: prism Affects Versions: trunk Reporter: Pragya Mittal -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FALCON-2157) Pending insances are not deleted from database when lookahead window is same as entity frequency
[ https://issues.apache.org/jira/browse/FALCON-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2157: -- Description: 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 Entries are deleted but again getting created. was: 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 > Pending insances are not deleted from database when lookahead window is same > as entity frequency > > > Key: FALCON-2157 > URL: https://issues.apache.org/jira/browse/FALCON-2157 > Project: Falcon > Issue Type: Bug > Components: prism >Affects Versions: trunk >Reporter: Pragya Mittal > > 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 > Entries are deleted but again getting created. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FALCON-2157) Pending insances are not deleted from database when lookahead window is same as entity frequency
[ https://issues.apache.org/jira/browse/FALCON-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2157: -- Summary: Pending insances are not deleted from database when lookahead window is same as entity frequency (was: EntitySlaAlertService fails when lookahead window is same as entity frequency) > Pending insances are not deleted from database when lookahead window is same > as entity frequency > > > Key: FALCON-2157 > URL: https://issues.apache.org/jira/browse/FALCON-2157 > Project: Falcon > Issue Type: Bug > Components: prism >Affects Versions: trunk >Reporter: Pragya Mittal > > 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FALCON-2157) EntitySlaAlertService fails when lookahead window is same as entity frequency
[ https://issues.apache.org/jira/browse/FALCON-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2157: -- Description: 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 > EntitySlaAlertService fails when lookahead window is same as entity frequency > - > > Key: FALCON-2157 > URL: https://issues.apache.org/jira/browse/FALCON-2157 > Project: Falcon > Issue Type: Bug > Components: prism >Affects Versions: trunk >Reporter: Pragya Mittal > > 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 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FALCON-2157) EntitySlaAlertService fails when lookahead window is same as entity frequency
Pragya Mittal created FALCON-2157: - Summary: EntitySlaAlertService fails when lookahead window is same as entity frequency Key: FALCON-2157 URL: https://issues.apache.org/jira/browse/FALCON-2157 Project: Falcon Issue Type: Bug Components: prism Affects Versions: trunk Reporter: Pragya Mittal -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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 ] Pragya Mittal updated FALCON-2156: -- Description: On enabling LogMover service, log mover listener attains deadlock and gets stuck at the first SUCCEEDED message received via WorkflowJobEndNotificationService. (was: On enabling LogMover service, log mover listener attains deadlock and gets stuck at the first SUCCEEDED message received via ) > Logmover listener gets stuck while listening to > WorkflowJobEndNotificationService > - > > Key: FALCON-2156 > URL: https://issues.apache.org/jira/browse/FALCON-2156 > Project: Falcon > Issue Type: Bug > Components: messaging >Affects Versions: trunk >Reporter: Pragya Mittal > > 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.4#6332)
[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 ] Pragya Mittal updated FALCON-2156: -- Description: On enabling LogMover service, log mover listener attains deadlock and gets stuck at the first SUCCEEDED message received via > Logmover listener gets stuck while listening to > WorkflowJobEndNotificationService > - > > Key: FALCON-2156 > URL: https://issues.apache.org/jira/browse/FALCON-2156 > Project: Falcon > Issue Type: Bug > Components: messaging >Affects Versions: trunk >Reporter: Pragya Mittal > > On enabling LogMover service, log mover listener attains deadlock and gets > stuck at the first SUCCEEDED message received via -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FALCON-2156) Logmover listener gets stuck while listening to WorkflowJobEndNotificationService
Pragya Mittal created FALCON-2156: - Summary: Logmover listener gets stuck while listening to WorkflowJobEndNotificationService Key: FALCON-2156 URL: https://issues.apache.org/jira/browse/FALCON-2156 Project: Falcon Issue Type: Bug Components: messaging Affects Versions: trunk Reporter: Pragya Mittal -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FALCON-2155) LogMover service fails to move logs in distributed mode
Pragya Mittal created FALCON-2155: - Summary: LogMover service fails to move logs in distributed mode Key: FALCON-2155 URL: https://issues.apache.org/jira/browse/FALCON-2155 Project: Falcon Issue Type: Bug Components: prism Affects Versions: trunk Reporter: Pragya Mittal LogMover service moves succeeded/failed logs but it is not doing so with the current trunk build. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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 ] Pragya Mittal updated FALCON-2154: -- Description: Currently backlog emitter service does not fall back to zero when entity is deleted from config store. It attains a static value forever. > 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: Bug > Components: messaging >Affects Versions: trunk >Reporter: Pragya Mittal >Assignee: Praveen Adlakha > > 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.4#6332)
[jira] [Created] (FALCON-2154) On deleting entity backlog emitter does not go back to zero
Pragya Mittal created FALCON-2154: - Summary: 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: Bug Components: messaging Affects Versions: trunk Reporter: Pragya Mittal -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FALCON-2150) Instances run in random order when dependencies are met
[ https://issues.apache.org/jira/browse/FALCON-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2150: -- Description: If 5 instances of process are in WAITING state and at some point their dependencies are met, then they should ideally run in defined order. But this is not happening as of now. Please note that the db used is mysql and not derby. > Instances run in random order when dependencies are met > --- > > Key: FALCON-2150 > URL: https://issues.apache.org/jira/browse/FALCON-2150 > Project: Falcon > Issue Type: Bug > Components: prism >Affects Versions: trunk >Reporter: Pragya Mittal >Assignee: Praveen Adlakha > > If 5 instances of process are in WAITING state and at some point their > dependencies are met, then they should ideally run in defined order. But this > is not happening as of now. Please note that the db used is mysql and not > derby. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FALCON-2150) Instances run in random order when dependencies are met
Pragya Mittal created FALCON-2150: - Summary: Instances run in random order when dependencies are met Key: FALCON-2150 URL: https://issues.apache.org/jira/browse/FALCON-2150 Project: Falcon Issue Type: Bug Components: prism Affects Versions: trunk Reporter: Pragya Mittal -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FALCON-2150) Instances run in random order when dependencies are met
[ https://issues.apache.org/jira/browse/FALCON-2150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2150: -- Assignee: Praveen Adlakha > Instances run in random order when dependencies are met > --- > > Key: FALCON-2150 > URL: https://issues.apache.org/jira/browse/FALCON-2150 > Project: Falcon > Issue Type: Bug > Components: prism >Affects Versions: trunk >Reporter: Pragya Mittal >Assignee: Praveen Adlakha > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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 ] Pragya Mittal updated FALCON-2148: -- Assignee: Praveen Adlakha > 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 > > 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.4#6332)
[jira] [Updated] (FALCON-2149) On deleting process entries still exist in BACKLOG_METRIC
[ https://issues.apache.org/jira/browse/FALCON-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2149: -- Assignee: Praveen Adlakha > On deleting process entries still exist in BACKLOG_METRIC > - > > Key: FALCON-2149 > URL: https://issues.apache.org/jira/browse/FALCON-2149 > Project: Falcon > Issue Type: Bug > Components: prism >Affects Versions: trunk >Reporter: Pragya Mittal >Assignee: Praveen Adlakha > > On deleting process entries still exist in BACKLOG_METRIC which should not be > the case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FALCON-2149) On deleting process entries still exist in BACKLOG_METRIC
Pragya Mittal created FALCON-2149: - Summary: On deleting process entries still exist in BACKLOG_METRIC Key: FALCON-2149 URL: https://issues.apache.org/jira/browse/FALCON-2149 Project: Falcon Issue Type: Bug Components: prism Affects Versions: trunk Reporter: Pragya Mittal On deleting process entries still exist in BACKLOG_METRIC which should not be the case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FALCON-2148) Entries not removed from sla list when instance succeeds
Pragya Mittal created FALCON-2148: - Summary: 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 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.4#6332)
[jira] [Created] (FALCON-2147) Excess logging due to SlaMonitoring service and Backlog emitter service
Pragya Mittal created FALCON-2147: - Summary: 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 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.4#6332)
[jira] [Created] (FALCON-2146) EntitySlaAlertService runs only once irrespective of the configured frequency
Pragya Mittal created FALCON-2146:
-
Summary: 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
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.4#6332)
[jira] [Commented] (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:comment-tabpanel=15456146#comment-15456146 ] Pragya Mittal commented on FALCON-2133: --- Thanks [~murali.msse] > 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 > > > 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.4#6332)
[jira] [Commented] (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:comment-tabpanel=15438873#comment-15438873
]
Pragya Mittal commented on FALCON-2120:
---
Thanks [~Praveen] for your contribution.
> 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
>
> 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.4#6332)
[jira] [Commented] (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:comment-tabpanel=15438867#comment-15438867 ] Pragya Mittal commented on FALCON-2127: --- Thanks [~murali.msse] for your contribution. > 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 > > > 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.4#6332)
[jira] [Created] (FALCON-2128) Status api shows timeout instances as failed
Pragya Mittal created FALCON-2128: - Summary: 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 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.4#6332)
[jira] [Commented] (FALCON-2127) Fix the falcon regression compilation issue and delete the depricated recipe test cases
[ https://issues.apache.org/jira/browse/FALCON-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15434218#comment-15434218 ] Pragya Mittal commented on FALCON-2127: --- [~Praveen] With falcon-0.10 recipe are available via api as well as client. Also the cli command for invoking recipe has changed. This jira is raised for the same. > Fix the falcon regression compilation issue and delete the depricated 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 > > > 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.4#6332)
[jira] [Updated] (FALCON-2126) Extra logging info in falcon logs
[
https://issues.apache.org/jira/browse/FALCON-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pragya Mittal updated FALCON-2126:
--
Assignee: Praveen Adlakha
> Extra logging info in falcon logs
> -
>
> Key: FALCON-2126
> URL: https://issues.apache.org/jira/browse/FALCON-2126
> Project: Falcon
> Issue Type: Bug
> Components: process
>Affects Versions: trunk, 1.0
>Reporter: Pragya Mittal
>Assignee: Praveen Adlakha
>
> As part of FALCON-2039 post-processing action is disabled. Logs contain the
> following information at too many places. It should be available at required
> places so that info is meaningful.
> {noformat}
> 2016-08-23 12:27:16,471 INFO - [ActiveMQ Session Task-2:] ~ Sleeing, no
> capacity in threadpool (LogMoverService:90)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FALCON-2126) Extra logging info in falcon logs
Pragya Mittal created FALCON-2126:
-
Summary: Extra logging info in falcon logs
Key: FALCON-2126
URL: https://issues.apache.org/jira/browse/FALCON-2126
Project: Falcon
Issue Type: Bug
Components: process
Affects Versions: trunk, 1.0
Reporter: Pragya Mittal
As part of FALCON-2039 post-processing action is disabled. Logs contain the
following information at too many places. It should be available at required
places so that info is meaningful.
{noformat}
2016-08-23 12:27:16,471 INFO - [ActiveMQ Session Task-2:] ~ Sleeing, no
capacity in threadpool (LogMoverService:90)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FALCON-2125) Feed replication fails due to failed post processing action missing in workflow
[
https://issues.apache.org/jira/browse/FALCON-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15432829#comment-15432829
]
Pragya Mittal commented on FALCON-2125:
---
Feed definition is :
{noformat}
minutes(5)
UTC
{noformat}
> Feed replication fails due to failed post processing action missing in
> workflow
> ---
>
> Key: FALCON-2125
> URL: https://issues.apache.org/jira/browse/FALCON-2125
> Project: Falcon
> Issue Type: Bug
> Components: feed, process
>Affects Versions: trunk, 1.0
>Reporter: Pragya Mittal
>Assignee: Praveen Adlakha
>
> https://issues.apache.org/jira/browse/FALCON-2039 introduced threadpool
> capacity for log moving in server. I have scheduled a feed (replication) and
> it is failing with failed post processing.
> Workflow:
> {noformat}
>
> name="FALCON_FEED_REPLICATION_A7769e4e0-bf3ce415">
>
>
>
> ${jobTracker}
> ${nameNode}
>
>
> mapred.job.queue.name
> ${queueName}
>
>
> oozie.launcher.mapred.job.priority
> ${jobPriority}
>
>
> oozie.action.sharelib.for.java
> hcatalog
>
>
> oozie.launcher.oozie.libpath
> ${wf:conf(falcon.libpath)}
>
>
>
> org.apache.falcon.workflow.LateDataHandler
> -out
> ${logDir}/latedata/${nominalTime}/${srcClusterName}
> -paths
> ${falconInPaths}
> -falconInputNames
> ${falconInputNames}
> -falconInputFeedStorageTypes
> ${falconInputFeedStorageTypes}
> -out
> ${logDir}/latedata/${nominalTime}/${srcClusterName}
>
>
>
>
>
>
>
> ${jobTracker}
> ${nameNode}
>
>
>
> oozie.launcher.mapreduce.job.user.classpath.first
> true
>
>
> mapred.job.queue.name
> ${queueName}
>
>
> oozie.launcher.mapred.job.priority
> ${jobPriority}
>
>
> oozie.action.sharelib.for.java
> distcp
>
>
> oozie.launcher.oozie.libpath
> ${wf:conf(falcon.libpath)}
>
>
>
> org.apache.falcon.replication.FeedReplicator
> -Dfalcon.include.path=${sourceRelativePaths}
> -Dmapred.job.queue.name=${queueName}
> -Dmapred.job.priority=${jobPriority}
> -maxMaps
> ${maxMaps}
> -mapBandwidth
> ${mapBandwidth}
> -sourcePaths
> ${distcpSourcePaths}
> -targetPath
> ${distcpTargetPaths}
> -falconFeedStorageType
> ${falconFeedStorageType}
> -availabilityFlag
> ${availabilityFlag == 'NA' ? NA :
> availabilityFlag}
> -counterLogDir
> ${logDir}/job-${nominalTime}/${srcClusterName == 'NA' ? '' :
> srcClusterName}
>
>
>
>
>
> Workflow failed, error
> message[${wf:errorMessage(wf:lastErrorNode())}]
>
>
>
> {noformat}
> Oozie logs :
> {noformat}
> 2016-08-23 18:27:36,856 ERROR pool-6-thread-2 SubmitXCommand -
> SERVER[8RPCG32.corp.inmobi.com] USER[pragya.mittal] GROUP[-] TOKEN[]
> APP[FALCON_FEED_REPLICATION_A7769e4e0-bf3ce415_A7769e4e0-adb310ea]
> JOB[004-160823182134602-oozie-oozi-C]
> ACTION[004-160823182134602-oozie-oozi-C@1] XException,
> org.apache.oozie.command.CommandException: E0708: Invalid transition, node
> [pre-processing] transition [failed-post-processing]
> at
> org.apache.oozie.command.wf.SubmitXCommand.execute(SubmitXCommand.java:272)
> at
> org.apache.oozie.command.wf.SubmitXCommand.execute(SubmitXCommand.java:76)
> at org.apache.oozie.command.XCommand.call(XCommand.java:286)
> at
> org.apache.oozie.DagEngine.submitJobFromCoordinator(DagEngine.java:138)
> at
>
[jira] [Updated] (FALCON-2125) Feed replication fails due to failed post processing action missing in workflow
[
https://issues.apache.org/jira/browse/FALCON-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pragya Mittal updated FALCON-2125:
--
Summary: Feed replication fails due to failed post processing action
missing in workflow (was: Feed fails due to no capacity in threadpool)
> Feed replication fails due to failed post processing action missing in
> workflow
> ---
>
> Key: FALCON-2125
> URL: https://issues.apache.org/jira/browse/FALCON-2125
> Project: Falcon
> Issue Type: Bug
> Components: feed, process
>Affects Versions: trunk, 1.0
>Reporter: Pragya Mittal
>Assignee: Praveen Adlakha
>
> https://issues.apache.org/jira/browse/FALCON-2039 introduced threadpool
> capacity for log moving in server. I have scheduled a feed (replication) and
> it is failing with failed post processing.
> Workflow:
> {noformat}
>
> name="FALCON_FEED_REPLICATION_A7769e4e0-bf3ce415">
>
>
>
> ${jobTracker}
> ${nameNode}
>
>
> mapred.job.queue.name
> ${queueName}
>
>
> oozie.launcher.mapred.job.priority
> ${jobPriority}
>
>
> oozie.action.sharelib.for.java
> hcatalog
>
>
> oozie.launcher.oozie.libpath
> ${wf:conf(falcon.libpath)}
>
>
>
> org.apache.falcon.workflow.LateDataHandler
> -out
> ${logDir}/latedata/${nominalTime}/${srcClusterName}
> -paths
> ${falconInPaths}
> -falconInputNames
> ${falconInputNames}
> -falconInputFeedStorageTypes
> ${falconInputFeedStorageTypes}
> -out
> ${logDir}/latedata/${nominalTime}/${srcClusterName}
>
>
>
>
>
>
>
> ${jobTracker}
> ${nameNode}
>
>
>
> oozie.launcher.mapreduce.job.user.classpath.first
> true
>
>
> mapred.job.queue.name
> ${queueName}
>
>
> oozie.launcher.mapred.job.priority
> ${jobPriority}
>
>
> oozie.action.sharelib.for.java
> distcp
>
>
> oozie.launcher.oozie.libpath
> ${wf:conf(falcon.libpath)}
>
>
>
> org.apache.falcon.replication.FeedReplicator
> -Dfalcon.include.path=${sourceRelativePaths}
> -Dmapred.job.queue.name=${queueName}
> -Dmapred.job.priority=${jobPriority}
> -maxMaps
> ${maxMaps}
> -mapBandwidth
> ${mapBandwidth}
> -sourcePaths
> ${distcpSourcePaths}
> -targetPath
> ${distcpTargetPaths}
> -falconFeedStorageType
> ${falconFeedStorageType}
> -availabilityFlag
> ${availabilityFlag == 'NA' ? NA :
> availabilityFlag}
> -counterLogDir
> ${logDir}/job-${nominalTime}/${srcClusterName == 'NA' ? '' :
> srcClusterName}
>
>
>
>
>
> Workflow failed, error
> message[${wf:errorMessage(wf:lastErrorNode())}]
>
>
>
> {noformat}
> Oozie logs :
> {noformat}
> 2016-08-23 18:27:36,856 ERROR pool-6-thread-2 SubmitXCommand -
> SERVER[8RPCG32.corp.inmobi.com] USER[pragya.mittal] GROUP[-] TOKEN[]
> APP[FALCON_FEED_REPLICATION_A7769e4e0-bf3ce415_A7769e4e0-adb310ea]
> JOB[004-160823182134602-oozie-oozi-C]
> ACTION[004-160823182134602-oozie-oozi-C@1] XException,
> org.apache.oozie.command.CommandException: E0708: Invalid transition, node
> [pre-processing] transition [failed-post-processing]
> at
> org.apache.oozie.command.wf.SubmitXCommand.execute(SubmitXCommand.java:272)
> at
> org.apache.oozie.command.wf.SubmitXCommand.execute(SubmitXCommand.java:76)
> at org.apache.oozie.command.XCommand.call(XCommand.java:286)
> at
> org.apache.oozie.DagEngine.submitJobFromCoordinator(DagEngine.java:138)
> at
> org.apache.oozie.command.coord.CoordActionStartXCommand.execute(CoordActionStartXCommand.java:214)
> at
> org.apache.oozie.command.coord.CoordActionStartXCommand.execute(CoordActionStartXCommand.java:63)
> at
[jira] [Updated] (FALCON-2125) Feed fails due to no capacity in threadpool
[
https://issues.apache.org/jira/browse/FALCON-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pragya Mittal updated FALCON-2125:
--
Description:
https://issues.apache.org/jira/browse/FALCON-2039 introduced threadpool
capacity for log moving in server. I have scheduled a feed (replication) and it
is failing with failed post processing.
Workflow:
{noformat}
${jobTracker}
${nameNode}
mapred.job.queue.name
${queueName}
oozie.launcher.mapred.job.priority
${jobPriority}
oozie.action.sharelib.for.java
hcatalog
oozie.launcher.oozie.libpath
${wf:conf(falcon.libpath)}
org.apache.falcon.workflow.LateDataHandler
-out
${logDir}/latedata/${nominalTime}/${srcClusterName}
-paths
${falconInPaths}
-falconInputNames
${falconInputNames}
-falconInputFeedStorageTypes
${falconInputFeedStorageTypes}
-out
${logDir}/latedata/${nominalTime}/${srcClusterName}
${jobTracker}
${nameNode}
oozie.launcher.mapreduce.job.user.classpath.first
true
mapred.job.queue.name
${queueName}
oozie.launcher.mapred.job.priority
${jobPriority}
oozie.action.sharelib.for.java
distcp
oozie.launcher.oozie.libpath
${wf:conf(falcon.libpath)}
org.apache.falcon.replication.FeedReplicator
-Dfalcon.include.path=${sourceRelativePaths}
-Dmapred.job.queue.name=${queueName}
-Dmapred.job.priority=${jobPriority}
-maxMaps
${maxMaps}
-mapBandwidth
${mapBandwidth}
-sourcePaths
${distcpSourcePaths}
-targetPath
${distcpTargetPaths}
-falconFeedStorageType
${falconFeedStorageType}
-availabilityFlag
${availabilityFlag == 'NA' ? NA :
availabilityFlag}
-counterLogDir
${logDir}/job-${nominalTime}/${srcClusterName == 'NA' ? '' :
srcClusterName}
Workflow failed, error
message[${wf:errorMessage(wf:lastErrorNode())}]
{noformat}
Oozie logs :
{noformat}
2016-08-23 18:27:36,856 ERROR pool-6-thread-2 SubmitXCommand -
SERVER[8RPCG32.corp.inmobi.com] USER[pragya.mittal] GROUP[-] TOKEN[]
APP[FALCON_FEED_REPLICATION_A7769e4e0-bf3ce415_A7769e4e0-adb310ea]
JOB[004-160823182134602-oozie-oozi-C]
ACTION[004-160823182134602-oozie-oozi-C@1] XException,
org.apache.oozie.command.CommandException: E0708: Invalid transition, node
[pre-processing] transition [failed-post-processing]
at
org.apache.oozie.command.wf.SubmitXCommand.execute(SubmitXCommand.java:272)
at
org.apache.oozie.command.wf.SubmitXCommand.execute(SubmitXCommand.java:76)
at org.apache.oozie.command.XCommand.call(XCommand.java:286)
at
org.apache.oozie.DagEngine.submitJobFromCoordinator(DagEngine.java:138)
at
org.apache.oozie.command.coord.CoordActionStartXCommand.execute(CoordActionStartXCommand.java:214)
at
org.apache.oozie.command.coord.CoordActionStartXCommand.execute(CoordActionStartXCommand.java:63)
at org.apache.oozie.command.XCommand.call(XCommand.java:286)
at org.apache.oozie.command.XCommand.call(XCommand.java:356)
at
org.apache.oozie.command.coord.CoordActionReadyXCommand.execute(CoordActionReadyXCommand.java:128)
at
org.apache.oozie.command.coord.CoordActionReadyXCommand.execute(CoordActionReadyXCommand.java:42)
at org.apache.oozie.command.XCommand.call(XCommand.java:286)
at org.apache.oozie.command.XCommand.call(XCommand.java:356)
at
org.apache.oozie.command.coord.CoordActionInputCheckXCommand.execute(CoordActionInputCheckXCommand.java:235)
at
org.apache.oozie.command.coord.CoordActionInputCheckXCommand.execute(CoordActionInputCheckXCommand.java:71)
at org.apache.oozie.command.XCommand.call(XCommand.java:286)
at
org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
at
[jira] [Updated] (FALCON-2125) Feed fails due to no capacity in threadpool
[
https://issues.apache.org/jira/browse/FALCON-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pragya Mittal updated FALCON-2125:
--
Summary: Feed fails due to no capacity in threadpool (was: Entities fails
due to no capacity in threadpool)
> Feed fails due to no capacity in threadpool
> ---
>
> Key: FALCON-2125
> URL: https://issues.apache.org/jira/browse/FALCON-2125
> Project: Falcon
> Issue Type: Bug
> Components: feed, process
>Affects Versions: trunk, 1.0
>Reporter: Pragya Mittal
>
> https://issues.apache.org/jira/browse/FALCON-2039 introduced threadpool
> capacity for log moving in server. I have scheduled a feed (replication) and
> it is failing with threadpool capacity.
> {noformat}
> 2016-08-23 12:41:35,420 INFO - [ActiveMQ Session Task-2:] ~ Sleeing, no
> capacity in threadpool (LogMoverService:90)
> {noformat}
> I have only 1 feed in my environment so this should have been handled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FALCON-2125) Entities fails due to no capacity in threadpool
Pragya Mittal created FALCON-2125:
-
Summary: Entities fails due to no capacity in threadpool
Key: FALCON-2125
URL: https://issues.apache.org/jira/browse/FALCON-2125
Project: Falcon
Issue Type: Bug
Components: feed, process
Affects Versions: trunk, 1.0
Reporter: Pragya Mittal
https://issues.apache.org/jira/browse/FALCON-2039 introduced threadpool
capacity for log moving in server. I have scheduled a feed (replication) and it
is failing with threadpool capacity.
{noformat}
2016-08-23 12:41:35,420 INFO - [ActiveMQ Session Task-2:] ~ Sleeing, no
capacity in threadpool (LogMoverService:90)
{noformat}
I have only 1 feed in my environment so this should have been handled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FALCON-2124) Incorrect order of application services defined in startup.properties
Pragya Mittal created FALCON-2124:
-
Summary: Incorrect order of application services defined in
startup.properties
Key: FALCON-2124
URL: https://issues.apache.org/jira/browse/FALCON-2124
Project: Falcon
Issue Type: Bug
Components: prism
Affects Versions: trunk
Reporter: Pragya Mittal
The expected order in startup.properties is as follows :
{noformat}
*.application.services=org.apache.falcon.security.AuthenticationInitializationService,\
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.metrics.MetricNotificationService,\
org.apache.falcon.service.EntitySLAAlertService,\
org.apache.falcon.service.BacklogMetricEmitterService
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (FALCON-1749) Instance status does not show instances if entity is deleted from one of the colos
[
https://issues.apache.org/jira/browse/FALCON-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pragya Mittal reopened FALCON-1749:
---
Reopening as the patch is reverted.
> Instance status does not show instances if entity is deleted from one of the
> colos
> --
>
> Key: FALCON-1749
> URL: https://issues.apache.org/jira/browse/FALCON-1749
> Project: Falcon
> Issue Type: Bug
> Components: prism, scheduler
>Affects Versions: 0.9
>Reporter: Pragya Mittal
>Assignee: Praveen Adlakha
> Fix For: trunk, 0.10
>
>
> Lets say I have a process with two clusters ua1 and ua2 and process gets
> deleted from ua1. If user fires status request from prism , it should display
> instances from ua2. Currently this is not happening. End result is :
> {noformat}
> dataqa@lda01:~$ falcon entity -type process -status -name processMerlinNative
> ua1/org.apache.falcon.FalconWebException::null
> ua2/RUNNING
> dataqa@lda01:~$ falcon instance -type process -status -name
> processMerlinNative
> ERROR: Bad Request;ua1/processMerlinNative (PROCESS) not found
> ua2/STATUS
> {noformat}
> Although giving colo will show the expected result
> {noformat}
> dataqa@lda01:~$ falcon instance -type process -status -name
> processMerlinNative -colo ua2
> 2016-01-14T09:08Z ProcessMultipleClustersTest-corp-2a8c -
> SUCCEEDED 2016-01-14T10:11Z 2016-01-14T10:12Z -
> http://8RPCG32.corp.inmobi.com:11000/oozie?job=880-160113111840703-oozie-oozi-W
> actions:
> hdfscommands OK -
> aggregator SUCCEEDED
> http://8RPCG32.corp.inmobi.com:8088/proxy/application_1452664055458_1798/
> 2016-01-14T09:07Z ProcessMultipleClustersTest-corp-2a8c -
> SUCCEEDED 2016-01-14T10:02Z 2016-01-14T10:03Z -
> http://8RPCG32.corp.inmobi.com:11000/oozie?job=878-160113111840703-oozie-oozi-W
> actions:
> hdfscommands OK -
> aggregator SUCCEEDED
> http://8RPCG32.corp.inmobi.com:8088/proxy/application_1452664055458_1577/
> 2016-01-14T09:06Z ProcessMultipleClustersTest-corp-2a8c -
> SUCCEEDED 2016-01-14T09:56Z 2016-01-14T09:58Z -
> http://8RPCG32.corp.inmobi.com:11000/oozie?job=876-160113111840703-oozie-oozi-W
> actions:
> hdfscommands OK -
> aggregator SUCCEEDED
> http://8RPCG32.corp.inmobi.com:8088/proxy/application_1452664055458_1444/
> Additional Information:
> Response: ua2/STATUS
> Request Id: ua2/1093419868@qtp-1214810373-11 -
> b81926ad-d244-45ab-9716-02d9b72abbee
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FALCON-2088) Entity submission fails with EntityNotRegisteredException in distributed mode
[
https://issues.apache.org/jira/browse/FALCON-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pragya Mittal updated FALCON-2088:
--
Summary: Entity submission fails with EntityNotRegisteredException in
distributed mode (was: Entity submission fails with
EntityNotRegisteredException)
> Entity submission fails with EntityNotRegisteredException in distributed mode
> -
>
> Key: FALCON-2088
> URL: https://issues.apache.org/jira/browse/FALCON-2088
> Project: Falcon
> Issue Type: Bug
> Components: feed, prism, process
>Affects Versions: trunk, 0.10
>Reporter: Pragya Mittal
>Priority: Blocker
>
> Feed/Process submission fails with following error :
> dataqa@falcon1001:~$ falcon entity -type feed -submit -file feed.xml
> ERROR: Bad Request;ProcessInstanceResumeTest-raaw-logs16-8a46ee1b (feed) not
> found
> {noformat}
> 2016-07-19 07:14:08,901 INFO - [2069246737@qtp-1229202732-5 -
> b657de76-c76f-42a0-bc87-12189603862e:dataqa:POST//entities/submit/feed] ~
> Logging in dataqa (CurrentUser:65)
> 2016-07-19 07:14:08,901 INFO - [2069246737@qtp-1229202732-5 -
> b657de76-c76f-42a0-bc87-12189603862e:dataqa:POST//entities/submit/feed] ~
> Request from authenticated user: dataqa, URL=/api/entities/submit/feed, doAs
> user: null (FalconAuthenticationFilter:185)
> 2016-07-19 07:14:08,909 INFO - [2069246737@qtp-1229202732-5 -
> b657de76-c76f-42a0-bc87-12189603862e:dataqa:POST//entities/submit/feed] ~
> Parsed Entity: ProcessInstanceResumeTest-raaw-logs16-8a46ee1b
> (EntityParser:94)
> 2016-07-19 07:14:08,909 WARN - [2069246737@qtp-1229202732-5 -
> b657de76-c76f-42a0-bc87-12189603862e:dataqa:POST//entities/submit/feed] ~
> ProcessInstanceResumeTest-raaw-logs16-8a46ee1b (FEED) not found
> (AbstractEntityManager:181)
> org.apache.falcon.entity.EntityNotRegisteredException:
> ProcessInstanceResumeTest-raaw-logs16-8a46ee1b (FEED) not found
> at org.apache.falcon.entity.EntityUtil.getEntity(EntityUtil.java:149)
> at
> org.apache.falcon.resource.AbstractEntityManager.getApplicableColos(AbstractEntityManager.java:174)
> at
> org.apache.falcon.resource.proxy.SchedulableEntityManagerProxy.submit_aroundBody2(SchedulableEntityManagerProxy.java:164)
> at
> org.apache.falcon.resource.proxy.SchedulableEntityManagerProxy$AjcClosure3.run(SchedulableEntityManagerProxy.java:1)
> at
> org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149)
> at
> org.apache.falcon.aspect.AbstractFalconAspect.logAroundMonitored(AbstractFalconAspect.java:51)
> at
> org.apache.falcon.resource.proxy.SchedulableEntityManagerProxy.submit(SchedulableEntityManagerProxy.java:156)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> {nofromat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FALCON-2088) Entity submission fails with EntityNotRegisteredException
[
https://issues.apache.org/jira/browse/FALCON-2088?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pragya Mittal updated FALCON-2088:
--
Priority: Blocker (was: Major)
> Entity submission fails with EntityNotRegisteredException
> -
>
> Key: FALCON-2088
> URL: https://issues.apache.org/jira/browse/FALCON-2088
> Project: Falcon
> Issue Type: Bug
> Components: feed, prism, process
>Affects Versions: trunk, 0.10
>Reporter: Pragya Mittal
>Priority: Blocker
>
> Feed/Process submission fails with following error :
> dataqa@falcon1001:~$ falcon entity -type feed -submit -file feed.xml
> ERROR: Bad Request;ProcessInstanceResumeTest-raaw-logs16-8a46ee1b (feed) not
> found
> {noformat}
> 2016-07-19 07:14:08,901 INFO - [2069246737@qtp-1229202732-5 -
> b657de76-c76f-42a0-bc87-12189603862e:dataqa:POST//entities/submit/feed] ~
> Logging in dataqa (CurrentUser:65)
> 2016-07-19 07:14:08,901 INFO - [2069246737@qtp-1229202732-5 -
> b657de76-c76f-42a0-bc87-12189603862e:dataqa:POST//entities/submit/feed] ~
> Request from authenticated user: dataqa, URL=/api/entities/submit/feed, doAs
> user: null (FalconAuthenticationFilter:185)
> 2016-07-19 07:14:08,909 INFO - [2069246737@qtp-1229202732-5 -
> b657de76-c76f-42a0-bc87-12189603862e:dataqa:POST//entities/submit/feed] ~
> Parsed Entity: ProcessInstanceResumeTest-raaw-logs16-8a46ee1b
> (EntityParser:94)
> 2016-07-19 07:14:08,909 WARN - [2069246737@qtp-1229202732-5 -
> b657de76-c76f-42a0-bc87-12189603862e:dataqa:POST//entities/submit/feed] ~
> ProcessInstanceResumeTest-raaw-logs16-8a46ee1b (FEED) not found
> (AbstractEntityManager:181)
> org.apache.falcon.entity.EntityNotRegisteredException:
> ProcessInstanceResumeTest-raaw-logs16-8a46ee1b (FEED) not found
> at org.apache.falcon.entity.EntityUtil.getEntity(EntityUtil.java:149)
> at
> org.apache.falcon.resource.AbstractEntityManager.getApplicableColos(AbstractEntityManager.java:174)
> at
> org.apache.falcon.resource.proxy.SchedulableEntityManagerProxy.submit_aroundBody2(SchedulableEntityManagerProxy.java:164)
> at
> org.apache.falcon.resource.proxy.SchedulableEntityManagerProxy$AjcClosure3.run(SchedulableEntityManagerProxy.java:1)
> at
> org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149)
> at
> org.apache.falcon.aspect.AbstractFalconAspect.logAroundMonitored(AbstractFalconAspect.java:51)
> at
> org.apache.falcon.resource.proxy.SchedulableEntityManagerProxy.submit(SchedulableEntityManagerProxy.java:156)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> {nofromat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (FALCON-2088) Entity submission fails with EntityNotRegisteredException
Pragya Mittal created FALCON-2088:
-
Summary: Entity submission fails with EntityNotRegisteredException
Key: FALCON-2088
URL: https://issues.apache.org/jira/browse/FALCON-2088
Project: Falcon
Issue Type: Bug
Components: feed, prism, process
Affects Versions: trunk, 0.10
Reporter: Pragya Mittal
Feed/Process submission fails with following error :
dataqa@falcon1001:~$ falcon entity -type feed -submit -file feed.xml
ERROR: Bad Request;ProcessInstanceResumeTest-raaw-logs16-8a46ee1b (feed) not
found
{noformat}
2016-07-19 07:14:08,901 INFO - [2069246737@qtp-1229202732-5 -
b657de76-c76f-42a0-bc87-12189603862e:dataqa:POST//entities/submit/feed] ~
Logging in dataqa (CurrentUser:65)
2016-07-19 07:14:08,901 INFO - [2069246737@qtp-1229202732-5 -
b657de76-c76f-42a0-bc87-12189603862e:dataqa:POST//entities/submit/feed] ~
Request from authenticated user: dataqa, URL=/api/entities/submit/feed, doAs
user: null (FalconAuthenticationFilter:185)
2016-07-19 07:14:08,909 INFO - [2069246737@qtp-1229202732-5 -
b657de76-c76f-42a0-bc87-12189603862e:dataqa:POST//entities/submit/feed] ~
Parsed Entity: ProcessInstanceResumeTest-raaw-logs16-8a46ee1b (EntityParser:94)
2016-07-19 07:14:08,909 WARN - [2069246737@qtp-1229202732-5 -
b657de76-c76f-42a0-bc87-12189603862e:dataqa:POST//entities/submit/feed] ~
ProcessInstanceResumeTest-raaw-logs16-8a46ee1b (FEED) not found
(AbstractEntityManager:181)
org.apache.falcon.entity.EntityNotRegisteredException:
ProcessInstanceResumeTest-raaw-logs16-8a46ee1b (FEED) not found
at org.apache.falcon.entity.EntityUtil.getEntity(EntityUtil.java:149)
at
org.apache.falcon.resource.AbstractEntityManager.getApplicableColos(AbstractEntityManager.java:174)
at
org.apache.falcon.resource.proxy.SchedulableEntityManagerProxy.submit_aroundBody2(SchedulableEntityManagerProxy.java:164)
at
org.apache.falcon.resource.proxy.SchedulableEntityManagerProxy$AjcClosure3.run(SchedulableEntityManagerProxy.java:1)
at
org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149)
at
org.apache.falcon.aspect.AbstractFalconAspect.logAroundMonitored(AbstractFalconAspect.java:51)
at
org.apache.falcon.resource.proxy.SchedulableEntityManagerProxy.submit(SchedulableEntityManagerProxy.java:156)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
{nofromat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FALCON-2085) FalconJPAService fails to start with NullPointerException
[
https://issues.apache.org/jira/browse/FALCON-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pragya Mittal updated FALCON-2085:
--
Description:
FalconJPAService fails with NullPointerException since application.services
(defined in startup.properties) are not in correct order. Stack trace is :
{noformat}
2016-07-18 07:22:19,961 ERROR - [main:] ~ Failed to initialize service
org.apache.falcon.service.FalconJPAService (ServiceInitializer:49)
java.lang.NullPointerException
at
org.apache.falcon.service.FalconJPAService.getPropsforStore(FalconJPAService.java:111)
at
org.apache.falcon.service.FalconJPAService.init(FalconJPAService.java:87)
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)
2016-07-18 07:22:19,974 ERROR - [main:] ~ Failed startup of context
org.mortbay.jetty.webapp.WebAppContext@5710768a{/,/mnt/falcon/server/server/webapp/falcon}
(log:87)
java.lang.RuntimeException: org.apache.falcon.FalconException:
java.lang.NullPointerException
at
org.apache.falcon.listener.ContextStartupListener.contextInitialized(ContextStartupListener.java:59)
{noformat}
Also no correct documentation is there to define required configurations.
Raised FALCON-2086 for the same.
was:
FalconJPAService fails with NullPointerException since application.services
(defined in startup.properties) are not in correct order. Stack trace is :
{noformat}
2016-07-18 07:22:19,961 ERROR - [main:] ~ Failed to initialize service
org.apache.falcon.service.FalconJPAService (ServiceInitializer:49)
java.lang.NullPointerException
at
org.apache.falcon.service.FalconJPAService.getPropsforStore(FalconJPAService.java:111)
at
org.apache.falcon.service.FalconJPAService.init(FalconJPAService.java:87)
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)
2016-07-18 07:22:19,974 ERROR - [main:] ~ Failed startup of context
org.mortbay.jetty.webapp.WebAppContext@5710768a{/,/mnt/falcon/server/server/webapp/falcon}
(log:87)
java.lang.RuntimeException: org.apache.falcon.FalconException:
java.lang.NullPointerException
at
org.apache.falcon.listener.ContextStartupListener.contextInitialized(ContextStartupListener.java:59)
{noformat}
Also no correct documentation is there to define required configurations
> FalconJPAService fails to start with NullPointerException
> -
>
> Key: FALCON-2085
> URL: https://issues.apache.org/jira/browse/FALCON-2085
> Project: Falcon
> Issue Type: Bug
> Components: prism
>Affects Versions: trunk, 0.10
>Reporter: Pragya Mittal
>
> FalconJPAService fails with NullPointerException since application.services
> (defined in startup.properties) are not in correct order. Stack trace is :
> {noformat}
> 2016-07-18
[jira] [Created] (FALCON-2086) Documentation missing to enable FalconJPAService
Pragya Mittal created FALCON-2086: - Summary: Documentation missing to enable FalconJPAService Key: FALCON-2086 URL: https://issues.apache.org/jira/browse/FALCON-2086 Project: Falcon Issue Type: Bug Components: prism Affects Versions: trunk Reporter: Pragya Mittal Currently there is no documentation available to refer for enabling FalconJPAService. Need to add that to twiki. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FALCON-2085) FalconJPAService fails to start with NullPointerException
Pragya Mittal created FALCON-2085:
-
Summary: FalconJPAService fails to start with NullPointerException
Key: FALCON-2085
URL: https://issues.apache.org/jira/browse/FALCON-2085
Project: Falcon
Issue Type: Bug
Components: prism
Affects Versions: trunk, 0.10
Reporter: Pragya Mittal
FalconJPAService fails with NullPointerException since application.services
(defined in startup.properties) are not in correct order. Stack trace is :
{noformat}
2016-07-18 07:22:19,961 ERROR - [main:] ~ Failed to initialize service
org.apache.falcon.service.FalconJPAService (ServiceInitializer:49)
java.lang.NullPointerException
at
org.apache.falcon.service.FalconJPAService.getPropsforStore(FalconJPAService.java:111)
at
org.apache.falcon.service.FalconJPAService.init(FalconJPAService.java:87)
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)
2016-07-18 07:22:19,974 ERROR - [main:] ~ Failed startup of context
org.mortbay.jetty.webapp.WebAppContext@5710768a{/,/mnt/falcon/server/server/webapp/falcon}
(log:87)
java.lang.RuntimeException: org.apache.falcon.FalconException:
java.lang.NullPointerException
at
org.apache.falcon.listener.ContextStartupListener.contextInitialized(ContextStartupListener.java:59)
{noformat}
Also no correct documentation is there to define required configurations
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FALCON-2076) Server fails to start since extension.store.uri is not defined in startup.properties
[ https://issues.apache.org/jira/browse/FALCON-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2076: -- Assignee: (was: Praveen Adlakha) > Server fails to start since extension.store.uri is not defined in > startup.properties > > > Key: FALCON-2076 > URL: https://issues.apache.org/jira/browse/FALCON-2076 > Project: Falcon > Issue Type: Bug > Components: prism >Affects Versions: 0.10 >Reporter: Pragya Mittal > Fix For: 0.10 > > > If the following property is left blank : > # HDFS location of extension store for extension artifacts > *.extension.store.uri= > Then falcon fails to start saying extension uri to be defined. I have to > explicitly remove it along with org.apache.falcon.extensions.ExtensionService > from application services. > These should be handled and falcon should not fail to start in absence of > these properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FALCON-2076) Server fails to start since extension.store.uri is not defined in startup.properties
[ https://issues.apache.org/jira/browse/FALCON-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2076: -- Description: If the following property is left blank : HDFS location of extension store for extension artifacts *.extension.store.uri= Then falcon fails to start saying extension uri to be defined. I have to explicitly remove it along with org.apache.falcon.extensions.ExtensionService from application services. These should be handled and falcon should not fail to start in absence of these properties. was: If the following property is left blank : # HDFS location of extension store for extension artifacts *.extension.store.uri= Then falcon fails to start saying extension uri to be defined. I have to explicitly remove it along with org.apache.falcon.extensions.ExtensionService from application services. These should be handled and falcon should not fail to start in absence of these properties. > Server fails to start since extension.store.uri is not defined in > startup.properties > > > Key: FALCON-2076 > URL: https://issues.apache.org/jira/browse/FALCON-2076 > Project: Falcon > Issue Type: Bug > Components: prism >Affects Versions: 0.10 >Reporter: Pragya Mittal > Fix For: 0.10 > > > If the following property is left blank : > HDFS location of extension store for extension artifacts > *.extension.store.uri= > Then falcon fails to start saying extension uri to be defined. I have to > explicitly remove it along with org.apache.falcon.extensions.ExtensionService > from application services. > These should be handled and falcon should not fail to start in absence of > these properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FALCON-2076) Server fails to start since extension.store.uri is not defined in startup.properties
[
https://issues.apache.org/jira/browse/FALCON-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pragya Mittal updated FALCON-2076:
--
Component/s: (was: scheduler)
> Server fails to start since extension.store.uri is not defined in
> startup.properties
>
>
> Key: FALCON-2076
> URL: https://issues.apache.org/jira/browse/FALCON-2076
> Project: Falcon
> Issue Type: Bug
> Components: prism
>Affects Versions: 0.10
>Reporter: Pragya Mittal
>Assignee: Praveen Adlakha
> Fix For: 0.10
>
>
> Lets say I have a process with two clusters ua1 and ua2 and process gets
> deleted from ua1. If user fires status request from prism , it should display
> instances from ua2. Currently this is not happening. End result is :
> {noformat}
> dataqa@lda01:~$ falcon entity -type process -status -name processMerlinNative
> ua1/org.apache.falcon.FalconWebException::null
> ua2/RUNNING
> dataqa@lda01:~$ falcon instance -type process -status -name
> processMerlinNative
> ERROR: Bad Request;ua1/processMerlinNative (PROCESS) not found
> ua2/STATUS
> {noformat}
> Although giving colo will show the expected result
> {noformat}
> dataqa@lda01:~$ falcon instance -type process -status -name
> processMerlinNative -colo ua2
> 2016-01-14T09:08Z ProcessMultipleClustersTest-corp-2a8c -
> SUCCEEDED 2016-01-14T10:11Z 2016-01-14T10:12Z -
> http://8RPCG32.corp.inmobi.com:11000/oozie?job=880-160113111840703-oozie-oozi-W
> actions:
> hdfscommands OK -
> aggregator SUCCEEDED
> http://8RPCG32.corp.inmobi.com:8088/proxy/application_1452664055458_1798/
> 2016-01-14T09:07Z ProcessMultipleClustersTest-corp-2a8c -
> SUCCEEDED 2016-01-14T10:02Z 2016-01-14T10:03Z -
> http://8RPCG32.corp.inmobi.com:11000/oozie?job=878-160113111840703-oozie-oozi-W
> actions:
> hdfscommands OK -
> aggregator SUCCEEDED
> http://8RPCG32.corp.inmobi.com:8088/proxy/application_1452664055458_1577/
> 2016-01-14T09:06Z ProcessMultipleClustersTest-corp-2a8c -
> SUCCEEDED 2016-01-14T09:56Z 2016-01-14T09:58Z -
> http://8RPCG32.corp.inmobi.com:11000/oozie?job=876-160113111840703-oozie-oozi-W
> actions:
> hdfscommands OK -
> aggregator SUCCEEDED
> http://8RPCG32.corp.inmobi.com:8088/proxy/application_1452664055458_1444/
> Additional Information:
> Response: ua2/STATUS
> Request Id: ua2/1093419868@qtp-1214810373-11 -
> b81926ad-d244-45ab-9716-02d9b72abbee
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FALCON-2076) Server fails to start since extension.store.uri is not defined in startup.properties
[ https://issues.apache.org/jira/browse/FALCON-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pragya Mittal updated FALCON-2076: -- Description: If the following property is left blank : # HDFS location of extension store for extension artifacts *.extension.store.uri= Then falcon fails to start saying extension uri to be defined. I have to explicitly remove it along with org.apache.falcon.extensions.ExtensionService from application services. These should be handled and falcon should not fail to start in absence of these properties. > Server fails to start since extension.store.uri is not defined in > startup.properties > > > Key: FALCON-2076 > URL: https://issues.apache.org/jira/browse/FALCON-2076 > Project: Falcon > Issue Type: Bug > Components: prism >Affects Versions: 0.10 >Reporter: Pragya Mittal >Assignee: Praveen Adlakha > Fix For: 0.10 > > > If the following property is left blank : > # HDFS location of extension store for extension artifacts > *.extension.store.uri= > Then falcon fails to start saying extension uri to be defined. I have to > explicitly remove it along with org.apache.falcon.extensions.ExtensionService > from application services. > These should be handled and falcon should not fail to start in absence of > these properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FALCON-2076) Server fails to start since extension.store.uri is not defined in startup.properties
[
https://issues.apache.org/jira/browse/FALCON-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pragya Mittal updated FALCON-2076:
--
Affects Version/s: (was: 0.9)
0.10
> Server fails to start since extension.store.uri is not defined in
> startup.properties
>
>
> Key: FALCON-2076
> URL: https://issues.apache.org/jira/browse/FALCON-2076
> Project: Falcon
> Issue Type: Bug
> Components: prism
>Affects Versions: 0.10
>Reporter: Pragya Mittal
>Assignee: Praveen Adlakha
> Fix For: 0.10
>
>
> Lets say I have a process with two clusters ua1 and ua2 and process gets
> deleted from ua1. If user fires status request from prism , it should display
> instances from ua2. Currently this is not happening. End result is :
> {noformat}
> dataqa@lda01:~$ falcon entity -type process -status -name processMerlinNative
> ua1/org.apache.falcon.FalconWebException::null
> ua2/RUNNING
> dataqa@lda01:~$ falcon instance -type process -status -name
> processMerlinNative
> ERROR: Bad Request;ua1/processMerlinNative (PROCESS) not found
> ua2/STATUS
> {noformat}
> Although giving colo will show the expected result
> {noformat}
> dataqa@lda01:~$ falcon instance -type process -status -name
> processMerlinNative -colo ua2
> 2016-01-14T09:08Z ProcessMultipleClustersTest-corp-2a8c -
> SUCCEEDED 2016-01-14T10:11Z 2016-01-14T10:12Z -
> http://8RPCG32.corp.inmobi.com:11000/oozie?job=880-160113111840703-oozie-oozi-W
> actions:
> hdfscommands OK -
> aggregator SUCCEEDED
> http://8RPCG32.corp.inmobi.com:8088/proxy/application_1452664055458_1798/
> 2016-01-14T09:07Z ProcessMultipleClustersTest-corp-2a8c -
> SUCCEEDED 2016-01-14T10:02Z 2016-01-14T10:03Z -
> http://8RPCG32.corp.inmobi.com:11000/oozie?job=878-160113111840703-oozie-oozi-W
> actions:
> hdfscommands OK -
> aggregator SUCCEEDED
> http://8RPCG32.corp.inmobi.com:8088/proxy/application_1452664055458_1577/
> 2016-01-14T09:06Z ProcessMultipleClustersTest-corp-2a8c -
> SUCCEEDED 2016-01-14T09:56Z 2016-01-14T09:58Z -
> http://8RPCG32.corp.inmobi.com:11000/oozie?job=876-160113111840703-oozie-oozi-W
> actions:
> hdfscommands OK -
> aggregator SUCCEEDED
> http://8RPCG32.corp.inmobi.com:8088/proxy/application_1452664055458_1444/
> Additional Information:
> Response: ua2/STATUS
> Request Id: ua2/1093419868@qtp-1214810373-11 -
> b81926ad-d244-45ab-9716-02d9b72abbee
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FALCON-2076) Server fails to start since extension.store.uri is not defined in startup.properties
[
https://issues.apache.org/jira/browse/FALCON-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pragya Mittal updated FALCON-2076:
--
Description: (was: Lets say I have a process with two clusters ua1 and
ua2 and process gets deleted from ua1. If user fires status request from prism
, it should display instances from ua2. Currently this is not happening. End
result is :
{noformat}
dataqa@lda01:~$ falcon entity -type process -status -name processMerlinNative
ua1/org.apache.falcon.FalconWebException::null
ua2/RUNNING
dataqa@lda01:~$ falcon instance -type process -status -name processMerlinNative
ERROR: Bad Request;ua1/processMerlinNative (PROCESS) not found
ua2/STATUS
{noformat}
Although giving colo will show the expected result
{noformat}
dataqa@lda01:~$ falcon instance -type process -status -name processMerlinNative
-colo ua2
2016-01-14T09:08Z ProcessMultipleClustersTest-corp-2a8c -
SUCCEEDED 2016-01-14T10:11Z 2016-01-14T10:12Z -
http://8RPCG32.corp.inmobi.com:11000/oozie?job=880-160113111840703-oozie-oozi-W
actions:
hdfscommands OK -
aggregator SUCCEEDED
http://8RPCG32.corp.inmobi.com:8088/proxy/application_1452664055458_1798/
2016-01-14T09:07Z ProcessMultipleClustersTest-corp-2a8c -
SUCCEEDED 2016-01-14T10:02Z 2016-01-14T10:03Z -
http://8RPCG32.corp.inmobi.com:11000/oozie?job=878-160113111840703-oozie-oozi-W
actions:
hdfscommands OK -
aggregator SUCCEEDED
http://8RPCG32.corp.inmobi.com:8088/proxy/application_1452664055458_1577/
2016-01-14T09:06Z ProcessMultipleClustersTest-corp-2a8c -
SUCCEEDED 2016-01-14T09:56Z 2016-01-14T09:58Z -
http://8RPCG32.corp.inmobi.com:11000/oozie?job=876-160113111840703-oozie-oozi-W
actions:
hdfscommands OK -
aggregator SUCCEEDED
http://8RPCG32.corp.inmobi.com:8088/proxy/application_1452664055458_1444/
Additional Information:
Response: ua2/STATUS
Request Id: ua2/1093419868@qtp-1214810373-11 -
b81926ad-d244-45ab-9716-02d9b72abbee
{noformat})
> Server fails to start since extension.store.uri is not defined in
> startup.properties
>
>
> Key: FALCON-2076
> URL: https://issues.apache.org/jira/browse/FALCON-2076
> Project: Falcon
> Issue Type: Bug
> Components: prism
>Affects Versions: 0.10
>Reporter: Pragya Mittal
>Assignee: Praveen Adlakha
> Fix For: 0.10
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
