Member since
01-08-2017
79
Posts
6
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1013 | 02-27-2018 09:57 PM |
02-27-2018
08:33 PM
Hi, I'm following the instruction to deploy a 10-node cluster on AWS. I managed to get to seeing the 10 nodes got created on my AWS console, but it failed at the step of "Wait for connectivity to the host(s)" How is it that it could create the instance but not able to ssh? Isn't it the same credential? Any suggestion is appreciated.
... View more
Labels:
- Labels:
-
Apache Metron
02-06-2018
03:28 PM
@Simon Elliston Ball Wonderful news! Thank you for the snapshot and the information, I was able to run the script, but I need to work on the query syntax. I assume the query syntax is in Stellar.
... View more
01-31-2018
07:14 PM
Hi, I've noticed in the later releases of Metron, there's a new script pcap_zeppelin_run.sh. Does anyone know the use case of this script? I'm very curious in any pcap development within Metron. From reading the script, it looks like a it wraps around the pcap_query script and it's still in the testing phase? Will we be doing pcap query from zeppelin notebook? thanks
... View more
Labels:
- Labels:
-
Apache Metron
-
Apache Zeppelin
01-24-2018
04:53 PM
I was able to upgrade ambari to 2.6.1 successfully. Thank you again for your help @Jonathan Hurley
... View more
01-24-2018
03:07 PM
Thank you so very much @Jonathan Hurley With your help, I got my id and set my current state. I can now proceed to try again with my upgrade. ambari=> SELECT repo_version_id, version, display_name FROM repo_version ORDER BY version; repo_version_id |version | display_name -----------------+------------+-------------- 1 | 2.5.3.0-37 | HDP-2.5.3.0 (1 row) ambari=> UPDATE cluster_version SET state = 'CURRENT' WHERE repo_version_id = 1; UPDATE 1 Thank you!
... View more
01-24-2018
02:54 PM
Thank you @Jonathan Hurley for your response and explanation. Pardon my very limited knowledge of ambari and postgresql. I logged on to ambari postgres and see the below relationship, but how do I find out what's my repo_version_id? ambari | repo_version| table | postgres ambari | cluster_version | table | postgres Thank you for your help.
... View more
01-23-2018
06:35 PM
Hello All, I've been stuck with upgrading many versions of ambari-server to finally get to the version 2.6.1.0; but kept failing. The last stack is from ambari-server of 2.5.2 to 2.6.1 with the following error Traceback (most recent call last):
File "/usr/sbin/ambari-server.py", line 952, in <module>
mainBody()
File "/usr/sbin/ambari-server.py", line 922, in mainBody
main(options, args, parser)
File "/usr/sbin/ambari-server.py", line 874, in main
action_obj.execute()
File "/usr/sbin/ambari-server.py", line 78, in execute
self.fn(*self.args, **self.kwargs)
File "/usr/lib/python2.6/site-packages/ambari_server/serverUpgrade.py", line 258, in upgrade
retcode = run_schema_upgrade(args)
File "/usr/lib/python2.6/site-packages/ambari_server/serverUpgrade.py", line 159, in run_schema_upgrade
upgrade_response = json.loads(stdout)
File "/usr/lib/python2.6/site-packages/ambari_simplejson/__init__.py", line 307, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line 335, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python2.6/site-packages/ambari_simplejson/decoder.py", line 353, in raw_decode
raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded 23 Jan 2018 13:30:58,621 INFO [main] LockFactory:53 - Lock profiling is disabled
23 Jan 2018 13:30:58,634 INFO [main] SchemaUpgradeHelper:420 - Upgrading schema to target version = 2.6.1.0
23 Jan 2018 13:30:58,673 INFO [main] SchemaUpgradeHelper:429 - Upgrading schema from source version = 2.5.2
23 Jan 2018 13:30:58,677 INFO [main] SchemaUpgradeHelper:163 - Upgrade path: [{ upgradeCatalog: sourceVersion = 2.5.2, targetVersion = 2.6.0 }, { upgradeCatalog: sourceVersion = 2.6.0, targetVersion = 2.6.1 }, { upgradeCatalog: sourceVersion = null, targetVersion = 2.6.1 }, { upgradeCatalog: sourceVersion = null, targetVersion = 2.6.1 }]
23 Jan 2018 13:30:58,677 INFO [main] SchemaUpgradeHelper:201 - Executing DDL upgrade...
23 Jan 2018 13:30:58,678 INFO [main] DBAccessorImpl:874 - Executing query: ALTER SCHEMA ambari OWNER TO "ambari";
23 Jan 2018 13:30:58,679 INFO [main] DBAccessorImpl:874 - Executing query: ALTER ROLE "ambari" SET search_path to 'ambari';
23 Jan 2018 13:30:58,710 ERROR [main] SchemaUpgradeHelper:208 - Upgrade failed.
org.apache.ambari.server.AmbariException: Unable to find any CURRENT repositories.
at org.apache.ambari.server.upgrade.UpgradeCatalog260.getCurrentVersionID(UpgradeCatalog260.java:540)
at org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:210)
at org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:931)
at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:206)
at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:444)
23 Jan 2018 13:30:58,713 ERROR [main] SchemaUpgradeHelper:464 - Exception occurred during upgrade, failed
org.apache.ambari.server.AmbariException: Unable to find any CURRENT repositories.
at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:209)
at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.main(SchemaUpgradeHelper.java:444)
Caused by: org.apache.ambari.server.AmbariException: Unable to find any CURRENT repositories.
at org.apache.ambari.server.upgrade.UpgradeCatalog260.getCurrentVersionID(UpgradeCatalog260.java:540)
at org.apache.ambari.server.upgrade.UpgradeCatalog260.executeDDLUpdates(UpgradeCatalog260.java:210)
at org.apache.ambari.server.upgrade.AbstractUpgradeCatalog.upgradeSchema(AbstractUpgradeCatalog.java:931)
at org.apache.ambari.server.upgrade.SchemaUpgradeHelper.executeUpgrade(SchemaUpgradeHelper.java:206)
... 1 more
... View more
Labels:
- Labels:
-
Apache Ambari
12-05-2017
06:44 PM
Thank you very much @Jasper I was able to do that for the indexing topology, but how do you set that for parsing and enrichment topology? I still see a large number of failed under indexing topology but nothing obvious in logs. Occasionally, I see kafka coordinate mark and discover dead topic and I don't know how to fix that, but it goes away after awhile
... View more
12-04-2017
08:05 PM
Thank you @Jasper I noticed I kept getting the error about fetching an offset out of range. I changed the kafka log retention rule to be shorter b/c I kept getting Out of Space because of pcap ingestion and kafka-log for pcap took all my space. Since I stop ingesting pcap, I reverted back the kafka retention rule and hopefully it won't complain about trying to read an offset that is already wiped out. If this doesn't work, I'll try the DEBUG mode that you suggested. Thank you again for your help! Fetch offset 82387394 is out of range for partition indexing-0, resetting offset
... View more