<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: cluster entry vertix must exist - Falcon issue? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/cluster-entry-vertix-must-exist-Falcon-issue/m-p/121126#M55283</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/14813/tsankar85.html" nodeid="14813"&gt;@Sankar T&lt;/A&gt; To resolve this issue, following is the workaround :&lt;/P&gt;&lt;P&gt;1. Remove service org.apache.falcon.metadata.MetadataMappingService from *.application.services in falcon startup.properties available in /etc/falcon/conf/&lt;/P&gt;&lt;P&gt;2. Restart falcon server &lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;</description>
    <pubDate>Fri, 24 Feb 2017 17:17:51 GMT</pubDate>
    <dc:creator>pbishnoi</dc:creator>
    <dc:date>2017-02-24T17:17:51Z</dc:date>
    <item>
      <title>cluster entry vertix must exist - Falcon issue?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/cluster-entry-vertix-must-exist-Falcon-issue/m-p/121125#M55282</link>
      <description>&lt;P&gt;Recently we had HDP 2.5.3 version upgrade, post validation steps we are checking Falcon job flows. we got a strange error stating -"cluster Entry vertex must exist" . did any one had the same and any fix ? Even after Falcon server restart is not solving the issue.&lt;/P&gt;&lt;P&gt;I could see some one have raised Falcon Jira request too.&lt;/P&gt;&lt;P&gt;&lt;A href="https://issues.apache.org/jira/browse/FALCON-1955" target="_blank"&gt;https://issues.apache.org/jira/browse/FALCON-1955&lt;/A&gt;&lt;/P&gt;&lt;P&gt;any help , greatly appreciated.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Feb 2017 10:48:42 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/cluster-entry-vertix-must-exist-Falcon-issue/m-p/121125#M55282</guid>
      <dc:creator>t_sankar85</dc:creator>
      <dc:date>2017-02-23T10:48:42Z</dc:date>
    </item>
    <item>
      <title>Re: cluster entry vertix must exist - Falcon issue?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/cluster-entry-vertix-must-exist-Falcon-issue/m-p/121126#M55283</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/14813/tsankar85.html" nodeid="14813"&gt;@Sankar T&lt;/A&gt; To resolve this issue, following is the workaround :&lt;/P&gt;&lt;P&gt;1. Remove service org.apache.falcon.metadata.MetadataMappingService from *.application.services in falcon startup.properties available in /etc/falcon/conf/&lt;/P&gt;&lt;P&gt;2. Restart falcon server &lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;</description>
      <pubDate>Fri, 24 Feb 2017 17:17:51 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/cluster-entry-vertix-must-exist-Falcon-issue/m-p/121126#M55283</guid>
      <dc:creator>pbishnoi</dc:creator>
      <dc:date>2017-02-24T17:17:51Z</dc:date>
    </item>
    <item>
      <title>Re: cluster entry vertix must exist - Falcon issue?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/cluster-entry-vertix-must-exist-Falcon-issue/m-p/121127#M55284</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/179/pbishnoi.html" nodeid="179"&gt;@peeyush&lt;/A&gt; Thanks for your help. Followed the same and issue been resolved. &lt;/P&gt;</description>
      <pubDate>Wed, 01 Mar 2017 02:19:19 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/cluster-entry-vertix-must-exist-Falcon-issue/m-p/121127#M55284</guid>
      <dc:creator>t_sankar85</dc:creator>
      <dc:date>2017-03-01T02:19:19Z</dc:date>
    </item>
  </channel>
</rss>

