siddharth's space

1. Most often outages happen because of config changes in dependencies used by your application. To give an example, lets say you are running hadoop jobs on a cluster and relying on HADOOP_USER_NAME to set the privileges under which your job runs. This has been working for quite some time. But now the cluster admin enables kerberos on the cluster and your job suddenly fails and you have an outage.

When Kerberos is disabled, the identity of a user is picked up by Hadoop first from the environment variable HADOOP_USER_NAME, then from the OS-level username (e.g. the system property user.name).

2. Second most common cause of outage is outage in a dependency. Say you are relying on AWS S3 to fetch some static content. And this happened.

3. A third common reason is expired credentials. Your service has been working fine for months. But now all of a sudden some credentials expire and you get a pager alarm.

select the icon at the left

then select datastore from the dropdown

you should now be able to run GQL queries like before

Ran into this issue today while trying to run a program from IntelliJ and using SLF4J for logging. pom.xml looked like below:

<pre><dependency>
    <groupId>org.slf4j</groupId>
    <artifactId>slf4j-api</artifactId>
    <version>1.7.21</version>
</dependency>
<dependency>
    <groupId>org.slf4j</groupId>
    <artifactId>slf4j-simple</artifactId>
    <version>1.6.1</version>
</dependency>

</pre>

I was not creating any fat jar. The problem was that IntelliJ was not able to import the

slf4j-simple dependency. To check this goto View -> Tool Windows -> Maven Projects.
Saw red swiggly lines as described in http://stackoverflow.com/a/24892769/147530. Could not find artifact descriptor.
Solution:
Downloaded the file manually from https://mvnrepository.com/artifact/org.slf4j/slf4j-simple/1.6.1 and installed it manually by running:

mvn install:install-file -Dfile=/Users/siddjain/Downloads/slf4j-simple-1.6.1.jar -DgroupId=org.slf4j -DartifactId=slf4j-simple -Dversion=1.6.1 -Dpackaging=jar

Now did a reimport in IntelliJ and the error went away

Step 1. Check that your Settings (accessed from File -> Settings) match following screenshots or equivalent:

Step 2: Close IntelliJ

Step 3: Delete all .idea directory and .iml files in your repo:

rm $(find . -name *.iml)

rm -r $(find . -name .idea)

will delete all files recursively on mac. On windows use the simpler

dir *.iml /s

dir .idea /s

Step 4: Delete IDEA system directory. On Windows the IDEA system directory is C:\Users\username\.IntelliJIdea2016.2\system

On Mac do:

rm -r ~/Library/Logs/IntelliJIdea15/*

rm -r ~/Library/Caches/IntelliJIdea15/*

Resources:

http://stackoverflow.com/a/5905931/147530:

First of all you should try File | Invalidate Caches and if it doesn’t help, delete IDEA system directory. Then re-import the Maven project and see if it helps.

http://www.fastcompany.com/3062596/tim-cooks-apple/eddie-cue-and-craig-federighi-open-up-about-learning-from-apples-failures

We had long discussions at the ET [executive team] level about the importance of Maps, where we thought Maps was going in the future, and could we treat it as a third-party app? I mean, we don’t do every app. We’re not trying to create a Facebook app. We think they do a great job. We always came back to the conclusion that Maps was not one of those. It’s an integral part to the whole platform. There were so many features that we wanted to build that are dependent on that technology, and we couldn’t see ourselves being in a position where that was something that we didn’t own.

It’s very, very expensive, and it doesn’t have a direct revenue stream. So when I say it’s only Google and us who are developing it, well, that’s part of the reason why. You can’t be a company going out and developing maps to make money; at least no one’s figured that out.