Member since
08-08-2017
1652
Posts
30
Kudos Received
11
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2093 | 06-15-2020 05:23 AM | |
| 17466 | 01-30-2020 08:04 PM | |
| 2256 | 07-07-2019 09:06 PM | |
| 8730 | 01-27-2018 10:17 PM | |
| 4914 | 12-31-2017 10:12 PM |
06-11-2018
05:33 AM
@Geoffrey , files are created each day ( average 5 files each day ) , on other clusters this isnt happens , so if I will delete the old files then the problem will return , so I need to find the root cause , maybe conf problem but my cluster have the same conf of cluster that not have this problem , so I am little confuse ,
... View more
06-10-2018
03:07 PM
I have found myself in a situation where the pg_xlog folder contains 80GB of data maybe because wrong configuration how to purge or cleanup the files under pg_xlog? /var/lib/pgsql/data/pg_xlog
[root@master02 pg_xlog]# ls -ltr | more
total 53887180
-rw-------. 1 postgres postgres 16777216 Sep 19 2017 0000000100000000000000F1
-rw-------. 1 postgres postgres 16777216 Sep 19 2017 0000000100000000000000F2
-rw------- 1 postgres postgres 16777216 Sep 19 2017 0000000100000000000000F3
-rw------- 1 postgres postgres 16777216 Sep 19 2017 0000000100000000000000F4
-rw------- 1 postgres postgres 16777216 Sep 19 2017 0000000100000000000000F5
-rw------- 1 postgres postgres 16777216 Sep 20 2017 0000000100000000000000F6
-rw------- 1 postgres postgres 16777216 Sep 20 2017 0000000100000000000000F7
-rw------- 1 postgres postgres 16777216 Sep 20 2017 0000000100000000000000F8
-rw------- 1 postgres postgres 16777216 Sep 20 2017 0000000100000000000000F9
-rw------- 1 postgres postgres 16777216 Sep 20 2017 0000000100000000000000FA
-rw------- 1 postgres postgres 16777216 Sep 20 2017 0000000100000000000000FB
-rw------- 1 postgres postgres 16777216 Sep 20 2017 0000000100000000000000FC
-rw------- 1 postgres postgres 16777216 Sep 20 2017 0000000100000000000000FD
-rw------- 1 postgres postgres 16777216 Sep 21 2017 0000000100000000000000FE
-rw------- 1 postgres postgres 16777216 Sep 21 2017 000000010000000100000000
-rw------- 1 postgres postgres 16777216 Sep 21 2017 000000010000000100000001
-rw------- 1 postgres postgres 16777216 Sep 21 2017 000000010000000100000002
-rw------- 1 postgres postgres 16777216 Sep 21 2017 000000010000000100000003
-rw------- 1 postgres postgres 16777216 Sep 21 2017 000000010000000100000004
-rw------- 1 postgres postgres 16777216 Sep 21 2017 000000010000000100000005
-rw------- 1 postgres postgres 16777216 Sep 22 2017 000000010000000100000006
-rw------- 1 postgres postgres 16777216 Sep 22 2017 000000010000000100000007
-rw------- 1 postgres postgres 16777216 Sep 22 2017 000000010000000100000008
-rw------- 1 postgres postgres 16777216 Sep 22 2017 000000010000000100000009
-rw------- 1 postgres postgres 16777216 Sep 22 2017 00000001000000010000000A
-rw------- 1 postgres postgres 16777216 Sep 22 2017 00000001000000010000000B
-rw------- 1 postgres postgres 16777216 Sep 23 2017 00000001000000010000000C
-rw------- 1 postgres postgres 16777216 Sep 23 2017 00000001000000010000000D
-rw------- 1 postgres postgres 16777216 Sep 23 2017 00000001000000010000000E
-rw------- 1 postgres postgres 16777216 Sep 23 2017 00000001000000010000000F
-rw------- 1 postgres postgres 16777216 Sep 23 2017 000000010000000100000010
-rw------- 1 postgres postgres 16777216 Sep 23 2017 000000010000000100000011
-rw------- 1 postgres postgres 16777216 Sep 23 2017 000000010000000100000012
-rw------- 1 postgres postgres 16777216 Sep 24 2017 000000010000000100000013
-rw------- 1 postgres postgres 16777216 Sep 24 2017 000000010000000100000014
-rw------- 1 postgres postgres 16777216 Sep 24 2017 000000010000000100000015
-rw------- 1 postgres postgres 16777216 Sep 24 2017 000000010000000100000016
-rw------- 1 postgres postgres 16777216 Sep 24 2017 000000010000000100000017
-rw------- 1 postgres postgres 16777216 Sep 24 2017 000000010000000100000018
-rw------- 1 postgres postgres 16777216 Sep 24 2017 000000010000000100000019
-rw------- 1 postgres postgres 16777216 Sep 24 2017 00000001000000010000001A
-rw------- 1 postgres postgres 16777216 Sep 24 2017 00000001000000010000001B
-rw------- 1 postgres postgres 16777216 Sep 25 2017 00000001000000010000001C
-rw------- 1 postgres postgres 16777216 Sep 25 2017 00000001000000010000001D
-rw------- 1 postgres postgres 16777216 Sep 25 2017 00000001000000010000001E
-rw------- 1 postgres postgres 16777216 Sep 25 2017 00000001000000010000001F
-rw------- 1 postgres postgres 16777216 Sep 25 2017 000000010000000100000020
-rw------- 1 postgres postgres 16777216 Sep 25 2017 000000010000000100000021
--More--
... View more
Labels:
06-10-2018
10:13 AM
hi all we want to trigger the spark history deletion each hour ( spark.history.fs.cleaner.interval = 1h ) and to delete the spark history logs that older then one day ( spark.history.fs.cleaner.maxAge = 1d ) so we set the following: and restart the spark services but after 2 hours still logs not deleted in spite logs need to deleted after one hour according to our setings why logs not deleted after one hour ?
... View more
Labels:
06-09-2018
09:01 PM
I also found that, so what is the right variable to set ? ( JAVA_OPTS or JVMFLAGS ) export JVMFLAGS="-Djute.maxbuffer=11000000"
... View more
06-08-2018
10:02 AM
how to validate that ? , I mean after I set in ambari "export JAVA_OPTS="-Djute.maxbuffer=11000000" and restart the zoo service then how to verify this seting is affected ? any way from some CLI to check that Djute.maxbuffer=11000000 ? we try: ps -ef | grep maxbuffer but no output, any suggestion how to validate the settings?
... View more
06-07-2018
09:17 PM
Geoffrey as I understand if I set the variable - export JAVA_OPTS="-Djute.maxbuffer=11000000" In ambari GUI ( as --> zookeper --> CONFIG --> zookeeper-env template ) then click on save and restart the service then it will be affected all zookeeper servers - am I right ? so no need to set it separate on each server,,
... View more
06-07-2018
07:51 PM
thank you Geoffrey , as I mentioned we want to increase only 0.1M to this value , as you said this isn't much , and we hope this will cause any issues second can you approve my syntax in zookeeper-env template in ambari? or maybe you have some remarks ? export JAVA_OPTS="-Djute.maxbuffer=11000000"
... View more
06-07-2018
04:52 PM
hi all when we upload conf file to zookeper we get the error - the .....xml weights 1095kb , which is more than zookeeper can have by default
(1024kb) so we decided to increase the ZNode size ( the default is limited to 1MB ) according to the article - https://community.hortonworks.com/content/supportkb/150660/error-javaioioexception-len-error-in-zookeeper-cau.html we set the following ( in order to support the 1095Kb size ) export JAVA_OPTS="-Djute.maxbuffer=11000000" in zookeeper-env template , ( ambari zookeeper CONFIG ) is this correct actions ?
... View more
Labels:
06-05-2018
03:59 PM
regarding the last option - Just block the public-repo-1.hortonworks.com public IP what you mean just "lock the public-repo-1.hortonworks.com public IP" HOW? remark we use only scripts to install ambari & HDP , so if we need to change someting in ambari we need to use API in order to perfrom some changing
... View more
06-05-2018
03:58 PM
regarding the /etc/hosts , do you mean to put as: 1.1.1.1 public-repo-1.hortonworks.com while no access to 1.1.1.1
... View more